Bug 900459 (JBPAPP6-1462)
Summary: | Enabling/Disabling nodes with JK Status Manager does not work | ||||||
---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Jan Stefl <jstefl> | ||||
Component: | Apache Server (httpd) and Connectors | Assignee: | Mladen Turk <mturk> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | |||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 6.0.0 | CC: | atangrin, dpospisi, jstefl, mturk, rajesh.rajasekaran, twells, vtunka | ||||
Target Milestone: | --- | ||||||
Target Release: | TBD EAP 6 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
URL: | http://jira.jboss.org/jira/browse/JBPAPP6-1462 | ||||||
Whiteboard: | connectors eap6_need_triage mod_jk native | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: |
Tested on Sol10 x86_64
|
|||||
Last Closed: | 2012-10-31 14:35:47 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 900553 | ||||||
Attachments: |
|
Description
Jan Stefl
2012-05-17 16:17:42 UTC
Labels: Removed: connectors mod_jk native Added: connectors eap6_need_triage mod_jk native That is actually correct behaviour. The point is that you never used the workerX, so it always uses the configuration file's value. Try using the worker and then setting the activation. Eg, Use the following procedure: 1. curl -G -d "mime=prop" 127.0.0.1:5080/jkmanager/ | grep activation This will initialize subworkers 2. curl -G -d "cmd=update&mime=prop&w=router&sw=worker1&vwa=1" 127.0.0.1:5080/jkmanager/ Now update to DIS 3. curl -G -d "mime=prop" 127.0.0.1:5080/jkmanager/ | grep activation Now it will show worker.worker1.activation=DIS Change was deliberate so that workers gets correctly initialized. You will need to pull values first which will init nodes and then you can update parameters. The same procedure is done when using web-browser as a client, which is BTW preferred way, so made sure that command line tools follow the same procedure. In essence any cmd=update should be preceded by show. Oops seems we have a bug after all Fixed in the http://www.qa.jboss.com/xbuildroot/packages/mod_jk/1.2.36/7.sun10/ http://www.qa.jboss.com/xbuildroot/packages/jboss-eap-native-webserver-connectors/6.0.0/10.sun10/ Please verify. Here is the patch (FTR) http://pkgs.devel.redhat.com/cgit/rpms/mod_jk/tree/tomcat-connectors-1.2.36-JBPAPP-9052.patch?h=jb-ep-6-xb As a side note... I don't think this issue is a blocker. Further more, anything related to status worker should never be blocker, because its optional component that doesn't influence the overall module functionality. Fixed Release Notes Docs Status: Added: Not Yet Documented Affects: Added: Release Notes Release Notes Docs Status: Removed: Not Yet Documented Added: Not Required Affects: Removed: Release Notes I have tested that using jboss-eap-native-webserver-connectors-6.0.0.CR1-RHEL5-x86_64.zip. But still, workers disabled from jkstatus page are not disabled and subsequent requests are still beeing routed to them. But are the workers disabled? If so, please don't hijack the issue with something unrelated. But are the workers disabled? If so, please don't hijack the issue with something unrelated. Link: Added: This issue is a dependency of JBPAPP-9188 Mladen, it sounds like the attempt to disable the workers fail. If that is true, is there a work around that we can give the users to disable the workers in some other way? I was tring to verify reported issue. You said that that's the correct behaviour, later you say that we have an issue. However, it is absolutelly unclear to me what is the actual issue and what is the correct behaviour. Without that information, it is impossible to verify. Release Notes Docs Status: Removed: Not Required Added: Not Yet Documented Affects: Added: Release Notes Dominik, this issue is abot jk status manager not changing status. AFAICT this now works, so please close this issue. If jkstatus worker cannot change the worker status to disabled only then we have a problem. There are many ways why you can get worker trying to connect even if disabled, but that's not relevant to the problem this JIRA was about. I presume that's clear enough. Attachment: Added: jbpapp-9052.ogv I have attached a video showing strange behaviour after disabling a node using status manager. The node stays in ACT state after disabling. After couple of requests, node is switching from ACT do DIS randomly. Let me know if I am doing st wrong. Thanks. Could you post the md5sum of the mod_jk.so you are using. This looks like a stuff we already fixed in 1.2.37 release of mod_jk and which should have been applied as a patch to the latest build, but I'm not sure which one you are using and which one got into the release. I was using mod_jk from CR1 zips: http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-6.0.0-CR1/native/jboss-eap-native-webserver-connectors-6.0.0.CR1-RHEL5-x86_64.zip 04607d1f609e333dbbd870bb2484b9f3 mod_jk.so Right, seems a correct one. You will have to try with pessimistic locking, but anyway, find this not critical issue, so will have to wait until we fix that upstream in ASF. OK, so edit each worker member directly (click 'E' in front of member name) instead using "Edit this attribute for all members" Then it works. Seems there is a bug in that feature of status manager, so you might close this issue and open a new one named "Edit attribute for all members does not work" However, that's a minor issue since directly editing members work. Link: Added: This issue relates to JBPAPP-9315 Closed as requested, created separate JIRA for that issue (JBPAPP-9315). Thanks for verifying this issue, Dominik. Hey guys, Can I have a bit more information on the fix/result of this bug for the release notes? Thanks. Release Notes Docs Status: Removed: Not Yet Documented Added: Not Required Writer: Added: tomwells Please follow https://issues.jboss.org/browse/JBPAPP-9315 Release Notes Docs Status: Removed: Not Required Writer: Removed: tomwells Docs QE Status: Removed: NEW |