[
https://issues.jboss.org/browse/AS7-5472?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-5472:
---------------------------------------
Yeah, I'm not arguing it's incorrect, just saying it's contrary to the
original (broken) design, and that's a probable cause of the JMX problem. If so the
fix is to adapt the JMX view logic to recognize and deal with this.
In general we need to make it easy for clients to recognize this (which is a separate
issue.)
unavailable datasource statistics
---------------------------------
Key: AS7-5472
URL:
https://issues.jboss.org/browse/AS7-5472
Project: Application Server 7
Issue Type: Bug
Components: JCA, JMX
Affects Versions: 7.1.2.Final (EAP)
Reporter: Mathieu Lachance
Assignee: Stefano Maestri
Priority: Minor
In the java visual vm, in the mbean tab, under the
"jboss.as:subsystem=datasources,data-source=MyDataSource" mbean, attribute
"statistics" is marked as "Unavailable"
When using the spy="true" attribute in the datasource subsystem in conjunction
with the "org.jboss.jca" logger set as TRACE level in the logging subsystem,
statistics are outputted as follow :
Statistics:
ActiveCount: 1
AvailableCount: 99
AverageBlockingTime: 0
AverageCreationTime: 248
CreatedCount: 1
DestroyedCount: 0
MaxCreationTime: 248
MaxUsedCount: 1
MaxWaitCount: 0
MaxWaitTime: 0
TimedOut: 0
TotalBlockingTime: 0
TotalCreationTime: 248
I would except to find those statistics available through separates jmx attributes when
using the spy="true".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira