Description of problem: In the feature/cassandra-backend branch the storage installer has introduced a dependency on a com.sun class to work around https://issues.jboss.org/browse/AS7-2138. This bug is supposed to be resolved in newer versions of JBoss AS; so, when we upgrade the app server in master, I can retest and hopefully remove the dependency on the com.sun class that is used. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
It looks like this bug is currently being tracked under https://issues.jboss.org/browse/WFLY-794.
Initially bug 958166 was a blocker because we were making JMX connections to Cassandra from both the storage installer as well as from the RHQ server. We no longer make JMX connections from the server, but we do from the storage installer. Currently both the RHQ EAR and Storage installer the rhq-cassandra-jmx-<rhq-version>.jar library. That library has the dependency on com.sun.jndi.url.rmi.rmiURLContext. The work around described in https://issues.jboss.org/browse/AS7-2138 still holds true. In the RHQ build we modify the sun.jdk JBoss module to export, <path name="com/sun/jndi/url/rmi"/> As long as the sun.jdk module exports that path, we can get rid of rhq-cassandra-jmx-<rhq-version>.jar
The rhq-cassandra-jmx module has been altogether removed from the source tree.
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.