java.io.IOException: Error initializing server socket factory SSL context: SunX509 KeyManagerFactory not available at sun.security.jca.GetInstance.getInstance(GetInstance.java:158) at javax.net.ssl.KeyManagerFactory.getInstance(KeyManagerFactory.java:20) at org.jboss.remoting.security.SSLSocketBuilder.loadKeyManagers(SSLSocketBuilder.java:1472) at org.jboss.remoting.security.SSLSocketBuilder.initializeServerSocketFactorySSLContext(SSLSocketBuilder.java:1250) at org.jboss.remoting.security.SSLSocketBuilder.createCustomServerSocketFactory(SSLSocketBuilder.java:366) at org.jboss.remoting.security.SSLSocketBuilder.createSSLServerSocketFactory(SSLSocketBuilder.java:346) at org.jboss.remoting.security.SSLSocketBuilder.createSSLServerSocketFactory(SSLSocketBuilder.java:325) at org.jboss.remoting.security.SSLServerSocketFactoryService.start(SSLServerSocketFactoryService.java:61) at org.rhq.enterprise.communications.ServiceContainer.initializeSecurityServices(ServiceContainer.java:1342) at org.rhq.enterprise.communications.ServiceContainer.setupServerConnector(ServiceContainer.java:1193) at org.rhq.enterprise.communications.ServiceContainer.start(ServiceContainer.java:550) at org.rhq.enterprise.communications.ServiceContainer.start(ServiceContainer.java:468) at org.rhq.enterprise.agent.AgentMain.startCommServices(AgentMain.java:2110) at org.rhq.enterprise.agent.AgentMain.start(AgentMain.java:624) at org.rhq.enterprise.agent.AgentMain.main(AgentMain.java:406) Looks like (http://www.google.com/codesearch/p?hl=en&sa=N&cd=1&ct=rc#9krPMA6e7qo/src/org/jboss/remoting/security/SSLSocketBuilder.java&q=org.jboss.remoting.security.SSLSocketBuilder.java). Adding -Dorg.jboss.remoting.keyStoreAlgorithm=IbmX509 as an option in rhq-agent-env.sh in the bin directory and using the "advanced setup" with IbmX509 as the "Server Side Keystore Algorithm" and "Keystore Trust Store Algorithm" on the client side. Make this work. Ideally the docs mention this and more ideally the default is IbmX509 when the vm is IBM instead of Sun.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2487
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
*** Bug 535753 has been marked as a duplicate of this bug. ***
fixed as part of bug #968357 git commit to master: 32e712e4da7a4ba93babb7e41c67c71aa1a838f7
Bulk closing of old issues now that HRQ 4.9 is in front of the door. If you think the issue has not been solved, then please open a new bug and mention this one in the description.