RE: Jk 1.2.10 worker limit?
To add to this- separating the lines into two worker.list lines *almost* worked. It seems that when I have a line like: worker.list=jkstatus,app1,app2,...,app72 worker.list=app73,app74,... The jkstatus page shows a worker with the name app72*app73 and assigned it an ajp13 worker on localhost:8009 even though its not configured anywhere, and then continues with app74. Looks like I'll just have to find the buffer(s) used in parsing worker.list and increase its capacity for now, but is anyone from the jk1 team reading this? It would be nice if multiple worker.list are supported, or worker.list becomes deprecated since its really not needed if you simply register the works as they are referenced in the worker definitions. Byron -Original Message- From: Guernsey, Byron (GE Consumer Industrial) Sent: Monday, April 04, 2005 10:49 AM To: Tomcat Users List Subject: Jk 1.2.10 worker limit? I've written a script to convert my mod_jk2 configs over to mod_jk1. The configs on jk2 have around 109 applications in them. When I load the config in jk 1.2.10, I see only the first 72 entries from the worker.list line. Is there a length limit of the length of the worker.list? My line appears to hit the magic length value 1024. And if so, will jk1 accept more than 1 worker.list line or where should I look in the source to up this line limit? Thanks, Byron - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jk 1.2.10 worker limit?
Guernsey, Byron (GE Consumer Industrial) wrote: To add to this- separating the lines into two worker.list lines *almost* worked. It seems that when I have a line like: worker.list=jkstatus,app1,app2,...,app72 worker.list=app73,app74,... This will not work. There is even a bugzilla entry on that, but the fix didn't get into release. Anyhow why would you need that much workers? Do you have that many Tomcat's instances in behind? The purpose of worker is to represent a physical Tomcat instance, not application or virtual host within some Tomcat instance. OTOH if you have that many workers, use shorter names, like only numbers, or something like that. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Jk 1.2.10 worker limit?
We have that many separate instances, and more. In large companies it becomes necessary to segregate your applications because each application has the potential to affect another application if bad code goes into production. So JVM's must be completely separate, otherwise you have war within your organization when someone makes a bad change and it affects tons of applications. Each application team has the ability to stop/start their production servers, and having separate tomcat instances prevents that from affecting everyone. And while you could combine some applications where the risk is low, for consistency and automation of various setup and maintenance tasks, it became necessary to make application consistent- meaning they all must have their own JVM's. Renaming the workers could be an option, but we will only have more and more workers added, so I'm increasing the value of LENGTH_OF_LINE to at least 2K in our build; which should hold us over until the fix is released. Byron -Original Message- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Monday, April 04, 2005 12:11 PM To: Tomcat Users List Subject: Re: Jk 1.2.10 worker limit? Guernsey, Byron (GE Consumer Industrial) wrote: To add to this- separating the lines into two worker.list lines *almost* worked. It seems that when I have a line like: worker.list=jkstatus,app1,app2,...,app72 worker.list=app73,app74,... This will not work. There is even a bugzilla entry on that, but the fix didn't get into release. Anyhow why would you need that much workers? Do you have that many Tomcat's instances in behind? The purpose of worker is to represent a physical Tomcat instance, not application or virtual host within some Tomcat instance. OTOH if you have that many workers, use shorter names, like only numbers, or something like that. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
