I found a one of the ActiveMQ thread got stuck unexpectedly for several days. Customer was very angry to the ActiveMQ for the bad behavior. Did anybody experienced this issue? It would be much appreciated if any clue!!!
My application is normal Java JMS application like the following:
create destination, producer and message
The follows is the stack when I looked into it with debug tools:
Based on my experiences if the issue caused by the producer flow control configuration, the logs will have some warning messages, right? In fact I didn't found any warning or errors in the activemq.log.
Anyway, I'll check the configuration files right now.
Re:Re: Re: Re: ActiveMQ client app hold unexpectedly!!!
I found the issue just this time. It worked fine for about two month with the ActiveMQ M/S cluster.
I've thought of the network glitch; What I feel strange most is there is no any error/exception on both the ActiveMQ client side and server side.
I went through the related codes and found there is a FutureResponse.getResult method with parameter 'timeout'. Maybe this method is more suitable for getting the result. Not very sure, hehe.