[
https://issues.jboss.org/browse/WFLY-3149?page=com.atlassian.jira.plugin....
]
Nicklas Karlsson commented on WFLY-3149:
----------------------------------------
I'm still seeing this issue on a WF10/JDK8/64b Windows Server 2008 (working on my Win8
64/JDK dev machine, though)
It installs as localservice with
"C:\WF\bin\service\amd64\wildfly-service" install WF
--DisplayName="WF" --Description "WF" --LogLevel=DEBUG
--LogPath="C:\WF\standalone\log" --LogPrefix=service --
StdOutput=auto --StdError=auto --StartMode=exe --StartImage=cmd.exe
--StartPath="C:\WF\bin" ++StartParams="/c \"set NOPAUSE=Y &&
standalone.bat\"" --StopMode=exe --StopImage=cmd.exe
--StopPath="C:\WF\bin" ++StopParams="/c \"set NOPAUSE=Y &&
jboss-cli.bat --connect --controller=localhost:9939 --command=:shutdown\""
And starts just fine with "service start" but doesn't stop with
"service stop".
If I run the jboss-cli command manually, it stops fine.
If I try the new service.bat from
https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/src...
I get a
The data area passed to a system call is too small.
and the starting fails.
Windows service on 64 bit systems cannot be stopped
---------------------------------------------------
Key: WFLY-3149
URL:
https://issues.jboss.org/browse/WFLY-3149
Project: WildFly
Issue Type: Bug
Components: Scripts
Affects Versions: 8.0.0.Final
Environment: Windows 2008 Server, Windows 7 professional - both 64 bit systems
using JDK 1.7.0_09
Reporter: Mohan Potturi
Assignee: Mladen Turk
The Windows service cannot be stopped. It says 'stopping' in the windows service
user interface window. The only way to stop it is ti actually kill the java process. It
works flawlessly on 32 bit systems though.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)