Description of problem: I have an application running in EAP 6 that is trying to monitor another JVM. The external JVM is running a standard MBean server. This issue was reported as https://issues.jboss.org/browse/AS7-2138. I am using the 7.2.0.Alpha1-redhat-4 of EAP 6.1. The issue described in AS7-2138 still exists. I am using the work around which is introducing dependencies on com.sun classes which I cannot use for the long term. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I found the community issue for this - https://issues.jboss.org/browse/WFLY-794
Is the workaround using jboss-deployment-structure.xml as specified in the comment below enought for JON's purposes? https://issues.jboss.org/browse/WFLY-794?focusedCommentId=12778745&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12778745
Am I correct in assuming that the work around will not require RHQ to depend on com.sun JRE classes as we currently do? If so then I will test with the changes in jboss-deployment-structure.xml.
I am still seeing the exception even with the change in the EAR's jboss-deployment-structure.xml, javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is: java.net.ConnectException: Connection refused] We were hitting this issue in two places - one in the EAR and the other in a module that is executed from the command line. I updated the module as well, and interestingly enough, it works. Stuart can you take a look at our jboss-deployment-structure.xml and see if there is something I am missing or something I did incorrectly? You can view it here - https://gist.github.com/jsanda/5713890.
Stuart Douglas <stuart.w.douglas> updated the status of jira WFLY-794 to Reopened
Stuart Douglas <stuart.w.douglas> made a comment on jira WFLY-794 Given that no-one can remember what the original issue is, and this keeps coming up over and over again, I think we should just add this to the sun.jdk module.
Brian Stansberry <brian.stansberry> made a comment on jira WFLY-794 Rejecting the PR as it seems it was closed unmerged.
I am going to nack this. Work is being done on this in Wildfly upstream by Eduardo but it is quite invasive and I do not feel comfortable putting it into EAP 6.2 at this time. Assuming we find no problems with it in Wildfly it should be possible to get this into 6.3.
Assigning to Eduardo, as he is doing the work in Wildfly.
I believe what this BZ really is showing is https://issues.jboss.org/browse/WFLY-2115
(In reply to John Mazzitelli from comment #16) > I believe what this BZ really is showing is > https://issues.jboss.org/browse/WFLY-2115 (well, actually, I think WFLY-2115 is in addition to the original problem, that being WFLY-794)
Verified with EAP 6.4.0.DR2.