commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Stefl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DAEMON-296) Errors in log after stopping windows service
Date Tue, 30 Apr 2013 14:40:15 GMT

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

Jan Stefl commented on DAEMON-296:
----------------------------------

After setting logging level to Debug, behaviour was changed a little.

net stop EAP61SVC 
returns:
---------------------------------------------------------------------------
The JBoss Enterprise Application Server 6.1 service is stopping.
A system error has occurred.

System error 1067 has occurred.

The process terminated unexpectedly.

The JBoss Enterprise Application Server 6.1 service was stopped successfully.
---------------------------------------------------------------------------



And log contains
------------------------------------------------------------------------------------------
[2013-04-30 07:32:50] [debug] ( prunsrv.c:844 ) [ 2028] reportServiceStatusE: 4, 0, 0, 0
[2013-04-30 07:32:50] [debug] ( prunsrv.c:1528) [ 2028] Waiting for worker to finish...
[2013-04-30 07:32:50] [debug] ( prunsrv.c:1533) [ 2028] Worker finished.
[2013-04-30 07:32:50] [debug] ( prunsrv.c:1559) [ 2028] Waiting for all threads to exit
[2013-04-30 07:32:52] [debug] ( prunsrv.c:844 ) [ 5504] reportServiceStatusE: 4, 0, 0, 0
[2013-04-30 07:33:17] [debug] ( prunsrv.c:844 ) [ 5504] reportServiceStatusE: 3, 0, 3000,
0
[2013-04-30 07:33:17] [info]  ( prunsrv.c:943 ) [ 5548] Stopping service...
[2013-04-30 07:33:17] [debug] ( javajni.c:941 ) [ 4904] Java Worker thread started java/lang/System:exit
[2013-04-30 07:33:18] [debug] ( prunsrv.c:844 ) [ 5548] reportServiceStatusE: 3, 0, 20000,
0
[2013-04-30 07:33:18] [debug] ( javajni.c:471 ) [ 5276] Exit hook with exit code 0
[2013-04-30 07:33:18] 
------------------------------------------------------------------------------------------
                
> Errors in log after stopping windows service
> --------------------------------------------
>
>                 Key: DAEMON-296
>                 URL: https://issues.apache.org/jira/browse/DAEMON-296
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Procrun
>    Affects Versions: 1.0.15
>         Environment: Windows 2008, Windows 2008 R2
> 32/64b
>            Reporter: Jan Stefl
>
> I am able to start and stop Windows service with prunsrv.exe, but after stopping the
service the log contains errors:
> ------------------------------------------------------------------------------
> [2013-04-22 07:04:58] [info]  [ 6076] Commons Daemon procrun (1.0.15.0 32-bit) started
> [2013-04-22 07:04:58] [info]  [ 6076] Service EAP61SVC name JBoss Enterprise Application
Server 6.1
> [2013-04-22 07:04:59] [info]  [ 6076] Service 'EAP61SVC' installed
> [2013-04-22 07:04:59] [info]  [ 6076] Commons Daemon procrun finished
> [2013-04-22 07:04:59] [info]  [ 2632] Commons Daemon procrun (1.0.15.0 32-bit) started
> [2013-04-22 07:04:59] [info]  [ 2632] Updating service...
> [2013-04-22 07:04:59] [info]  [ 2632] Service 'EAP61SVC' updated
> [2013-04-22 07:04:59] [info]  [ 2632] Update service finished.
> [2013-04-22 07:04:59] [info]  [ 2632] Commons Daemon procrun finished
> [2013-04-22 07:06:01] [info]  [ 2496] Commons Daemon procrun (1.0.15.0 32-bit) started
> [2013-04-22 07:06:01] [info]  [ 2496] Running 'EAP61SVC' Service...
> [2013-04-22 07:06:01] [info]  [ 4376] Starting service...
> [2013-04-22 07:06:03] [info]  [ 4376] Service started in 1713 ms.
> [2013-04-22 07:06:43] [info]  [ 5820] Stopping service...
> [2013-04-22 07:06:44] [error] [ 5984] Failed to set service status
> [2013-04-22 07:06:44] [error] [ 5984] The handle is invalid.
> ------------------------------------------------------------------------------

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message