glassfish_at_javadesktop.org wrote:
> Hi.
> If you have a container managed transaction on an mdb onMessage() method, and the app server runs out of memory due to another process running on the box, are all bets off on reliable transmission?
>
> I use an XA transaction to manage db and jms resources in an mdb where i take message, log a row in a db and pass it onto another jms queue.Whenever the server ran out of memory, i got a message about 'Unable to complete container managed transaction' and the message disappeared (ie it was consumed, and no message was sent on.)
>
> Is this expected behaviour? I would have expected the rollback to occur, but then again it was out of memory, and I suppose that may not have been possible?
>
Andy,
Even when there is an out of memory, data integrity is expected. What
about the DB update? Do you see that happening? Is your
transaction-service.automatic-recovery in the domain.xml set to true? If
not, when you restart the server, you should observe the data consistency.
regards
sankar
> Regards,
> Andy
> [Message sent by forum member 'andymorton' (andymorton)]
>
> http://forums.java.net/jive/thread.jspa?messageID=296919
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>