[
https://issues.jboss.org/browse/JBIDE-11709?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-11709.
---------------------------------
Resolution: Done
I am convinced this was fixed in beta3, however, the bug is now targeted to cr1, so just
test trunk. It also seems fixed in trunk. I am able to start / stop / check jmx beans in
trunk with no errors for ER6
Server EAP 6 ER6 fails to stop
------------------------------
Key: JBIDE-11709
URL:
https://issues.jboss.org/browse/JBIDE-11709
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Reporter: Martin Malina
Assignee: Martin Malina
Priority: Blocker
Fix For: 3.3.0.CR1
With JBIDE-11674 fixed, it turns out EAP6 ER6 cannot stop properly.
This is all that's printed in the log:
!ENTRY org.eclipse.wst.server.core 4 0 2012-04-30 10:36:09.309
!MESSAGE Server jboss-eap-6.0.0.ER6 failed to stop.
Also, there are plenty of errors in the log like this:
!ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2012-04-30 10:36:14.429
!MESSAGE Error connecting to jmx for server jboss-eap-6.0.0.ER6
!STACK 1
org.jboss.tools.jmx.core.JMXException: Runtime Exception contacting JBoss instance.
Please ensure your server is up and exposes its management ports via the
-Djboss.bind.address.management=yourwebsite.com system property
--
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