[
https://issues.jboss.org/browse/JBIDE-12153?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-12153.
---------------------------------
Resolution: Done
commited a limited refresh for all calls to findPort. In properly isolated xpaths (which
do not for example check an entire folder, but rather limit to just one xml file) this
should be extremely quick.
Refresh server ports when server is added
-----------------------------------------
Key: JBIDE-12153
URL:
https://issues.jboss.org/browse/JBIDE-12153
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.1
This is a follow-up from JBIDE-11854.
I agree that we cannot always check if the management port in standalone.xml is changed.
But at least in the case when you add a server the ports should be refreshed.
The original steps to hit this problem are here:
1. Add AS7 server with management port set to 9899 in standalone.xml
2. Start the server - the server will be started correctly in a few seconds - this means
the management port is detected correctly, perfect
3. Stop the server, remove the server runtime and server adapter
4. Change the management port of your AS7 server to 9799 in standalone.xml
5. Add the server again
6. Try to start the server - this time it will be "starting" until it reaches
timeout, because it will assume the management port is again 9899 - FAIL
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira