[
https://issues.apache.org/jira/browse/DAEMON-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Barnard updated DAEMON-405:
-------------------------------
Description:
I have a Windows 10 x64 service created with this command (run in a command
window which says "Administrator: Command Prompt"):
prunsrv //IS//IBMJL --Startup=manual --DisplayName="IBM Jazz on Liberty"
--Description="IBM Jazz on Liberty" ++DependsOn=Tcpip
--LogPath=C:\IBM\JazzTeamServer\server\logs --StdOutput=auto --StdError=auto
--StartMode=exe --StartPath=C:\IBM\JazzTeamServer\server
--StartImage=C:\IBM\JazzTeamServer\server\server.startup.bat --StopMode=exe
--StopPath=C:\IBM\JazzTeamServer\server
--StopImage=C:\IBM\JazzTeamServer\server\server.shutdown.bat
The two batch files start/stop IBM Jazz running in Websphere Liberty Profile.
The service can be succesfully started by
NET START IBMJL
And in the Windows Services this is initially shown as Running but then that
status disappears (which I think means that Services doesn't think the IBMJL is
running, but Liberty is still active and usable), and using
NET STOP IBMJL
doesn't work at all, says the service isn't running. I can force Liberty to
stop manually by running the server.shutdown.bat.
The generated logs show the startup, but there is nothing at all for the
attempted shutdown of the service.
This *precise* same service definition works fine (and has done for a long
time) on Server 2012R2 and on Server 2016.
I tried both 1.1.0 and 1.2.0, and I tried both x32 and x64 builds of prunsrv,
no better.
I don't know how to debug this - I don't have a workaround which lets me run
this my service on Windows 10, but for my particular deployment that doesn't
actually matter, so I set this bug to Minor.
was:
I have a Windows 10 x64 service created with:
prunsrv //IS//IBMJL --Startup=manual --DisplayName="IBM Jazz on Liberty"
--Description="IBM Jazz on Liberty" ++DependsOn=Tcpip
--LogPath=C:\IBM\JazzTeamServer\server\logs --StdOutput=auto --StdError=auto
--StartMode=exe --StartPath=C:\IBM\JazzTeamServer\server
--StartImage=C:\IBM\JazzTeamServer\server\server.startup.bat --StopMode=exe
--StopPath=C:\IBM\JazzTeamServer\server
--StopImage=C:\IBM\JazzTeamServer\server\server.shutdown.bat
The two batch files start/stop IBM Jazz running in Websphere Liberty Profile.
The service can be succesfully started by
NET START IBMJL
And in the Windows Services this is initially shown as Running but then that
status disappears (which I think means that Services doesn't think the IBMJL is
running, but Liberty is still active and usable), and using
NET STOP IBMJL
doesn't work at all, says the service isn't running. I can force Liberty to
stop manually by running the server.shutdown.bat.
The generated logs show the startup, but there is nothing at all for the
attempted shutdown of the service.
This *precise* same service definition works fine (and has done for a long
time) on Server 2012R2 and on Server 2016.
I tried both 1.1.0 and 1.2.0, and I tried both x32 and x64 builds of prunsrv,
no better.
I don't know how to debug this - I don't have a workaround which lets me run
this my service on Windows 10, but for my particular deployment that doesn't
actually matter, so I set this bug to Minor.
> On Windows 10, an exe service starts but its status stops being shown as
> Running and service stop doesn't work
> --------------------------------------------------------------------------------------------------------------
>
> Key: DAEMON-405
> URL: https://issues.apache.org/jira/browse/DAEMON-405
> Project: Commons Daemon
> Issue Type: Bug
> Components: Procrun
> Affects Versions: 1.1.0, 1.2.0
> Reporter: Ian Barnard
> Priority: Minor
>
> I have a Windows 10 x64 service created with this command (run in a command
> window which says "Administrator: Command Prompt"):
> prunsrv //IS//IBMJL --Startup=manual --DisplayName="IBM Jazz on Liberty"
> --Description="IBM Jazz on Liberty" ++DependsOn=Tcpip
> --LogPath=C:\IBM\JazzTeamServer\server\logs --StdOutput=auto --StdError=auto
> --StartMode=exe --StartPath=C:\IBM\JazzTeamServer\server
> --StartImage=C:\IBM\JazzTeamServer\server\server.startup.bat --StopMode=exe
> --StopPath=C:\IBM\JazzTeamServer\server
> --StopImage=C:\IBM\JazzTeamServer\server\server.shutdown.bat
> The two batch files start/stop IBM Jazz running in Websphere Liberty Profile.
> The service can be succesfully started by
> NET START IBMJL
> And in the Windows Services this is initially shown as Running but then that
> status disappears (which I think means that Services doesn't think the IBMJL
> is running, but Liberty is still active and usable), and using
> NET STOP IBMJL
> doesn't work at all, says the service isn't running. I can force Liberty to
> stop manually by running the server.shutdown.bat.
> The generated logs show the startup, but there is nothing at all for the
> attempted shutdown of the service.
> This *precise* same service definition works fine (and has done for a long
> time) on Server 2012R2 and on Server 2016.
> I tried both 1.1.0 and 1.2.0, and I tried both x32 and x64 builds of prunsrv,
> no better.
> I don't know how to debug this - I don't have a workaround which lets me run
> this my service on Windows 10, but for my particular deployment that doesn't
> actually matter, so I set this bug to Minor.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
