Re: Catalina shutdown port as command line param?
Mladen Turk wrote: Hi, I was wondering if we can add the '-shutdown portnumber' to the catalina's command line parameters. The usage would be to enable multiple TC instances using the same server.xml file. If present the param would override the config's Server port=8005 For 4.1.x or 5.0 ? In 5.0 I would like to use ajp13 for shutdown, like in 3.3 - there is no need for a second port and all support is there, including the generation of a random password at startup and selection of the first free port. Costin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Catalina shutdown port as command line param?
Costin Manolache wrote: Mladen Turk wrote: Hi, I was wondering if we can add the '-shutdown portnumber' to the catalina's command line parameters. The usage would be to enable multiple TC instances using the same server.xml file. If present the param would override the config's Server port=8005 For 4.1.x or 5.0 ? In 5.0 I would like to use ajp13 for shutdown, like in 3.3 - there is no need for a second port and all support is there, including the generation of a random password at startup and selection of the first free port. Since you're speaking about start/stop, did there is plan to use a service wrapper (may be using JNI) to ensure start/stop works. For instance I've got some applications here, embedded in TC 3.3.1, which take time to stop properly and the problem when using start/stop from command line, is that you're never sure the application has finished, which is problematic when you want to make a restart for instance. The patch I commited in start scripts for TC 3.3.1/4.1/5.0 help us to know the PID of the first java process, but having something more bullet proof will be welcomed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Catalina shutdown port as command line param?
Howdy, 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? In 5.0 I would like to use ajp13 for shutdown, like in 3.3 - there is no Would this require an actual AJP13 connector to be running on the shutdown port? Yoav Shapira Millennium ChemInformatics This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Catalina shutdown port as command line param?
Shapira, Yoav wrote: Howdy, 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? In 5.0 I would like to use ajp13 for shutdown, like in 3.3 - there is no Would this require an actual AJP13 connector to be running on the shutdown port? Yep and there is potential security flaw if you didn't use more advanced login/pwd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Catalina shutdown port as command line param?
-Original Message- From: Henri Gomez [mailto:[EMAIL PROTECTED] Sent: 14. oujak 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]
