It looks like, as per Daniel's post, you may find that things improve if
you upgrade your Mule version.
One other thing to watch out for is what happens when Mule stops - if it
doesn't have enough time to persist the data (or if a Fatal exception prevents
persisting), then the persistence strategy won't help.
HTH
Antoine Borg, Senior Consultant | Tel:
+32 28 504
696
ricston Ltd., BP 2, 1180 Uccle, Brussels,
BELGIUM
I use the version 2.0.2
Youkoun
2008/10/5 Daniel Feist
<dfeist@...>
What version of Mule is this, there were some issues with persistence in
early versions of 2.0..
Dan
On Oct 3, 2008, at 9:17 AM, bokc bokc wrote:
Hi,
Some time, my Mule wrapper restart the JVM it
self :
JVM appears hung: Timed out waiting for signal from
JVM.
JVM did not exit on request, terminated
Launching a
JVM...
Starting the Mule Server...
Wrapper (Version 3.2.3)
http://wrapper.tanukisoftware.org Copyright
1999-2006 Tanuki Software, Inc. All Rights Reserved.
But the VM
persistent don't running. treatments are stop and when the JVM restart,
treatments are not running again.
In my Mule configuration I put yet :
<queue-profile persistent="true"
maxOutstandingMessages="1000"/>
What I have to do for stopping the
restart of JVM or make good
persistence?
Youkoun
