Bug 1110515 - mod_cluster Connected count shows improper inflation
Summary: mod_cluster Connected count shows improper inflation
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: mod_cluster
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ER2
: EAP 6.4.0
Assignee: jboss-set
QA Contact: Michal Karm Babacek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-17 20:15 UTC by Aaron Ogburn
Modified: 2019-08-19 12:44 UTC (History)
6 users (show)

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.
Clone Of:
Environment:
Last Closed: 2019-08-19 12:44:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker MODCLUSTER-416 0 Major Reopened mod_cluster Connected count shows improper inflation 2017-11-08 20:30:04 UTC

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.


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