Peristent Message not redelivered even though MDB didnt ackn

[upankar]

I am using jboss-4.0.2. We have a queue configured (with default org.jboss.mq.pm.jdbc2.PersistenceManager) and send persistent TextMessage to it from a client app. There is a MDB configured to consume in Client_acknowledgement mode from this queue. When there is a problem in processing the message in MDB, we dont acknowledge the message and hence expects it to be redelivered. But i can not get it redelivered. The QueueDepth also shows 0 meaning it is no longer stored. Does it lose the message ? Is there anything special that needs to be done ? I believe we probably are missing some reqd configuration as this is something a bare minimum requirement of a JMS provider.

[schrouf]

do you call context.setRollbackOnly() in case of a processing error ? this is the 'normal' way to force redelivery as acknowledgment is handled by the MDB container as part of the transaction handling.

regards
ulf

[upankar]

Thanks. It works.. But could you please explain why it is needed to call setRollBackOnly() ? My application didnt start any transaction, so a roll-back was not necessary. Or, is it that JMS provider always invokes MDB onMessage() on a transactional context implicitely ?

Anyway.. Thanks again. Atleast, it is getting redelivered now as intended

[schrouf]

It's the MDB container that handles all transactions for the MDB. The call to context.serRollbackOnly() within the MDB just sets a signal flag for the 'surrounding' MDB container that actually triggers the rollback operation.

regards
ulf