The problem with both of these ideas is that the component now needs to know about this extra config file or mapping component... unless of cource this mapping is done via the config service.
I still think that a routing port manger sitting infront of all possible components would be easier to manage. --jason Dain Sundstrom wrote: > Marc, > > I was talking about this last week. The problem with this suggestion > is it does not address other ports such as http, http-jmx management. > My ideas was to have a port config file that listed each named port > for a server, and then each mbean that used a port would look in this > file (or an mbean that represents the file). Scott said that this > idea was lame, and we need naming conventions for the port attributes > or xmbeans with additional meta data. I don't think there was a > resolution. > > -dain > > marc fleury wrote: > >> there should be a service that is part of the first services coming >> up and >> that detects if other JBoss systems are running on the same physical >> machines, this is to avoid port conflict as some services are holding >> on to >> some ports (e.g. naming on 1099, detached RMI, clustered RMI). >> >> We would then not start the naming as a duplicate nor the detached >> RMI but >> we would use the clustered RMI by increasing the connection port. >> >> This will enable people to run multiple instances of JBoss without >> having to >> manually change the stuff all the time. At least on the services we >> provide >> we should show how these behave. >> >> marcf >> >> >> _______________________________________________ >> 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 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
