[ 
https://issues.apache.org/jira/browse/DAEMON-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408882#comment-17408882
 ] 

Steve Hofmeyr commented on DAEMON-336:
--------------------------------------

Hi [~markt] - I believe i have gotten to the bottom of our cause for this 
issue. Our use-case is using Jetty from eclipse with the Daemon, and the code 
that i found called join() after the stop() not after the start() (as shown in 
Eclipses own sample code). Let me know if you think the following is enough to 
reproduce the issue and then we can at least get Daemon to be a bit safer going 
forward, otherwise i can close the PR and let this be a lesson to anyone else 
who finds it or at least the PR will help them debug the issue for themselves.

{code:java}
        public void start() throws Exception {
                server.start();
                server.join();
        }

        public void stop() throws Exception {
                if (server != null) {
                        server.stop();
                        server = null;
                }
        }
{code}

> prunsrv crash on service stop
> -----------------------------
>
>                 Key: DAEMON-336
>                 URL: https://issues.apache.org/jira/browse/DAEMON-336
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Procrun
>    Affects Versions: 1.0.15
>         Environment: Windows 8.1 with Java 8 64bit, Java mode
>            Reporter: Volker Berlin
>            Priority: Major
>
> If the service should be stop then it crash. In the event log you can see:
> Name der fehlerhaften Anwendung: foo-serverService.exe, Version: 1.0.15.0, 
> Zeitstempel: 0x51543b9d
> Name des fehlerhaften Moduls: ntdll.dll, Version: 6.3.9600.17736, 
> Zeitstempel: 0x550f4336
> Ausnahmecode: 0xc0000005
> Fehleroffset: 0x0000000000035150
> ID des fehlerhaften Prozesses: 0x1578
> Startzeit der fehlerhaften Anwendung: 0x01d0be119603c23f
> Pfad der fehlerhaften Anwendung: C:\Program Files\foo 
> Server\foo-serverService.exe
> Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
> Berichtskennung: da5b2537-2a04-11e5-8063-7427ea3e8675
> Vollständiger Name des fehlerhaften Pakets: 
> Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to