I seems solve the problem with follow change.
in jboss-service.xml
<mbean code="org.jboss.invocation.jrmp.server.JRMPInvoker"
| name="jboss:service=invoker,type=jrmp,socketType=SSL">
| <attribute name="RMIObjectPort">14445</attribute>
| <attribute
name="ServerAddress">${jboss.bind.address}</attribute>
| <attribute
name="RMIClientSocketFactory">org.jboss.security.ssl.RMISSLClientSocketFactory</attribute>
| <attribute
name="RMIServerSocketFactory">org.jboss.security.ssl.RMISSLServerSocketFactory</attribute>
| <attribute name="SecurityDomain">java:/jaas/RMI+SSL</attribute>
| <depends>jboss:service=TransactionManager</depends>
|
<depends>jboss.security:service=JaasSecurityDomain,domain=RMI+SSL</depends>
| </mbean>
add jboss:service=TransactionManager .
Try it out. but is there any way to test whether the ejb is really go through
ssl?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965194#3965194
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3965194
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
