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]
