[ http://jira.jboss.com/jira/browse/JBAS-1562?page=history ]
Dimitris Andreadis updated JBAS-1562:
-------------------------------------
Original Estimate: 28800
Remaining Estimate: 28800
> Expose getEntityLockMonitor in the MBean EntityLockMonitorMBean
> ---------------------------------------------------------------
>
> Key: JBAS-1562
> URL: http://jira.jboss.com/jira/browse/JBAS-1562
> Project: JBoss Application Server
> Type: Feature Request
> Components: EJBs, JMX
> Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final,
> JBossAS-3.2.6 Final
> Reporter: Yaron Zakai Or
> Assignee: Dimitris Andreadis
>
> Original Estimate: 1 day
> Remaining: 1 day
>
> In order to perform proper monitoring of EJB locks, the current functionality
> is not enough for the following reasons:
> 1. The LockMonitor is saved per EJB name, where multiple EJBs can have the
> same name. The solution should be to store it based on the jndi name.
> 2. The only way to get per-EJB information is to use the printLockMonitor
> method. This will create a non reasonable overhead for a real-life monitoring
> solution. The solution here is to expose the method getEntityLockMonitor in
> the MBean interface.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
