[
https://issues.apache.org/jira/browse/DAEMON-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859863#action_12859863
]
Mladen Turk commented on DAEMON-156:
------------------------------------
The example application is faulty
Turn on debug logging and you will see:
[2010-04-22 18:04:58] [debug] ( prunsrv.c:1413) Commons Daemon procrun log
initialized
[2010-04-22 18:04:58] [info] Commons Daemon procrun (1.0.3.0) started
[2010-04-22 18:04:58] [info] Running 'ProcrunServiceJvm' Service...
[2010-04-22 18:04:58] [debug] ( prunsrv.c:1190) Inside ServiceMain...
[2010-04-22 18:04:58] [info] Starting service...
[2010-04-22 18:04:58] [debug] ( javajni.c:456 ) Jvm Option[0]
-Djava.class.path=C:\wrkplace\daemon\trunk\src\samples\ProcrunService.jar
[2010-04-22 18:04:58] [debug] ( javajni.c:665 ) Java Worker thread started
ProcrunService:start
[2010-04-22 18:04:58] [debug] ( javajni.c:675 ) Java Worker thread
ProcrunService:start finished
[2010-04-22 18:04:58] [debug] ( javajni.c:679 ) Java Worker thread finished
ProcrunService:start
[2010-04-22 18:04:59] [debug] ( prunsrv.c:1010) Java started ProcrunService
[2010-04-22 18:04:59] [info] Service started in 1046 ms.
[2010-04-22 18:04:59] [debug] ( prunsrv.c:1297) Waiting for worker to finish...
[2010-04-22 18:04:59] [debug] ( prunsrv.c:1302) Worker finished.
[2010-04-22 18:04:59] [debug] ( prunsrv.c:1325) Waiting for all threads to exit
This means that the procrun reported services as stopped immediately after it
was started.
The start() method for procrun MUST not return until stop() has been called.
I agreed that crash is nasty, and should probably be investigated further, but
currently it's not a blocker
> Prunsrv crashes with access violation when stopping service
> -----------------------------------------------------------
>
> Key: DAEMON-156
> URL: https://issues.apache.org/jira/browse/DAEMON-156
> Project: Commons Daemon
> Issue Type: Bug
> Components: Procrun
> Affects Versions: 1.0.2
> Reporter: Sebb
>
> The prunsrv.exe application crashes with an access violation during the final
> stages of jvm-mode service shutdown, after the service class stop method has
> been invoked.
> To reproduce, use the ProcrunService example, installed using
> ProcrunServiceInstall; start and then stop the service.
> There should be an entry in the Dr Watson directory, and an Application
> Failed dialogue box will appear.
> I don't know yet if the problem also occurs with Java or Exe mode shutdown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
