Why have worker.list?
The goal of the worker.list is to publish a worker to make it available to JkMount, correct? Why not have: worker.jvmRoute.type=ajp13 worker.jvmRoute.host=10.0.0.1 worker.jvmRoute.port=8009 worker.jvmRoute.mountable=1 And then construct the available workers for jkmount after the initialization of each worker, eliminating the worker.list altogether? Thanks for the response. I haven't found the issue yet. There is no VirtualHost setup on this particular server. I had changed JK1 to allow for long worker.list lines by increasing the LINE_LENGTH to 4K. This worked just fine under Apache 2 and we haven't seen any issues in the JK1 code or cookies with respect to the ':' in the JVM Routes. To you it might seem easier to change the jvmRoute, but unfortunately there are literally 100's of production app servers that would need changed and restarted. It wouldn't be easy at all and would require every app to be retested- which is quite a task with this many applications. We face some large scale problems that most users of tomcat/jk don't see because we have so many applications. I'm going to try loading the same jk config files on an apache 2 build of JK1 and see if I have the same issues- if so then I'll know its somewhere in my config. If not, then I'll know that there is some difference in behavior between jk1 on apache 1.3 and apache 2.0. As I mentioned before, the error I saw in the logs "NULL factory for ajp13*ajp13" makes me believe there was a problem during parsing of the config since I never explicitly specify "ajp13*ajp13" as a value anywhere. So perhaps the modified LINE_LENGTH of 4K works fine with apache 2, but runs into issues on Apache 1.3. Byron -----Original Message----- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 20, 2005 8:19 AM To: Tomcat Users List Subject: Re: jk 1.2.10 + apache 1.3 issue Guernsey, Byron (GE Consumer & Industrial) wrote: > > It uses a urimap.properties file instead of JkMounts. > OK. > The config directives in httpd.conf look like: > > <IfDefine MOD_JK> > JkLogLevel debug > JkShmSize 300 > JkShmFile /usr/local/apache/logs/jk1-ssodev.shm > JkWorkersFile /usr/local/apache/conf/workers_sso.properties > JkMountFile /usr/local/apache/conf/uriworkermap_sso.properties > JkLogFile /usr/local/apache/logs/mod_jk-ssodev.log > JkLogStampFormat "[%a %b %d %H:%M:%S %Y] " > JkRequestLogFormat "%w %V %T" > > <Location /jkstatus/> > JkMount jkstatus > Order deny,allow > Deny from all > Allow from 3. > Allow from 127. > </Location> > </IfDefine> > > As you can see from my previous posting, not even jkstatus works, nor > do any workers. Yet, they are configured properly and the jk log > shows that it finds them: > Well, just try the worker names without a colon. The reason for why we are forcing the alnum chars only is because the special chars needs to be url encoded if the client does not support the cookies. So it's easier and safer anyhow to rename the jvmRoutes in server.xml. Also for jkstatus. If you are calling that from some virtual host, you will need to have 'JkMountCopy On' directive in root, or define the Location in that virtual host. Also any workers.propeties directive should not exceed the 1024 chars. 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]
