Bug 900272 (JBEWS-326)

Summary:	On RHEL 6 mod_jk unable to handle space after equal '=' sign in uriworkermap.properties where worker name includes a hyphen '-'
Product:	[JBoss] JBoss Enterprise Web Server 1	Reporter:	Lami Akagwu <lakagwu>
Component:	unspecified	Assignee:	Permaine Cheung <pcheung>
Status:	CLOSED EOL	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	EWS 1.0.2	CC:	csutherl, lakagwu, mturk
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEWS-326
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	900273 (view as bug list)		Environment:	RHEL 6 Reproduced on 2.6.32-131.0.15.el6.x86_64
Last Closed:	2017-08-04 15:03:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lami Akagwu 2012-04-20 09:16:14 UTC

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

Comment 1 Permaine Cheung 2012-04-20 13:39:09 UTC

Hi Mladen, can you please take a look? Thanks!

Comment 2 Permaine Cheung 2012-04-20 13:48:24 UTC

Updating Fix Version for tracking purpose.

Comment 3 Mladen Turk 2012-04-20 15:15:00 UTC

In the error log I see 'jk-stauus' not jk-status.
Could it be config typo?

Comment 4 Lami Akagwu 2012-04-23 08:30:38 UTC

So I thought initially, but adding the space after the equal sign appears to replicate the problem.

/jk-status|/* = jk-status

Comment 5 Mladen Turk 2012-04-23 10:25:15 UTC

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.

Comment 6 Lami Akagwu 2012-04-23 10:55:07 UTC

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

Comment 7 Mladen Turk 2012-04-23 11:57:52 UTC

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 :)

Comment 8 Jiri Skrabal 2012-11-13 16:27:29 UTC

Docs QE Status: Removed: NEW