[
https://jira.jboss.org/jira/browse/JBIDE-3046?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-3046:
------------------------------------
Also they won't be able to shutdown the server, as the shutdown.sh and shutdown.jar
files use JMX to set the proper security credentials in order to shut the server down.
If something is wrong with their server configuration, whether its the hostname, the port,
the username, or the password, if they just ignore it they won't be able to deploy
properly and won't be able to shut the server down properly.
I'll let them ignore it, and I'll upgrade the text in the dialog to reflect the
seriousness of this issue.
AS credential question should not hide the reason
-------------------------------------------------
Key: JBIDE-3046
URL:
https://jira.jboss.org/jira/browse/JBIDE-3046
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.0.0.beta1
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Fix For: 3.0.0.CR2
If the server has jmx issues I get a dialog telling me a Security exception was thrown
with no info on the message nor any trace of it in the console or error log.
Making it very hard to debug what is the cause of it.
Maybe we should tell the user that JMX login might be disabled ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira