Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1110515 - mod_cluster Connected count shows improper inflation
mod_cluster Connected count shows improper inflation
Status: NEW
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: mod_cluster (Show other bugs)
6.3.0
Unspecified Unspecified
medium Severity medium
: ER2
: EAP 6.4.0
Assigned To: jboss-set
Michal Karm Babacek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-17 16:15 EDT by Aaron Ogburn
Modified: 2018-03-05 10:30 EST (History)
7 users (show)

See Also:
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:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker MODCLUSTER-416 Major Reopened mod_cluster Connected count shows improper inflation 2017-11-08 15:30 EST

  None (edit)
Description Aaron Ogburn 2014-06-17 16:15:11 EDT
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 15:03:47 EDT
Aaron Ogburn <aogburn@redhat.com> updated the status of jira MODCLUSTER-416 to Reopened
Comment 2 Jean-frederic Clere 2014-11-07 05:54:57 EST
I think it should be documented as a known as the fix only improves the situation.
Comment 3 Michal Karm Babacek 2015-01-20 10:19:46 EST
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 11:44:59 EST
@MICHAL yes close & document.

Note You need to log in before you can comment on or make changes to this bug.