You should be able to get a stack trace of when the SSL objects are being constructed.
Could you post those?
I don't see that MBean ObjectName in the JBoss 3.2.3 distribution, so I assume it's
customer.
There is something close (in ./server/default/conf/jboss-service.xml)
| <mbean code="org.jboss.invocation.jrmp.server.JRMPInvoker"
| name="jboss:service=invoker,type=jrmp">
| <attribute name="RMIObjectPort">4444</attribute>
| <attribute name="ServerAddress">${jboss.bind.address}</attribute>
| <!--
| <attribute name="RMIClientSocketFactory">custom</attribute>
| <attribute name="RMIServerSocketFactory">custom</attribute>
| <attribute name="SecurityDomain">ssl-domain-name</attribute>
| -->
|
| <depends>jboss:service=TransactionManager</depends>
| </mbean>
What were the values used for your install?
If you can construct a test case, somebody at JBoss would likely fix the problem.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3837866#3837866
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3837866
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
