We have the same problem with 5.1. Out of some 100 object messages produced,
4 messagges are left (actually leaped because they are generated in the
middle).
When we restart the broker then the massages are read.
The reader in configured with spring. The onMessage method is marked as
transactional.
<bean id="listenerQueueTawGridResultados"
class="org.springframework.jms.listener.DefaultMessageListenerContainer">
<property name="concurrentConsumers" value="1"/>
<property name="connectionFactory" ref="jmsFactory" />
<property name="destination" ref="jmsQueueTawGridResultados" />
<property name="messageListener" ref="gestorResultadosService"
/>
<property name="transactionManager" ref="jmsTransactionManager"
/>
<property name="sessionTransacted" value="true"/>
<property name="recoveryInterval" value="10000"/>
</bean>
Any idea?
--
View this message in context:
http://www.nabble.com/Messages-dont-get-redelivered-till-broker-restart---expected-behaviour--tp9615827s2354p17515417.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
