Bug 640633

Summary:	JBoss web server connector metrics for JBossAS appear to use threads allocated instead of maxThreads for the max
Product:	[Other] RHQ Project	Reporter:	dsteigne
Component:	Plugins	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED WONTFIX	QA Contact:	Mike Foley <mfoley>
Severity:	medium	Docs Contact:
Priority:	low
Version:	3.0.0	CC:	dsteigne, jshaughn
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-27 20:55:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description dsteigne 2010-10-06 14:00:42 UTC

Description of problem:

The embedded JBoss web server connector metrics for JBossAS appear to use threads allocated instead of maxThreads for the maximum. So an alert for "> 90% max AJP connections" triggers when 4 out of 4 threads are busy even though maxThreads is 50. We are seeing similar false alarms after creating alerts for Datasource connections in use and ConnectionFactory connections in use. 

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

2.4.0

Comment 1 Jay Shaughnessy 2014-06-27 20:55:47 UTC

closed due to inactivity, please re-open if still an issue.