Hi,
Thanks for your reply. I know the message failed 4 times, and i know why
(it's an exception thrown by consummer causing the reject of the message :
My goal is not to correct this exception because i throw it volontary to
test the redelivery delay).
My goal is that activemq keep message for a long time (yes, the high value
of initialRedeliveryDelay is intended) before send it again in the file. But
for the time, activemq only kept the message 1 seconde before resending.
The bean receiving message look like that (it's an EJB, managing
transaction, with async method):
/
@Stateless
@TransactionManagement(TransactionManagementType.BEAN)
public class MyJmsAsyncReceiver{
...
@Override
@Asynchronous
@Lock(LockType.READ)
@AccessTimeout(-1)
public final Future<Integer> receiveMsg(){
try {
userTransaction.begin();
...
myQueueConnection.start();
...
myMessageConsumer.receive(5000);
...
userTransaction.commit();
...
closeAll(myQueueSession, myQueueConnection, myMessageConsumer);
} catch (Exception e1) {
userTransaction.rollback();
closeAll(myQueueSession, myQueueConnection, myMessageConsumer);
}
...
}/
but not sure the consumer change anything in activemq configuration, isn't
it?
thanks
Clément
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/TomEEplus-Activemq-RedeliveryDelay-not-working-tp4673241p4673326.html
Sent from the TomEE Users mailing list archive at Nabble.com.
