Hi Guus,
indeed, this is what I was looking for.
So this thread (TaskEngine-pool-3) is locking the StreamManager class
(the synchrinized on streamManager) and the global StreamManager class
lock done by thread socket_c2s_ssl-thread-2 in the StreamManager.java
class, function
Hi Emmanuel,
I'm not sure if I understand what you're saying or asking. My email client
doesn't do a great job of formatting all that code in the email either,
which might add to the confusion.
The code that you seem to refer to is here:
Hi Guus,
thanks for teh full stack trace.
I've some concern about this blocked thread:
"TaskEngine-pool-3" #40 daemon prio=5 waiting on lock
java.lang.Thread.State: BLOCKED
- blocked on org.apache.mina.filter.ssl.SSLHandlerG0@99f49e2 (owned by
socket_c2s_ssl-thread-2 id=78)
at
Check my graphic in the previous email.
On Mon, Dec 12, 2022 at 3:53 AM Emmanuel Lécharny
wrote:
> Hi Guus,
>
> there is something missing in the stacck trace: the two threads are
> blocked on different monitors:
> * SSLHandlerG0@99f49e2 owned by socket_c2s_ssl-thread-2
> *
Hi Guus,
there is something missing in the stacck trace: the two threads are
blocked on different monitors:
* SSLHandlerG0@99f49e2 owned by socket_c2s_ssl-thread-2
* StreamManager@7e024771 owned by TaskEngine-pool-3
they are not related, they are not blocking each one other.
Can you provide
