MDBs and JDBC Transactions

If you have a scenario where an Asynchronous Message Arrives and then it has to be written to the database. In case

the write fails, is there any way we can roll back the ENTIRE transaction, so that the message can be re-delivered?

This is assuming I'm using the conventional JMS model (not SonicMQ or any other vendor)

[339 byte] By [Balroga] at [2007-11-27 3:52:51]
# 1
If the MDB has container-managed transactions and onMessage has tx attribute REQUIRED, thespecification requires that the message be redelivered at least once.In this scenario, thedelivery of the message itself is considered a unit of work within the transaction.
ksaksa at 2007-7-12 8:56:52 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...