Bug 1110515

Summary: mod_cluster Connected count shows improper inflation
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Aaron Ogburn <aogburn>
Component: mod_clusterAssignee: jboss-set
Status: CLOSED EOL QA Contact: Michal Karm Babacek <mbabacek>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.3.0CC: aogburn, bmaxwell, bperkins, jclere, mbabacek, msochure
Target Milestone: ER2   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
Cause: The plus/minus operations of the mod_cluster connected count (a proxy_worker's busy attribute) aren't atomic because that would have some performance impact. Consequence: The mod_cluster connected count shows improper inflation. Workaround (if any): None Result: The mod_cluster connected count can be inaccurate. With load stopped, non-zero values have still been seen through the mod_cluster-manager page and INFO MCMP responses.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:44:53 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 Aaron Ogburn 2014-06-17 20:15:11 UTC 
Description of problem:

The mod_cluster connected count (a proxy_worker's busy attribute) shows improper inflation. With load stopped, non-zero values have still been seen through the mod_cluster-manager page and INFO MCMP responses.

Version-Release number of selected component (if applicable):

mod_cluster 1.2.9.Final
Comment 1 JBoss JIRA Server 2014-07-08 19:03:47 UTC 
Aaron Ogburn <aogburn> updated the status of jira MODCLUSTER-416 to Reopened
Comment 2 Jean-frederic Clere 2014-11-07 10:54:57 UTC 
I think it should be documented as a known as the fix only improves the situation.
Comment 3 Michal Karm Babacek 2015-01-20 15:19:46 UTC 
https://bugzilla.redhat.com/show_bug.cgi?id=1018705#c16

I think we should decide what to do with BZ 1018705 and BZ 1110515 for good.

@JFC Regarding comment 2, do I get it right that we should close & document both of them?
Comment 4 Jean-frederic Clere 2015-01-20 16:44:59 UTC 
@MICHAL yes close & document.