commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mladen Turk (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DAEMON-195) "net stop serviceName" prints "Error 109: The pipe has been ended." Stopping via Windows Control Panel hangs.
Date Sat, 05 Nov 2011 18:46:51 GMT

     [ https://issues.apache.org/jira/browse/DAEMON-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mladen Turk resolved DAEMON-195.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.8

Seems the fix was really trivial.
Instead waiting on stop thread to finish, return control immediately to the service control
manager.
This prevents broken pipe messages if start or stop method calls System.exit
                
> "net stop serviceName" prints "Error 109: The pipe has been ended." Stopping via Windows
Control Panel hangs.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: DAEMON-195
>                 URL: https://issues.apache.org/jira/browse/DAEMON-195
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Procrun
>    Affects Versions: 1.0.5
>         Environment: WinXP SP3 32-bit
>            Reporter: Konstantin Kolinko
>            Priority: Minor
>             Fix For: 1.0.8
>
>
> This issue was reported for Tomcat 7.0.6: https://issues.apache.org/bugzilla/show_bug.cgi?id=50673
> To reproduce:
> 1. Install apache-tomcat-7.0.6.exe   I am installing with default options. I am not starting
Tomcat after installation.
> 2. Launch the command prompt window.
> 3. The following command succeeds:
> net stop Tomcat7
> It prints two localized messages that can be translated as
> The "Apache Tomcat 7" service is being started.
> The "Apache Tomcat 7" service started successfully.p
> 4. The following command apparently fails, but actually it succeeds:
> net stop Tomcat7
> It prints two localized messages that are, citing from BZ 50673:
> System error 109.
> The pipe has been ended.
> Note that "The service being stopped" message is not printed.
> 5. Repeating the command shows that the service has been stopped:
> net stop Tomcat7
> The "Apache Tomcat 7" service has not been started.
> The commons-daemon.<date>.log contains only the following four lines when stopping
the service with Debug logging enabled:
> [2011-01-27 20:18:59] [info]  (          :0   ) Stopping service...
> [2011-01-27 20:18:59] [debug] ( javajni.c:844 ) argv[0] = stop
> [2011-01-27 20:18:59] [debug] ( javajni.c:891 ) Java Worker thread started org/apache/catalina/startup/Bootstrap:main
> [2011-01-27 20:19:00] [debug] ( prunsrv.c:871 ) Waiting for java jni stop worker to finish...
> Stopping the service with Stop button in prunmgr app succeeds without any messages.
> Stopping the service from the Services list in the Control Panel quickly goes to 50%
of progress but then continues to wait forever, without any changes on the screen.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message