we
care, revive the thread if you can, better submit configuration that would work
with "many instances" on the same machine
marcf
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Finn
Sent: Tuesday, April 16, 2002 11:01 AM
To: Jboss-Development-List
Subject: [JBoss-dev] Multiple Instance - continuedYou guys probably have more to worry about right now, with RC1 and all, but:A while back there was a thread regarding the whole 'multiple instance detection' thing - where the problem of managing multiple listeners vying for the same port was discussed (JNDI, RMI, etc).Was there any resolution or direction? This is of interest to me as we do often have multiple JBosses running on a single box (to make it more challenging - we share a box with another group that has pure RMI apps running on it..).One of the options was a 'port manager' that would (if I understand) forward traffic (like a proxy) to the correct port for the requested service.1) To do this, I imagine the 'port mgr' would have to be able to sniff the incoming bytestream and determine the requested service by interrogating the content. This imposes the restriction that only one instance of a service (service being wire protocol - JNDI, HTTP, RMI, etc) can be routed, since there probably would be no unambiguous way to differentiate between two HTTP streams (for instance).2) The port mgr (MBean?) would somehow need to be aware of the 'real' ports being used within the JBoss process space by the managed services. Would the MBean Notification mechanism suffice? Where each MBean that owns a "managed" port would send a notification with the port/s onwhich it it is listening. Or, as (I think) Marc suggested, a P2P solution like JXTA (which may be a better solution than JMX Notifications?). Or a config file (less than optimal, IMO).Thoughts?I would definitely be interested in contributing on this. Or maybe no one cares about this one anymore. :-)Mike
