Hello,
For some reason, my consumer stops receiving message after some time. The
problem seems to be triggered by varying the load. Here is the JMX for the
queue when the consumer stops. You could see that there were a lot of
pending messages.
http://www.nabble.com/file/p20613096/consumer-problem.png
The consumer uses Spring DefaultMessageListenerContainer.
<!-- and this is the message listener container for a queue -->
<bean id="jmsContainer"
class="org.springframework.jms.listener.DefaultMessageListenerContainer">
<property name="connectionFactory" ref="connectionFactory"/>
<property name="destination" ref="myDestination"/>
<property name="messageListener" ref="myMessageListener"/>
<property name="cacheLevelName" value="CACHE_CONSUMER"/>
</bean>
The message listener is just write the text of the message to a file using
log4j.
The consumer Java process was running when it actually stopped receiving.
There were no error or exception. Any advice of how to investigate further.
Some unknown problem about DefaultMessageListenerContainer? I did a
thread-dump and saw some ActiveMQ Session Task threads were blocked by
DefaultMessageListenerContainer. But I am not sure whether it was the
problem.
Thank you very much.
--
View this message in context:
http://www.nabble.com/Consumer-stops-receiving-message-tp20613096p20613096.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
