Resending due to my messed up sendmail config... ---------- Forwarded Message ----------
Subject: Re: [JBoss-dev] JMX RMI Adapter & JNDI binding Date: Mon, 13 May 2002 19:59:24 +0000 From: Jason Dillon <[EMAIL PROTECTED]> To: "Hiram Chirino" <[EMAIL PROTECTED]>, [EMAIL PROTECTED], [EMAIL PROTECTED] Agreeded. Any reason why we are using : a seperator here? No big deal just makes this namespace rather flat when using JNDIView to check it out. --jason On Monday 13 May 2002 03:22 pm, Hiram Chirino wrote: > I think that you can just default it to jmx:rmi and give allow the location > of the bind to be configurable. > > So when you have 2 jmx servers using the same JNDI service, then that > problem is solved by having second jmx server can bind to something like > server2/jmx:rmi > > Regards, > Hiram > > > From: "Andreas Schaefer" <[EMAIL PROTECTED]> > > >To: "Jason Dillon" <[EMAIL PROTECTED]>, > ><[EMAIL PROTECTED]> > >Subject: Re: [JBoss-dev] JMX RMI Adapter & JNDI binding > >Date: Mon, 13 May 2002 07:33:57 -0700 > > > >Hi Jason > > > > > Can someone point me to the spec where it states where in JNDI the JMX > > > >RMI > > > > > adapter should be bound to. > > > >Because otherwise no client can find the JMX RMI-Adapter except for the > >local > >client. > > > > > Currently we are binding to "jmx:<hostname>:rmi" which is fine when you > > > >are > > > > > working with the localhost, but will start to cause problems once used > > > >in > >a > > > > > multi-host environment. > > > > > > For example, consider a situation where a machine has more than one > > > >resolvable > > > > > name (via DNS CNAMES or similar). Lets say that the localhost name is > > > >set > >to > > > > > "myhost.mydomain.com", and there us a CNAME "www.mydomain.com". The > > > JMX > > > >RMI > > > > > adapter will be bound to "jmx:myhost.mydomain.com:rmi". > > > > > > Now consider the deployer.<sh|bat> scripts run from a seperate machine. > > > >There > > > > > is a --server option, which is the <hostname> bit from > > > >"jmx:<hostname>:rmi". > > > > > This is currently only used to lookup the RMIAdapter from JNDI but not > > > >used to > > > > > setup the Context.URL. This means that a client could not: > > > > > > ./deployer.sh --server www.mydomain.com --deploy someurl > > > >Aggreed that is a problem. The reason to do so is that I wanted a way to > >bind > >multiple JMX-RMI Adaptor on the JNDI server. > >The REAL problem pops up when we have two JVMs with a JMX RMI Adaptor > >running !!! > > > > > Assuming that deployer.sh did make up a Context.URL from --server > > > (which > > > >it does > > > > > not) this would not work due to a lookup failure, as there will be no > > > "jmx:www.mydomain.com:rmi" bound. > > > >The client is supposed to look up the right JNDI name but I created a > >pattern he > >can easier guess the right name. > > > > > The point is that we can not reliably use any resolvable address. > > > >As I said the bigger problem is with two JVMs. > > > > > So, I don't know what the spec says. If the spec wants us to use the > > > >hostname > > > > > fine, but lets also bind the local adapter to a common name, like > > > "jmx:localhost:rmi" or perhaps "jmx::rmi" or whatever I don't really > > > >care, > >as > > > > > long as the name is not specific to the local host configuration. > > > >The current spec. says nothing and the current JNDI name was my idea. We > >could > >add a second name called "jmx:localhost:rmi" which does not help when we > >have > >2 JVMs. Assuming that the JNDI server is running on another box this name > >has > >not meaning anymore. > > > >Have fun - Andy > > > > > > > >_______________________________________________________________ > > > >Have big pipes? SourceForge.net is looking for download mirrors. We supply > >the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] > >_______________________________________________ > >Jboss-development mailing list > >[EMAIL PROTECTED] > >https://lists.sourceforge.net/lists/listinfo/jboss-development > > _________________________________________________________________ > Chat with friends online, try MSN Messenger: http://messenger.msn.com ------------------------------------------------------- _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
