Obviously something is wrong with the thread-safe operation the write stack.
If it was thread safe then there is no need to ever have locks in the filter
chain unless you have an executor filter.
1027 exposes a bug in the lock routines of IoSession
Sent from my iPhone
> On Feb 9, 2016, at 12
Le 09/02/16 18:22, Jon V. a écrit :
> Its my understanding that Read and Write operations are thread-safe and
> should never cause deadlocks. (not sure why there are locks in those
> filters)
>
> Also, I don’t think SSL should be after Proxy. You cannot initiate an SSL
> session if you proxy the s
Its my understanding that Read and Write operations are thread-safe and
should never cause deadlocks. (not sure why there are locks in those
filters)
Also, I don’t think SSL should be after Proxy. You cannot initiate an SSL
session if you proxy the setup routine. What is the goal in this setup?
Hello,
I detected a deadlock when using Proxies and Ssl together.
The SslFilter and the ProxyFilzter both have synchronized blocks, and when
sending
and receiving messages you get deadlocks.
The SslFilter hangs in "sslLock.lock()" in "SslHandler.flushScheduledEvents()",
while the ProxyFilter
