In CMT message driven bean with 'NOT Supported' tx attribute, if runtime exception occures while executing onMessge method, will the message be put back to into queue? Because in case of CMT, the message acknowledgement is based on whether tx is committed or rolled back. So, how it behaves when tx attribute is 'Not supported'?
Thanks, <br />Prashant<br />SCJP, SCBCD
posted 12 years ago
So, how it behaves when tx attribute is 'Not supported'?
If the transaction attribute is not supported that means the method will run in an unspecified transaction context which means that the container is free to do anything. Unspecified transaction context doesn't mean that that it is guaranteed that there will be no transaction but it is left to the container provider.
If any system exception is thrown (Runtime exception) the message will be placed back in the queue.