RE: RMIJRMPServerImpl

Hi, 

> Here is a solution to our problem with JRMP and the 
> UnicastRemoteObject 
> class:
> If replaceing the
>     /UnicastRemoteObject.export(obj, port, clientFactory, 
> serverFactory)/ call
> with
>     /UnicastRemoteObject.export(obj)/, or
>     /UnicastRemoteObject.export(obj, 0, clientFactory, serverFactory)/
> than, we do not have the exception any more :-)

No.
I have a doubt that you...

> This is the details of the scenario:
> - The first JOnAS server starts a registry on a port *P* 
> (maybe 1099 or 
> another, here 1962),
> than starts a MBean server and creates a RMIConnectorServer which is 
> started at     /service:jmx:rmi://host:1962/jndi/jrmpconnector_j1/.

... didn't read carefully the JMXServiceURL spec for RMI, in particular here:
http://java.sun.com/j2se/1.5.0/docs/api/javax/management/remote/rmi/package-summary.html

The correct JMXServiceURL for your case should be:
service:jmx:rmi:///jndi/rmi://jonas1:1962/jrmpconnector_j1

> - The second JOnAS servers starts and detects that registry 
> is already 
> started on *P*.
> Than, it creates its MBean server and a RMIConnectorServer 
> that has to 
> be started at
> /service:jmx:rmi://host:1962/jndi/jrmpconnector_j3/.

See above, should be:
service:jmx:rmi:///jndi/rmi://jonas1:1962/jrmpconnector_j3

Regards,

Simon


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl