> -----Original Message----- > From: Henri Gomez [mailto:[EMAIL PROTECTED] > Sent: 14. ožujak 2003 17:44 > To: Tomcat Developers List > Subject: Re: Catalina shutdown port as command line param? > > > > > >>>The usage would be to enable multiple TC instances using the same > >>>server.xml file. > > > > > > But what about the real connector ports, used by apps, > defined inside > > server.xml? Would you need to change those as well? > >
No problem, the connector will increment if the port is used, although those connector are unused. > > > >>In 5.0 I would like to use ajp13 for shutdown, like in 3.3 > - there is > > Well the entire problem is two fold: 1. Server with multiple childs (I even have an experimental NT mpm with multiple childs), each of them wishing to start it's own JVM and TC instance. The inprocess TC is completely useless in that case cause each consecutive TC instance is aborted due to the shutdown port collision. IMHO in that case (inprocess) the shutdown port isn't needed at all, but seems that catalina wasn't designed to be _embedded_, and that is what we need. All the Socket connectors should be disabled in that case from the http connector to the each AJP connector, no matter what the server.xml states. 2. Starting TC from the 'dirty' JVM could not be accomplished right now. I'm working on a solution based on LauncherBootsrap, that is single independent class file and can be injected using DefineClass (from bytes) in the VM. That of course implicates the usage of commons-launcher. So perhaps instead of '-port shudownport' we should introduce '-embedded' where the catalina will wait for some sort of a signal from it's parent class. It can be AJP message, but allowed only from JNI channel (that will be the only one enabled in that mode), to skip the need for complicated authorization schemes. MT. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
