[
https://issues.jboss.org/browse/JBIDE-14979?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-14979:
-------------------------------------
The attached pull request fixes many issues, but it does not convert wildfly to use port
9990 at this time. This is because JMX cannot work port 9990 at this time, only 9999
works. Wildfly still works for both almost all use cases, except the case of issuing a
jboss-cli.sh command over ssh to shut down the server.
Because of this, the attached patch does the following:
1) Port used is 9999 as the management port
2) New jars are added
3) For local use case, 9999 works in all cases
4) For RSE use case, 9999 works for all cases except in jboss-cli.sh, so, remote
management shutdown is used instead (shutdown via management directly).
This is a bit of a change in behavior, and it does not fully convert the wildfly adapter
to use 9990, but until a wildfly that has 9990 working effectively for all use cases
arrives, that would be impossible.
Remote Wildfly cannot be started - password not accepted
--------------------------------------------------------
Key: JBIDE-14979
URL:
https://issues.jboss.org/browse/JBIDE-14979
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server, upstream
Affects Versions: 4.1.0.Beta2
Environment: OS X Mountain Lion - client
RHEL 6 - remote server
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.1.1.Final
When I try to create a remote server using the wildfly adapter I get stuck on tools
asking me for a password and not accepting the correct password.
A side issue is that when you ignore the dialog and then try to stop the server, it will
show [Stopped] in the server view, but the process will keep running on the server - it
should kill the process.
--
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