[jbosstools-issues] [JBoss JIRA] (JBIDE-11064) JMX Connections to as7 errors out and is not usable at all.
[
https://issues.jboss.org/browse/JBIDE-11064?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-11064:
-------------------------------------
Issue for shutdown is as follows: Once you expose the management port using
-Djboss.bind.address.management=mywebsite.com, the shutdown command must change from
{code}jboss-cli.sh --connect command=:shutdown{code} to {code}jboss-cli.sh
--controller=website.com:9999 --connect command=:shutdown{code}
Perhaps we should not be auto-exposing the management port. This seems like a bad idea and
it is not secure. I will think of further ways to ensure this works without being a
hindrance to the user. Pretty rough.
JMX Connections to as7 errors out and is not usable at all.
------------------------------------------------------------
Key: JBIDE-11064
URL: https://issues.jboss.org/browse/JBIDE-11064
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, jmx
Affects Versions: 3.3.0.Beta1
Environment: jbdevstudio-product-universal-5.0.0.v201202250031M-H77-Beta1.jar
JBoss AS 7.0.2
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Blocker
Labels: new_and_noteworthy
Fix For: 3.3.0.Beta3
Attachments: as7.0.2remote.log
AS 7.0.2 fails to start using RSE.
!ENTRY org.jboss.ide.eclipse.as.core 4 0 2012-02-27 11:26:24.651
!MESSAGE Error connecting to this server's JMX service: jboss-as-7.0.2.Final on
marvin
!STACK 0
java.io.IOException: Failed to retrieve RMIServer stub:
javax.naming.ServiceUnavailableException
I'm not sure how exactly it works, but I am told that remote JNDI didn't really
work in 7.0.2 so maybe that's why?
--
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