"rollback" a Message during onMessage()

[wdfink]

Hi,

I have a problem to get a Message twice if error occur.

My idea:
If a problem occurs in onMessage() the Message should be delivered again.

My Code:

QueueConnectionFactory conF = (QueueConnectionFactory).lookup("QueueConnectionFactory");
con = conF.createQueueConnection();
session=con.createQueueSession(false,acknowledge);
//Test with acknowledge DUPS_OK_ || CLIENT_ || AUTO_
. . .

onMessage(message) {
try {
if(!error) {
message.acknowledge();
}
}catch(Exception e) {
//Error . . .
}
}


After onMessage() runs the Message is never delivered again, I think it's marked as 'delivered' in JBoss-Queue.

What is wrong with my idea :-( or Code?

Thanks
Wolf

[mefesto78]

In your message driven bean, are you throwing a TransactionRolledBackLocalException when you detect an error and do not want to continue processing?

That will keep the transaction from completing and the message will stay in queue.

Allen

[simonh10]

TransactionRolledBackLocalException is not in any of the jar files and the MessageListener does not specify that an exception is thrown, could you be a little more exact as I would like to achieve transactional stuff in message driven beans.

[simonh10]

Well, I've managed to get it working in a different way than suggested above.

Good article to explain it.
http://www.javaworld.com/javaworld/jw-03-2002/jw-0315-jms-p5.html

Is the redelivery from a failed transaction configurable, number of retries, time between etc.

The system tries to send them again when a new message arrives in the queue and when the ejb is redployed are there any other events that would make the system attempt another delivery?