activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wolfgang Schmid <>
Subject Deadlock in Broker (using SSL)
Date Fri, 25 Oct 2013 13:00:58 GMT

we are running ActiveMQ 5.8 on a Solaris platform (Solaris 10) and we are
using SSL. That's the way how we defined the SSL stuff:

<broker ...>

          <transportConnector name="ssl"
         <sslContext keyStore="file:...../server-keystore"
                     keyStorePassword="some password"
                     trustStorePassword="some password"/>


So currently we running tests without InactivityMonitor. (but we have the
same behavior if InactivityMonitor is active).

In our test scenario we have many clients that send messages (both to queues
and topics) and one server that processes these messages.
The broker is activated using the Tanuki service wrapper.

As you can see in the attached logfile of the service wrapper you can see
two situation, where the service warpper detects a deadlock in the broker
and therefore restarts the broker.

Any ideas why there is a dead lock ?
Why do I see a TCp connection even if we use SSL ?
INFO   | jvm 8    | 2013/10/25 06:54:13 | WrapperManager Error: "ActiveMQ
Connection Dispatcher:tcp://" tid=0

Any comments are appreciated.


View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message