Menu
▾
▴
#56 warpper just stops - no other information
We have been running two services using the wrapper for
several months. On 31/08/2004 16:30:14, one of the
wrappers just stopped. Output:
jvm 1 | 2004/08/31 16:20:00 | [main] INFO - New
file '2004-08-24 13:11:09|PDET_DONE.999999;2235'
jvm 1 | 2004/08/31 16:20:01 | [main] INFO - Copied
jvm 1 | 2004/08/31 16:20:01 | [main] INFO - New
file '2004-08-24 13:14:31|PDET_DONE.999999;2236'
jvm 1 | 2004/08/31 16:20:01 | [main] INFO - Copied
jvm 1 | 2004/08/31 16:20:01 | [main] INFO - New
file '2004-08-24 13:21:28|PDET_DONE.999999;2237'
jvm 1 | 2004/08/31 16:20:01 | [main] INFO - Copied
wrapper | 2004/08/31 16:20:14 | <-- Wrapper Stopped
On 31/08/2004 17:46:48, the other wrapper just stopped.
Output:
jvm 1 | 2004/08/31 16:16:46 | [main] INFO - New
file '2004-08-31 16:14:56|S40A03162F_20040831161456.xml'
jvm 1 | 2004/08/31 16:16:46 | [main] INFO - Copied
jvm 1 | 2004/08/31 16:16:46 | [main] INFO -
Transfer ended: scout
jvm 1 | 2004/08/31 16:16:46 | [main] INFO - Files
copied: 82
jvm 1 | 2004/08/31 16:45:46 | [main] INFO -
jvm 1 | 2004/08/31 16:45:46 | [main] INFO -
Transfer initiated: scout
jvm 1 | 2004/08/31 16:46:32 | [main] DEBUG - files: 5969
jvm 1 | 2004/08/31 17:46:46 |
wrapper | 2004/08/31 17:46:48 | <-- Wrapper Stopped
The times are in Melbourne/Australia local time.
We are using version 3.1.0 and running on Windows NT SP6.
I am fairly ceratain they are not explicit user stop
requests because I display such requests to the log. Eg.
jvm 1 | 2004/09/02 11:09:09 | Wrapper (Version
3.1.0) http://wrapper.tanukisoftware.org
jvm 1 | 2004/09/02 11:09:09 |
jvm 1 | 2004/09/02 11:09:10 | [main] INFO -
FileTransfer Version 0.85 started
jvm 1 | 2004/09/02 11:09:10 | [main] INFO -
jvm 1 | 2004/09/02 11:09:10 | [main] DEBUG - Loading
database into memory: elads.db
jvm 1 | 2004/09/02 11:09:10 | [main] DEBUG -
Database loaded - 14689 entries
jvm 1 | 2004/09/02 11:20:41 | [stop] INFO - Stop
request received
jvm 1 | 2004/09/02 11:20:41 | [stop] INFO -
Application ended
jvm 1 | 2004/09/02 11:20:41 |
wrapper | 2004/09/02 11:20:41 | <-- Wrapper Stopped
This may be related to 1014405 except the log output is
different.
Sam
Logged In: YES
user_id=228081
Sam,
If the Wrapper decided to shutdown due to a timeout of any
kind then it would have displayed a log entry. The Wrapper
appears to think that it is shutting down normally.
This can happen for one of a couple of reasons.
1) The application calls System.exit, or WrapperManager.stop.
2) All non daemon threads have completed.
If you enable debug output by setting wrapper.debug=true
then I would be able to tell you the exact cause of the
shutdown by viewing the log.
The two server shutdowns do not happen at the same time. So
I doubt that this is a timer related problem like the
1014405 issue.
If you set the system clock back to run through that time
period again, does the server shutdown again or does it
continue normally? I will need to see the debug output
before I can do much more than guess.
Cheers,
Leif
Logged In: NO
Hi Leif.
I haven't tried running it past the same system clock period
as it seems doubtful thats its a 1014405 problem.
The problem has only happened once in the several months
that the application ran.
I've decided to go with the next release so this issue can
be closed if you like.
Thanks
Sam
Logged In: NO
Hi Leif.
I haven't tried running it past the same system clock period
as it seems doubtful thats its a 1014405 problem.
The problem has only happened once in the several months
that the application ran.
I've decided to go with the next release so this issue can
be closed if you like.
Thanks
Sam
Logged In: YES
user_id=228081
Sam,
My only guess right now is that your app asked the JVM to
quit or the last non-daemon thread exit. So I'll go ahead
and close this off as you suggested. If you see any future
problems, please let me know though.
Cheers,
Leif