I had been working on an alternative solution to this problem (see earlier thread in Mid-April: "Multiple Instances"). After some thought and work, this (Dain's) seems more robust (at least to me). The other way was effectively a proxy server sitting on a single (known) port, directing streams to the correct endpoints. The problem is that not every wire protocol puts enough (or anything) in the initial packets in the stream to identify the service - so I don't think the proxy would work as we discussed before (HTTP would work OK, but it looks like JNDI and RMI wouldn't). Unfortunately, I didn't do any packet sniffing to find this until I had already written the proxy server/MBean :-(.
Q 1) I assume "service name" would be the JBoss service name? (jmx-html, webserver, etc). IP service name would be insufficient as there are multiple services serving HTTP (webserver, jmx-html, jetty/tomcat). 2) How do clients find what port to which they connect today? For example, w/ a separate-VM-client that does a bean lookup (via configured port - eg 1099) - where does it find the RMI port number(eg 4444) to make the method call? Is it in the object returned from the JNDI server? (Probably a dumb one, but not obvious to me). #mike -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dain Sundstrom Sent: Monday, May 20, 2002 2:44 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Re: [JBoss-user] JBoss in a multi developers environment Jules Gosnell wrote: > OK - that's not so bad. I can interface Jetty to it - no problem. Well that's one vote. We'll have to wait to see if everyone else agrees. > I'm still a little concerned about this centralisation creeping > outwards. Are ports the only resource over which different instances of > JBoss running on the same box are likely to collide ? I think so, but I don't know. > We should also bear in mind that certain services are usually expected > on particular ports. Reconfiguring the client side to know where the new > port is may be just as important as telling the server side where to > listen. I would also like to add server pushed client-side configuration for stuff like ENC, security config, ports, etc.. For all I know it could already be there. For now, they would have to configure the client by hand. > You port service will need to allocate/deallocate and lookup ports (and > throw PortAlreadyAllocated and NoSuchPort Exceptions). Or is this > becoming too complicated ? Much simpler. It just returns you a port number (int). The service would have to de allocate the port on shutdown (the port service could listen for destroy life cycle event). -dain _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
