Any luck finding the solution of this problem I was also running into same problem only difference is that I tried this same configuration with JBoss 5.0.1.
I was not able to find a solution. I spent quite a lot of time on this topic, but without any luck...
I confirmed that it is broken in JBoss5.0.1, I am not sure since when it is broken but it was working on JBoss4.2.1. I also confirmed that it is fixed in JBoss5.1.0
I checked the source code for following classes under jbosswe.jar and jbossweb-service.jar
JBossSocketFactory overrides following methods from tomcat's
protected TrustManager getTrustManagers(String keystoreType, String algorithm) protected KeyManager getKeyManagers(String keystoreType, String algorithm, String keyAlias)
But in tomcat JSSESocketFactory under JBoss5.0.1, method signatures are changed by adding additional String parameter String keystoreProvider.
So methods are changed to following in tomcat JSSESocketFactory
protected TrustManager getTrustManagers(String keystoreType, String keystoreProvider, String algorithm) protected KeyManager getKeyManagers(String keystoreType, String keystoreProvider, String algorithm, String keyAlias)
So JBossSocketFactory was not overriding these methods anymore and despite providing SSLImplementation="org.jboss.net.ssl.JBossImplementation" these two methods from JSSESocketFactory were invoked in place of JBossSocketFactory.
This is fixed in JBoss5.1.0