++ This bug is a clone of bug 900272 ++ Help Desk Ticket Reference: https://na7.salesforce.com/500A0000009gDME Workaround Description: Remove space after'=' sign Change /jk-status|/* = jk-status to /jk-status|/* =jk-status project_key: JBEWS Where the worker name includes a '-' and there is a space after the '=' sign in the uriworkermap .properties, the following error is logged in the mod_jk logs [Tue Apr 03 23:41:26.992 2012] [25736:139832971024352] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'jk-stauus' in uri map post processing. [Tue Apr 03 23:41:26.992 2012] [25736:139832971024352] [error] uri_worker_map_ext::jk_uri_worker_map.c (506): Could not find worker with name 'jk-stauus' in uri map post processing. TEST CASE ## workers.properties worker.list=jk-status worker.jk-status.type=status worker.jk-status.read_only=true ## uriworkermap.properties /jk-status|/* = jk-status ## mod_jk.conf <Location /jk-status> # Inside Location we can omit the URL in JkMount JkMount jk-status Order deny,allow Deny from all Allow from 127.0.0.1 </Location> From the error log it is not easy to identify the root cause of the problem If this is not going to be fixed, perhaps validating the .properties file will help users fix the errors themselves Though for the status worker no entry is required in uriworkermap.properties. The worker.properties entry and JKMount directive is sufficient
Hi Mladen, can you please take a look? Thanks!
Updating Fix Version for tracking purpose.
In the error log I see 'jk-stauus' not jk-status. Could it be config typo?
So I thought initially, but adding the space after the equal sign appears to replicate the problem. /jk-status|/* = jk-status
But without spaces it works? If so, I see no reason why would this be a major issue. I can check the code, but that's minor and irrelevant stuff.
The workaround is noted, but it would be good to have this addressed at some point to have a pointer alerting the user of the root cause. Adjusting severity
Sure, I'll put that on my TODO list. We'll probably fix that with the next mod_jk release in the upstream. I'll see what it'll take to apply a patch for the next jboss-eap-native-webserver-connectors.zip Then we can see if we need to apply it to EWS1 BTW, could you check with the latest upstream release if the same issue is present there as well. If it its, could you create ASF bugzilla issue so we have that connected with upstream fixes? Some other developer might have more free time then I, so the fix could actually appear more promptly :)
Docs QE Status: Removed: NEW
Lami, have you got a chance to check upstream version and file the BZ if needed? Assigning to Weinan to follow up on this in next EWS release.
not yet fixed upstream.
BTW: There is a BZ upstream yet.
@Jan Stefl: Does this affect contemporary mod_jk releases, i.e. EAP 6.4+, JWS 3+ or it is merely an outdated Bugzilla?
I did the verification over EAP 6.4.0.GA and JWS 3.0.0.GA and the problem does not manifest any more.
Apparently, needs backporting from EAP 6.4.0 mod_jk's branch and/or from JWS 3.0.0 branch? If it's not pertinent to EWS 2.1.x, pls, close.
Hello, I was trying to reproduce this issue, but every time it was able to resolve worker. It was tested with EWS 2.0, 2.1 and JWS 3.0. Can anybody give any information?
Can you please provide me failing binaries or artifacts or addition information? I am not able to reproduce it with our products mentioned above.