[esb-java-user] My ESB will shutdown automatically after 24 hours

[unmou]

Hi all,

I have encountered a problem...
I'm using ESB 1.7
I found out that after 24 hours,
It shut down automatically
I have no idea what happened to it
I've attached the log file
Can anyone help me with this?
Thanks so much!!!

Fanny

http://www.nabble.com/file/p18561475/wso2-esb.log.20080719
wso2-esb.log.20080719

[Asankha C. Perera]

Hi Fanny

Post by unmou
I have encountered a problem...
I'm using ESB 1.7
I found out that after 24 hours,
It shut down automatically
I have no idea what happened to it
I've attached the log file
Can anyone help me with this?

The WSO2 ESB is used in production environments 24x7 at customer
locations and it does not have any issues as you report regarding an
automatic shutdown. This seems to be triggered by some external factor
which killed your JVM, as can be seen by the following log snippet,
where the shutdown is initiated by the JVM shutdown hook

2008-07-19 17:47:47,429 [-] [*WSO2 ESB Shutdown Hook*] INFO ServiceBusManager Stopping the WSO2 Enterprise Service Bus..
2008-07-19 17:47:47,429 [-] [WSO2 ESB Shutdown Hook] INFO StatisticsReporterThread Statistics reporter thread is being stopped
...
2008-07-19 17:47:47,703 [-] [WSO2 ESB Shutdown Hook] INFO ServiceBusManager [ESB] Stop request completed
2008-07-19 17:47:47,703 [-] [WSO2 ESB Shutdown Hook] INFO ServiceBusManager Shutting down the JMX connector
2008-07-19 17:47:47,721 [-] [WSO2 ESB Shutdown Hook] INFO ServiceBusManager [ESB] Shutdown completed
2008-07-19 17:47:47,721 [-] [WSO2 ESB Shutdown Hook] INFO ServiceBusManager [ESB] System will exit in approximately 3 seconds..


What is your OS and JVM (include exact versions)? Does the OS reboot
itself? Are there cron jobs etc that might shutdown the system? or..
even a Task that mistakenly calls System.exit() ?

asankha

[unmou]

hello asankha

I think instead of posting my reply here, I replied it to your email... :(
I'll post it again here

Post by Asankha C. Perera
Hi Fanny

Post by unmou
I have encountered a problem...
I'm using ESB 1.7
I found out that after 24 hours,
It shut down automatically
I have no idea what happened to it
I've attached the log file
Can anyone help me with this?

The WSO2 ESB is used in production environments 24x7 at customer
locations and it does not have any issues as you report regarding an
automatic shutdown. This seems to be triggered by some external factor
which killed your JVM, as can be seen by the following log snippet,
where the shutdown is initiated by the JVM shutdown hook
2008-07-19 17:47:47,429 [-] [*WSO2 ESB Shutdown Hook*] INFO
ServiceBusManager Stopping the WSO2 Enterprise Service Bus..
2008-07-19 17:47:47,429 [-] [WSO2 ESB Shutdown Hook] INFO
StatisticsReporterThread Statistics reporter thread is being stopped
...
2008-07-19 17:47:47,703 [-] [WSO2 ESB Shutdown Hook] INFO
ServiceBusManager [ESB] Stop request completed
2008-07-19 17:47:47,703 [-] [WSO2 ESB Shutdown Hook] INFO
ServiceBusManager Shutting down the JMX connector
2008-07-19 17:47:47,721 [-] [WSO2 ESB Shutdown Hook] INFO
ServiceBusManager [ESB] Shutdown completed
2008-07-19 17:47:47,721 [-] [WSO2 ESB Shutdown Hook] INFO
ServiceBusManager [ESB] System will exit in approximately 3 seconds..
What is your OS and JVM (include exact versions)? Does the OS reboot
itself? Are there cron jobs etc that might shutdown the system? or..
even a Task that mistakenly calls System.exit() ?
I'm using linux liunx 2.6.18-8.el5 #1 SMP and jdk is /jdk1.6.0_06
The OS didn't reboot itself that day
But from the log I found out that 15 min before ESB shut down
A task of cleaning the DB has performed
I'm thinking if it's that task that killed it or something else
asankha
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
_______________________________________________
Esb-java-user mailing list
Esb-java-user at wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

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

may I ask what will it happened after global timeout?
For the [Timer-1] log, does it mean that I have a message in the ESB for
86400 sec or what?

I'm new to ESB and I'm sorry that I have so many questions

Thanks!!

Fanny

[Paul Fremantle]

Post by unmou
I have another guess
since it shut down in 86400 sec
INFO TimeoutHandler This engine will expire all callbacks after
: 86400 seconds, irrespective of the timeout action, after the specified or
optional timeout
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.

Paul
--
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair
VP, Apache Synapse

Office: [phone]
Cell: [phone]

blog: http://pzf.fremantle.org
paul at wso2.com

"Oxygenating the Web Service Platform", www.wso2.com

[Asankha C. Perera]

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!

Post by Paul Fremantle

Post by unmou
I have another guess
since it shut down in 86400 sec
INFO TimeoutHandler This engine will expire all callbacks after
: 86400 seconds, irrespective of the timeout action, after the specified or
optional timeout
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]

Hi Fanny

Does the ESB restart at a particular time every day? If so, the culprit
could be an electrical power switch over, or the cleaner plugging your
system off for the vacuum etc :-) .. you never know!

http://message.snopes.com/showthread.php?p=675508
http://www.geekzone.co.nz/forums.asp?ForumId=65&TopicId=20245

asankha

[unmou]

Thanks asankha and Paul!!

I will try running ESB in another machine to see if the same problems occur
first

Thank you for all your advices!

Hope that I could fix this soon!

Fanny

Post by Asankha C. Perera
Hi Fanny
Does the ESB restart at a particular time every day? If so, the culprit
could be an electrical power switch over, or the cleaner plugging your
system off for the vacuum etc :-) .. you never know!
http://message.snopes.com/showthread.php?p=675508
http://www.geekzone.co.nz/forums.asp?ForumId=65&TopicId=20245
asankha
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
_______________________________________________
Esb-java-user mailing list
Esb-java-user at wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user