We still see the threads stuck in socketWrite both on the broker and clients, during the failover. And the failover is not successful. And these sockets were not released till we recycle the broker and client.
We are using AMQ 5.4.2 and for performance perspective, we are using Straight through Session Consumption ie, alwaysSessionAsync set to false. But this is not an issue when we set alwaysSessionAsync to true. >From the jira items, viz http:// https://issues.apache.org/jira/browse/AMQ-2693 2693 , we notice that this socketWrite issue has been resolved in 5.4. But it isnt the case. The issue is highly repeatable. In the attachment, i had the thread dump on both the broker as well as the clients connected to it. Let me know in case you need more details. http://activemq.2283324.n4.nabble.com/file/n4283418/AMQ_542_socketWrite_alwaysSessionAsync__false.txt AMQ_542_socketWrite_alwaysSessionAsync__false.txt -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-potential-hang-with-failover-deadlock-pending-dispatch-with-AMQ-5-4-2-tp4283418p4283418.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
