|
From: Hubert F. <hub...@ab...> - 2007-05-22 13:26:36
|
For some reason my question was placed in the wrong discussion, so I resend it: Where is the correct place to stop the WrapperActionServer? I use implementation method 3. I initialize WrapperActionServer in the start() method and stop it by calling the WrapperActionServer int the stop() method. If I don't call the stop method, wrapper behaves good if I request shutdown or restart using WrapperActionServer with telnet. If I call WrapperActionServer.stop() , the process hangs. Last thing I see is "WrapperListener.stop runner thread started." Can anybody please help? Hubert INFO | jvm 1 | 2007/05/21 10:32:09 | WrapperManager Debug: WrapperManager.stop(0) called by thread: WrapperActionServer_runner INFO | jvm 1 | 2007/05/21 10:32:09 | WrapperManager Debug: Send a packet STOP : 0 DEBUG | wrapperp | 2007/05/21 10:32:09 | read a packet STOP : 0 DEBUG | wrapper | 2007/05/21 10:32:09 | JVM requested a shutdown. (0) DEBUG | wrapper | 2007/05/21 10:32:09 | wrapperStopProcess(0) called. DEBUG | wrapper | 2007/05/21 10:32:09 | Sending stop signal to JVM DEBUG | wrapperp | 2007/05/21 10:32:09 | send a packet STOP : NULL INFO | jvm 1 | 2007/05/21 10:32:09 | WrapperManager Debug: Received a packet STOP : INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug: Thread, WrapperActionServer_runner, handling the shutdown process. INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug: calling listener.stop() INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug: Waiting for WrapperListener.stop runner thread to complete. INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug: WrapperListener.stop runner thread started. ________________________________________ ABACUS User Conference 2007 ABACUS Business Software: Next Generation Donnerstag, 14. oder Freitag, 15. Juni 2007 Anmeldung unter: www.abacus.ch |
|
From: Leif M. <le...@ta...> - 2007-05-24 06:49:23
|
Hubert,
This is a bug. The problem is that the WrapperActionServer stop
method blocks for the termination of the runner thread handling
incoming commands. That runner thread is in turn blocking in
WrapperManager.stop for the JVM to shutdown.
I have fixed this by making use of the WrapperManager.
stopAndReturn method. The same problem exists with the the
restart action.
This has been fixed for the next release.
In the mean time however, you should be able to simply omit
the call to WrapperActionServer.stop. The JVM should then
shutdown correctly. Were having any problems if this was not
called?
Cheers,
Leif
Hubert Felber wrote:
> For some reason my question was placed in the wrong discussion, so I
> resend it:
>
> Where is the correct place to stop the WrapperActionServer?
>
> I use implementation method 3.
> I initialize WrapperActionServer in the start() method and stop it by
> calling the WrapperActionServer int the stop() method.
>
> If I don't call the stop method, wrapper behaves good if I request
> shutdown or restart using WrapperActionServer with telnet.
> If I call WrapperActionServer.stop() , the process hangs. Last thing I
> see is "WrapperListener.stop runner thread started."
>
> Can anybody please help?
> Hubert
>
> INFO | jvm 1 | 2007/05/21 10:32:09 | WrapperManager Debug:
> WrapperManager.stop(0) called by thread: WrapperActionServer_runner
> INFO | jvm 1 | 2007/05/21 10:32:09 | WrapperManager Debug: Send a
> packet STOP : 0
> DEBUG | wrapperp | 2007/05/21 10:32:09 | read a packet STOP : 0
> DEBUG | wrapper | 2007/05/21 10:32:09 | JVM requested a shutdown.
> (0)
> DEBUG | wrapper | 2007/05/21 10:32:09 | wrapperStopProcess(0)
> called.
> DEBUG | wrapper | 2007/05/21 10:32:09 | Sending stop signal to JVM
> DEBUG | wrapperp | 2007/05/21 10:32:09 | send a packet STOP : NULL
> INFO | jvm 1 | 2007/05/21 10:32:09 | WrapperManager Debug:
> Received a packet STOP :
> INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug:
> Thread,
> WrapperActionServer_runner, handling the shutdown process.
> INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug:
> calling
> listener.stop()
> INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug:
> Waiting
> for WrapperListener.stop runner thread to complete.
> INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug:
> WrapperListener.stop runner thread started.
>
>
>
>
> ________________________________________
> ABACUS User Conference 2007
> ABACUS Business Software: Next Generation
> Donnerstag, 14. oder Freitag, 15. Juni 2007
> Anmeldung unter: www.abacus.ch
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
|
|
From: Hubert F. <hub...@ab...> - 2007-05-24 07:52:20
|
Leif,
Thanks for fixing this :-)
No there weren 't any problems omitting the stop. The JVM shot down
correctly.
Thank you
Hubert
>>> Leif Mortenson <le...@ta...> 24.05.2007 08:49 >>>
Hubert,
This is a bug. The problem is that the WrapperActionServer stop
method blocks for the termination of the runner thread handling
incoming commands. That runner thread is in turn blocking in
WrapperManager.stop for the JVM to shutdown.
I have fixed this by making use of the WrapperManager.
stopAndReturn method. The same problem exists with the the
restart action.
This has been fixed for the next release.
In the mean time however, you should be able to simply omit
the call to WrapperActionServer.stop. The JVM should then
shutdown correctly. Were having any problems if this was not
called?
Cheers,
Leif
Hubert Felber wrote:
> For some reason my question was placed in the wrong discussion, so I
> resend it:
>
> Where is the correct place to stop the WrapperActionServer?
>
> I use implementation method 3.
> I initialize WrapperActionServer in the start() method and stop it
by
> calling the WrapperActionServer int the stop() method.
>
> If I don't call the stop method, wrapper behaves good if I request
> shutdown or restart using WrapperActionServer with telnet.
> If I call WrapperActionServer.stop() , the process hangs. Last thing
I
> see is "WrapperListener.stop runner thread started."
>
> Can anybody please help?
> Hubert
>
> INFO | jvm 1 | 2007/05/21 10:32:09 | WrapperManager Debug:
> WrapperManager.stop(0) called by thread: WrapperActionServer_runner
> INFO | jvm 1 | 2007/05/21 10:32:09 | WrapperManager Debug: Send
a
> packet STOP : 0
> DEBUG | wrapperp | 2007/05/21 10:32:09 | read a packet STOP : 0
> DEBUG | wrapper | 2007/05/21 10:32:09 | JVM requested a shutdown.
> (0)
> DEBUG | wrapper | 2007/05/21 10:32:09 | wrapperStopProcess(0)
> called.
> DEBUG | wrapper | 2007/05/21 10:32:09 | Sending stop signal to JVM
> DEBUG | wrapperp | 2007/05/21 10:32:09 | send a packet STOP : NULL
> INFO | jvm 1 | 2007/05/21 10:32:09 | WrapperManager Debug:
> Received a packet STOP :
> INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug:
> Thread,
> WrapperActionServer_runner, handling the shutdown process.
> INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug:
> calling
> listener.stop()
> INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug:
> Waiting
> for WrapperListener.stop runner thread to complete.
> INFO | jvm 1 | 2007/05/21 10:32:10 | WrapperManager Debug:
> WrapperListener.stop runner thread started.
>
>
>
>
> ________________________________________
> ABACUS User Conference 2007
> ABACUS Business Software: Next Generation
> Donnerstag, 14. oder Freitag, 15. Juni 2007
> Anmeldung unter: www.abacus.ch
>
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user
________________________________________
ABACUS User Conference 2007
ABACUS Business Software: Next Generation
Donnerstag, 14. oder Freitag, 15. Juni 2007
Anmeldung unter: www.abacus.ch
|