[ https://jira.jboss.org/jira/browse/JBIDE-3393?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-3393. -------------------------------- Resolution: Done This issue was actually due to the locally-loaded security classes in jbossall-client.jar which were used to properly set the security information for people who had their JMX secured. The locally-loaded classes would do some debugging output before it even attempted the JMX connection. The fix is to ignore this output by adding a log4j.xml which uses the null appender. The reason for this was that, after closer inspection the output is entirely non-interesting. I had spent a while trying to figure out how to save the output in case it turned out to be useful, either by contributing my own appender to log it in the server log view, but this was completely futile. Either I would have had to have a specific log4j version bundled with my plugin, which then would caused problems later when loading the jboss jar, or get compilation version errors or class not found errors. I believe the only way this would work (in case, in the future, the output really was interesting) would be to not extend any log4j appender classes at all, and only include in my plugin the log4j API and not the implementation. However, for now, the nullappender is used. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-3393?page=com.atlassian.jira.plu... ] Rob Stryker updated JBIDE-3393: ------------------------------- Priority: Optional (was: Major) -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-3393?page=com.atlassian.jira.plu... ] Rob Stryker updated JBIDE-3393: ------------------------------- Fix Version/s: 3.1.0 (was: 3.0.1.GA) -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-3393?page=com.atlassian.jira.plu... ] Rob Stryker updated JBIDE-3393: ------------------------------- Fix Version/s: LATER (was: 3.1.0.M3) Reboot... start from scratch -- 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