[
https://issues.jboss.org/browse/WFLY-3149?page=com.atlassian.jira.plugin....
]
Claudio Illanes edited comment on WFLY-3149 at 8/28/14 4:08 PM:
----------------------------------------------------------------
Is the fix just to remove the credentials variables from the 2 lines?
(Restricted to jira-users group)
was (Author: claudioillanes):
I found that manually running ""jboss-cli.bat --controller=localhost:9990
--connect --command=:shutdown" did not shut the service down.
To fix this install issue:
1. I went to the command line and ran "wildfly-mgr.exe //ES//Wildfly"
2. Visited the shutdown tab and realized that my wildfly install doesn't respond to
localhost:9990. I changed "localhost" to my server IP, saved the change, and I
was then able to stop the service from the command line.
I guess my Wildfly setup is not permitting localhost:9990 to be reached.
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
Security Level: Public(Everyone can see)
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.3.1#6329)