Hi Fanny
I totally missed the bottom half of your email :-) .. and was wondering
what was happening.. luckily Paul's message made me notice your reply!
Paul Fremantle wrote:
I have another guess
since it shut down in 86400 sec
I wonder is there anything due with this two log:
INFO TimeoutHandler This engine will expire all callbacks after
: 86400 seconds, irrespective of the timeout action, after the specified or
optional timeout
[Timer-1] WARN TimeoutHandler Expiring message ID :
urn:uuid:80D551713EF82B30717010673804263801284483447
; dropping message after global timeout of : 86400 seconds
This means that you had a response handler that never got a response. I
can only imagine you had a one-way message but you did not let the ESB
know that the flow is one-way by setting the OUT_ONLY property.
This really has nothing to do with your JVM shutdown though.
Yes, the timeout is a mechanism to not wait forever leaking memory, for
a reply which will probably never come. This has nothing to do with the
JVM restart. Can I suggest that you run the same configuration in
another machine? Maybe your office desktop or home computer etc.. and
check if the restart can still be seen.. you may also run the ESB
without your custom code/tasks etc and leave it for a couple of days to
see if the problem lies elsewhere
asankha
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
