great thing. So I will wait and hope, that this issue is solved soon ;-).
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3995266#3995266
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3995266
The problem lies in our use of javax.net.ssl.SSLSocketFactory.getDefault()
internally when explicit ssl config is missing (more on this in a min), which
can be found within org.jboss.remoting.security.SSLSocketBuilder (line 421).
The jdk (at least Sun's implementation) will cache this factory
I don't know if this matches the previous mentioned issue or if this is an
issue for its own, but I have the problem that when running two Clients using
Transporters to connect to a target POJO on the server side and using SSL to do
this, always the second client is handled as beeing the first
