It a simple lock inspection monitor as described in the admin/devel docs:
The EntityLockMonitor has no configurable attributes. It does have the following
read-only attributes:
-MedianWaitTime: The median value of all times threads had to wait to acquire a lock.
-AverageContenders: The ratio of the total number of contentions to the sum of all
threads that had to wait for a lock.
-TotalContentions: The total number of threads that had to wait to acquire the
transaction lock. This happens when a thread attempts to acquire a lock that is
associated with another transaction
-MaxContenders: The maximum number of threads that were waiting to acquire the
transaction lock.
It also has the following operations:
-clearMonitor: This operation resets the lock monitor state by zeroing all counters.
-printLockMonitor: This operation prints out a table of all ejb locks that lists the
ejbName of the bean, the total time spent waiting for the lock, the count of times the
lock was waited on and the number of transactions that timed out waiting for the lock.
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "Meyer-Willner, Bernhard" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, January 08, 2003 12:53 AM
Subject: Re: [JBoss-user] Purposes/behavior of different MBean services
Thanks a lot for the info, Scott.
Could you also please comment on the EntityLockMonitor, as I believe it
could be useful for detecting deadlock.
<!-- Uncomment to enable JMX monitoring of the entity bean locking
-->
<mbean code="org.jboss.monitor.EntityLockMonitor"
name="jboss.monitor:name=EntityLockMonitor"/>
Thanks,
Bernhard
-----Ursprüngliche Nachricht-----
Von: Scott M Stark [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 8. Januar 2003 04:00
An: [EMAIL PROTECTED]
Betreff: Re: [JBoss-user] Purposes/behavior of different MBean services
- BeanCacheMonitor is obsolete and will be removed.
- FileDeploymentStore and DeploymentCache were experiments by Jason. They
are unsupported and only available for experimentation.
- CounterService is simple accumulator you can lookup from JNDI under
java:/CounterService to invoker accumulate(String counterName, long add) ops
on and list totals from.
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "Meyer-Willner, Bernhard" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 07, 2003 2:46 AM
Subject: Re: [JBoss-user] Purposes/behavior of different MBean services
Hi,
does anybody from the JBoss team care to comment on those MBeans? Seems
there some interesting services offered and I'd love to know what they're
for, can't find any docs or meaningful info on the forums, though.
Thanks,
Bernhard
-----Ursprüngliche Nachricht-----
Von: Meyer-Willner, Bernhard [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 6. Januar 2003 16:06
An: JBoss-User (E-Mail)
Betreff: [JBoss-user] Purposes/behavior of different MBean services
Hi,
I have a couple of questions on different MBean services which are not
covered in the paid-for docs unfortunately, or are covered, but not in a
sufficient manner IMHO.
I'd love to hear from anybody who can tell me about the following:
1:
--
Except from jboss-service.xml:
<!--
==================================================================== -->
<!-- Monitoring and Management
-->
<!--
==================================================================== -->
<!-- Uncomment to enable JMX monitoring of the bean cache -->
<mbean code="org.jboss.monitor.BeanCacheMonitor"
name="jboss.monitor:name=BeanCacheMonitor"/>
<!-- Uncomment to enable JMX monitoring of the entity bean locking
-->
<mbean code="org.jboss.monitor.EntityLockMonitor"
name="jboss.monitor:name=EntityLockMonitor"/>
2:
--
Excerpt from jboss-service.xml
<!--
==================================================================== -->
<!-- Deployment Scanning
-->
<!--
==================================================================== -->
<!-- Uncomment to enable caching of deployment units -->
<mbean code="org.jboss.deployment.cache.FileDeploymentStore"
name="jboss.deployment:type=DeploymentStore,flavor=File">
<attribute name="DirectoryName">data/deployment-cache</attribute>
</mbean>
<mbean code="org.jboss.deployment.cache.DeploymentCache"
name="jboss.deployment:type=DeploymentCache">
<depends
optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depend
s>
<depends
optional-attribute-name="Store">jboss.deployment:type=DeploymentStore,flavor
=File</depends>
</mbean>
3:
--
What's the counter service MBean for (counter-service.xml) and how can it be
used and for what purposes?
Thanks,
Bernhard
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
This e-mail and any attachment is for authorised use by the intended recipient(s)
only. It may contain proprietary material,
confidential information and/or be subject to legal privilege. It should not be
copied, disclosed to, retained or used by,
any other party. If you are not an intended recipient then please promptly delete
this e-mail and any attachment and all
copies and inform the sender. Thank you.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
