RE: adding mx4j's connector class to factory list

Hi,

> Once that is fixed, I expect I'll hit the same problem that my
> non-J2EE client has.  I am using the URL
> service:jmx:rmi://localhost:2003.  I don't think there is anything
> wrong with that URL since (1) I can start up a mx4j connector server
> with this URL, 

This does not mean you can start a *client* with that URL.
If you call getAddress() before and after start()ing a JMXConnectorServer, you will see something :)
Details are in the Javadocs of the javax.management.remote.rmi package.

> (2) clients work fine with this URL with Sun's remote
> API R.I., 

Didn't you get an error like "missing /jndi/, /stub/ or /ior/ in the path" ?
I don't think RJMXRI can start a client with a JMXServiceURL with no path.

> (3) the mx4j Guide uses URLs just like mine:
> "service:jmx:rmi://host".  But, when I track down my stack trace to
> RMIResolver.java:79, it looks like it is requiring a JNDI specifier.
> I don't want to use JNDI, I want to use "service:jmx:rmi://localhost:2003".

You cannot avoid use of JNDI with RMI, unless your client and your server are in-VM, or you have a way to pass the stub from server to the client (like corba's IOR). Note that this last possibility exists with JSR 160 and plain RMI.

BTW, I could not find the RJMX classes in Tomcat 5...
Where are they ? I am trying to run your example to see what it does not work.

Thanks

Simon


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click