Hello,
we are using ActiveMQ 5.3. Application is using Spring JMSTemplate
(DefaultMessageListenerContainer)
configured like this:
<bean id="jmsContainer"
class="org.springframework.jms.listener.DefaultMessageListenerContainer">
<property name="autoStartup" value="false"/>
<property name="connectionFactory" ref="myConnectionFactory"/>
<property name="destination" ref="myDestination"/>
<property name="messageListener" ref="smppbean"/>
<property name="acceptMessagesWhileStopping" value="false"/>
<property name="sessionTransacted" value="true"/>
</bean>
<bean id="myDestination" class="org.apache.activemq.command.ActiveMQQueue">
<constructor-arg value="${activemq.queue}"/> </bean>
<bean id="myConnectionFactory"
class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL" value="${activemq.brokerUrl}"/>
</bean>
The container has started, few messages are delivered. When things
go wrong, onMessage returns without exception (we can see that from
our logs). In a "stuck" state, code is not in our application,
so it seems ActiveMQ is somewhat frozen, but it should not be waiting
for anything in application. There are no exceptions in the console.
When I click in the admin interface, everything is okay, except for our
queue. Clicking on a queue name or any of the operations (except for
View consumers) hangs. I can not even purge the queue or view it's
messages.
I believe this is a bug in ActiveMQ, or I am not getting something, but
I think any consumer should freeze ActiveMQ. No other consumers
get messages either. Is this a known bug or I have configured something
wrong?
We are using a cluster, which mainly works with one or two consumers.
When I disconnect or connect the cluster, the behavior is still the same.
Any ideas?
Thank you,
Juraj.
