I think that Mark mentioned that JXTA might be appropriate for this and I'd like to second it.
If clusters of jboss are distributed all over the place - not just on dedicated server boxes - then a loosely coupled protocol/service framework would be ideal. Setting up known 'rendezvous' points will help to discover and use a robust port service. I hope to start adding jxta bits to jboss in about six months time, but for the moment I'm totally swamped. Jason Dillon wrote: > > I am glad someone is looking into this. I wish I had more time to review what > is going on here & add input, but I am loaded with tasks at the moment. From > my brief overviews of your emails, look like you are on the case. > > --jason > > Quoting Mike Finn <[EMAIL PROTECTED]>: > > > You 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 > > > > > > > > > > ------------------------------------------------- > This mail sent through IMP: http://horde.org/imp/ > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
