Greg Wilkins

@arshadwkhan can you attach any stack traces that you have, as that will make it easier to replicate.

@arshadwkhan not yet. Other priorities sorry. But just to clarify the scenario: 1. request received client->proxy 2. request sent proxy->server 3. response received server-> proxy with large header 4. 200...

@lachlan-roberts for now any WebSocketClientConfiguration should be off by default, so it can be contained in the normal client jar. You then need to add it in a `context.xml` file...

@janbartel I agree that conceptually we want to enable/disable modules per webapp. However there is simply not the mechanism to do that as ini files are just a way to...

We certainly can do: ```java public interface LifeCycle { ... interface Closeable extends LifeCycle, AutoCloseable { @Override default void close() throws Exception { stop(); } } } ``` Not sure...

@r0bertini Something is very strange here. Firstly your stacks still do not match 10.0.18 entirely. Then the thread 10442 is waiting on a _dateLock on Server. Which is used in...

There is not much we can investigate further on, simply because it is so bizarre. It certainly looks like you have some thread holding the _dateLock, but then I cannot...

This is a step toward #235

I see this more as a utility implementation of Callback (like CompletableFututre is a utility implementation of Future). It might also be good to have an abstract version where the...

@scrat98 again note #11598 which deprecates ChunkAccumulator. It is still draft status, but we are working on improving these areas of the code.