Instead of a shutdown hook I would recommend using Mule's lifecycle, as at least there's a better control of the shutdown order (nothing is guaranteed for runtime JVM hooks).
I think this topic emerged before, so I filed a
http://mule.mulesource.org/jira/browse/MULE-2479 , you can put a watch on it. Note, however, I'm reluctant to change the API in 1.4.x for backwards compatibility, so for now it'll be in
2.x.
For the time being you can achieve the same by registering a proper listener on the MuleManager, e.g. on 'models stopped' events.
Andrew
On 10/4/07,
JURZAK Theotime <theotime.jurzak@...> wrote:
Hi Andrew,
Thanks to reply.
The problem is my transaction monitor
(atomikos) is already shutdown. It has a shutdown hook and checking logs, i see
that when rollback is called, it's stopped.
I let you know if i find something.
Theotime
De : Andrew
Perepelytsya [mailto:aperepel@...]
Envoyé : mercredi 3
octobre 2007 17:56
À : user@...
Objet : Re: [mule-user] Mule
shudown with jms and xa
XA transacted receiver polls queue for new messages in transaction.
When you shutdown the server those polling threads give you the message.
Andrew
