[
https://issues.jboss.org/browse/JBIDE-11921?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11921:
-------------------------------------
Will work for as7 only as of now since management on as<7 is different and I
haven't had time to truly evaluate it. Tasks that were done for this are:
1) Update the ui
2) Modify the launchers for local as7 to properly override the management arg
3) Modify the launchers for remote as7 to properly override both start and stop
4) Update JMX for as7. While no changes should have been needed, it seems that there were
two issues.
a) The close() would block forever. This is similar to the as71 management issue and
simply needs to have an interrupt to fix it
b) if you make a second jmx connection (expand the mbean view) after making the first
(automatically made after startup) but before the close() has completed, the connection
fails with status waiting. Not really sure on this yet, but I made the interrupt delay
for jmx only 2 seconds, to ensure that people using the editor and the view will not have
problems. But this definitely requires more investigation, such as erroring in a more
graceful way if the delay were longer. Currently it seems logging to the error log is not
really enough.
Add "expose management on same host" and add
-bmanagement=<host> on startup and shutdown
----------------------------------------------------------------------------------------
Key: JBIDE-11921
URL:
https://issues.jboss.org/browse/JBIDE-11921
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
Attachments: JBIDE-11921.png
--
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