You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "M.G. (JIRA)" <ji...@apache.org> on 2011/04/11 14:27:05 UTC
[jira] [Created] (DAEMON-203) unexpected procrun exit (Console
LOGOFF event signaled )
unexpected procrun exit (Console LOGOFF event signaled )
--------------------------------------------------------
Key: DAEMON-203
URL: https://issues.apache.org/jira/browse/DAEMON-203
Project: Commons Daemon
Issue Type: Bug
Components: Procrun
Affects Versions: 1.0.5, 1.0.4
Environment: Procun is used in a Windows 2003 server to manage a java application.
Reporter: M.G.
The service is installed using a command like the following:
agent.exe //IS//agent --Install=c:\agentpath\bat\agent.exe --Description="agent" --Classpath=[[all the needed jars]] --JvmMs=10 --JvmMx=512 --Jvm=%JREPATH:\=/%\bin\client\jvm.dll --StartMode=java --StartClass=the.agent.start.class --StartMethod=start --StopClass=the.agent.stop.class --StopMethod=stop --LogPath=c:\log\agent\ --StdOutput=c:\log\agent\service-stdout.log --StdError=c:\log\agent\service-stderr.log --LogLevel=DEBUG
The application is started using NET START and works fine.
Sometimes, the application catch a LOGOFF event and stops itself as you can see on the following log:
{noformat}
[2011-04-11 05:01:38] [debug] ( prunsrv.c:1494) Commons Daemon procrun log initialized
[2011-04-11 05:01:38] [info] ( :0 ) Commons Daemon procrun (1.0.5.0 32-bit) started
[2011-04-11 05:01:38] [info] ( :0 ) Running 'agent' Service...
[2011-04-11 05:01:38] [debug] ( prunsrv.c:1246) Inside ServiceMain...
[2011-04-11 05:01:38] [info] ( :0 ) Starting service...
[2011-04-11 05:01:38] [info] ( :0 ) Service started in 46 ms.
[2011-04-11 05:01:40] [debug] ( prunsrv.c:1369) Waiting for worker to finish...
[2011-04-11 10:27:05] [info] ( :0 ) Console LOGOFF event signaled
[2011-04-11 10:27:05] [info] ( :0 ) Console LOGOFF event signaled
[2011-04-11 10:27:06] [debug] ( prunsrv.c:1374) Worker finished.
[2011-04-11 10:27:06] [debug] ( prunsrv.c:1397) Waiting for all threads to exit
[2011-04-11 10:27:06] [debug] ( prunsrv.c:1401) JVM destroyed.
[2011-04-11 10:27:06] [info] ( :0 ) Run service finished.
[2011-04-11 10:27:06] [info] ( :0 ) Commons Daemon procrun finished
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DAEMON-203) unexpected procrun exit (Console
LOGOFF event signaled )
Posted by "Mladen Turk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DAEMON-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mladen Turk resolved DAEMON-203.
--------------------------------
Resolution: Invalid
In your example you are using --StartMode=java which will cause to spawn a separate java.exe process. In that case you will need to pass the -Xrs to that process so it doesn't get killed on logoff. Or I suppose you probably meant to use the --StartMode=jvm since you have --Jvm param.
Anyhow, Jira is not support forum so make further discussion on commons users list with [DAEMON] subject prefix.
> unexpected procrun exit (Console LOGOFF event signaled )
> --------------------------------------------------------
>
> Key: DAEMON-203
> URL: https://issues.apache.org/jira/browse/DAEMON-203
> Project: Commons Daemon
> Issue Type: Bug
> Components: Procrun
> Affects Versions: 1.0.4, 1.0.5
> Environment: Procun is used in a Windows 2003 server to manage a java application.
> Reporter: M.G.
>
> The service is installed using a command like the following:
> agent.exe //IS//agent --Install=c:\agentpath\bat\agent.exe --Description="agent" --Classpath=[[all the needed jars]] --JvmMs=10 --JvmMx=512 --Jvm=%JREPATH:\=/%\bin\client\jvm.dll --StartMode=java --StartClass=the.agent.start.class --StartMethod=start --StopClass=the.agent.stop.class --StopMethod=stop --LogPath=c:\log\agent\ --StdOutput=c:\log\agent\service-stdout.log --StdError=c:\log\agent\service-stderr.log --LogLevel=DEBUG
> The application is started using NET START and works fine.
> Sometimes, the application catch a LOGOFF event and stops itself as you can see on the following log:
> {noformat}
> [2011-04-11 05:01:38] [debug] ( prunsrv.c:1494) Commons Daemon procrun log initialized
> [2011-04-11 05:01:38] [info] ( :0 ) Commons Daemon procrun (1.0.5.0 32-bit) started
> [2011-04-11 05:01:38] [info] ( :0 ) Running 'agent' Service...
> [2011-04-11 05:01:38] [debug] ( prunsrv.c:1246) Inside ServiceMain...
> [2011-04-11 05:01:38] [info] ( :0 ) Starting service...
> [2011-04-11 05:01:38] [info] ( :0 ) Service started in 46 ms.
> [2011-04-11 05:01:40] [debug] ( prunsrv.c:1369) Waiting for worker to finish...
> [2011-04-11 10:27:05] [info] ( :0 ) Console LOGOFF event signaled
> [2011-04-11 10:27:05] [info] ( :0 ) Console LOGOFF event signaled
> [2011-04-11 10:27:06] [debug] ( prunsrv.c:1374) Worker finished.
> [2011-04-11 10:27:06] [debug] ( prunsrv.c:1397) Waiting for all threads to exit
> [2011-04-11 10:27:06] [debug] ( prunsrv.c:1401) JVM destroyed.
> [2011-04-11 10:27:06] [info] ( :0 ) Run service finished.
> [2011-04-11 10:27:06] [info] ( :0 ) Commons Daemon procrun finished
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira