[jboss-jira] [JBoss JIRA] (WFCORE-1719) Wildfly 10.1.0.CR1 does not start as a windows service

[Cedric HENRY (Jira)]

    [ https://issues.redhat.com/browse/WFCORE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310623#comment-14310623 ] 

Cedric HENRY commented on WFCORE-1719:
--------------------------------------

Hello,

I have had to recently use Wildfly 10.1.0.Final as a Windows Service on Win 10) and meeting the Service Stop issue.

 

Out of curiosity, I have looked over the Internet about _Windows Service_ Stop timeout and found [https://www.coretechnologies.com/blog/windows-services/increase-shutdown-time/]. Based on its content, I have understood that _windows_ intends to stop the service in 20 seconds or less.

Furthermore,  I have seen in the Wildfly _service.bat_, the STOPARAM use the ':shutdown' CLI command, which may take some time  because it is a graceful shutdown...

 

As a first test, I have edited the batch file to use ':shutdown(timeout=20)', as well as ':shutdown(timeout=0)' for immediate shutdown, reinstalled the service and tried stopping the service on the Windows server.

Unfortunately and surprisingly to me, I got the same outcome about the service not responding in a timely fashion.

 

As a another test, hoping to get more information in the console, I have used: 
{code:java}
service.bat stop
{code}
The outcome is that the internal {{prunsrv.exe stop Wildfly}} lasts quite some time regardless of the shutdown timeout set, to end up with the message:
{code:java}
C:\JBoss_Wildfly\wildfly-10.1.0.Final\bin\service>service.bat stop
Using the X86-64bit version of prunsrv

Service Wildfly stopping...
ERROR: Failed to load service Wildfly configuration
{code}
 

Then, with service started, I have run the command meant to be ran on the service stop action.
{code:java}
C:\JBoss_Wildfly\wildfly-10.1.0.Final\bin>jboss-cli.bat --controller=localhost:9990 --connect --command=:shutdown
{"outcome" => "success"}
Press any key to continue . . .
{code}
Executing it results in having the stopped immediately.

What I have observed with that last test is:
 * the _server.log_ records the shutdown action in the logs when the CLI command is executed as-if, but
 * when the Windows Service stop action used, not such recording appears in _server.log_

 

My assumption is that the Windows Service stop action, or {{prunsrv.exe stop Wildfly}}, does not succeed to execute the Jboss CLI command (in STOPARAM  in _service.bat_) to shutdown JBoss... 

> Wildfly 10.1.0.CR1 does not start as a windows service
> ------------------------------------------------------
>
>                 Key: WFCORE-1719
>                 URL: https://issues.redhat.com/browse/WFCORE-1719
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Scripts
>    Affects Versions: 2.2.0.Final
>         Environment: Windows 8/Windows Server 2012
> Oracle Java 8
>            Reporter: Anton Yudin
>            Assignee: Tomaž Cerar
>            Priority: Major
>             Fix For: 3.0.0.Alpha6, 2.2.1.CR1
>
>         Attachments: screenshot-1.png
>
>
> Wildfly fails to start as a windows service.
> Installation works fine:
> {code}
> .\service.bat install
> Using the X86-64bit version of prunsrv
> "C:\applications\wildfly-10.1.0.CR1-test\bin\service\amd64\wildfly-service" install Wildfly  --DisplayName=WildFly --Description=""WildFly Application Server"" --LogLevel=INFO --LogPath="C:\applications\wildfly-10.1.0.CR1-test\standalone\log" --LogPrefix=service --StdOutput=auto --StdError=auto --StartMode=exe --Startup=manual --StartImage=cmd.exe --StartPath="C:\applications\wildfly-10.1.0.CR1-test\bin" ++StartParams="/c#set#NOPAUSE=Y#&&#standalone.bat#-Djboss.server.base.dir=C:\applications\wildfly-10.1.0.CR1-test\standalone#--server-config=standalone.xml" --StopMode=exe --StopImage=cmd.exe --StopPath="C:\applications\wildfly-10.1.0.CR1-test\bin"  ++StopParams="/c jboss-cli.bat --controller=localhost:9990 --connect  --command=:shutdown"
> Service Wildfly installed
> {code}
> Windows reports this error:
> {quote}
> Windows could not start the Wildfly on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code1.
> {quote}
> {code}
> Event log report:
> The Wildfly service terminated with the following service-specific error: 
> Incorrect function.
>   <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
>     <System>
>         <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager"/>
>         <EventID Qualifiers="49152">7024</EventID>
>         <Version>0</Version>
>         <Level>2</Level>
>         <Task>0</Task>
>         <Opcode>0</Opcode>
>         <Keywords>0x8080000000000000</Keywords>
>         <TimeCreated SystemTime="2016-08-13T21:40:42.402218400Z"/>
>         <EventRecordID>196500</EventRecordID>
>         <Correlation/>
>         <Execution ProcessID="668" ThreadID="10184"/>
>         <Channel>System</Channel>
>         <Computer>ITPC7.intra.rfgh.net</Computer>
>         <Security/>
>     </System>
>     -
>     <EventData>
>         <Data Name="param1">Wildfly</Data>
>         <Data Name="param2">%%1</Data>
>         <Binary>570069006C00640066006C0079000000</Binary>
>     </EventData>
> </Event>
> {code}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)