[jboss-jira] [JBoss JIRA] Resolved: (JBAS-6999) expose MOs for EJB3 MDBs w/ some metrics

[Andrew Lee Rubinger (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-6999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Lee Rubinger resolved JBAS-6999.
---------------------------------------

    Resolution: Done


> expose MOs for EJB3 MDBs w/ some metrics
> ----------------------------------------
>
>                 Key: JBAS-6999
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6999
>             Project: JBoss Application Server
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: ProfileService
>    Affects Versions: JBossAS-5.1.0.GA
>            Reporter: Ian Springer
>            Assignee: Andrew Lee Rubinger
>             Fix For: JBossAS-5.2.0.Beta1
>
>
> <pilhuhn> Do you also plan to list MDBs so that they can at least be detected?
> <ALR> pilhuhn: I hadn't, but I can add that.  What would you like exposed for MDB?
> <pilhuhn> metrics like on the jmx console would be cool, but just listing them as ManagedComponent within a EJB jar would be great - they are already in the KnownComponentTypes :)
> <ALR> pilhuhn: To list as a ManagedComponent wouldn't I need to register some @ManagementObject ?  Just some stub thing?
> <pilhuhn> aehm .. :)
> <ALR> pilhuhn: I've found some stats I can expose, actually, without touching the ejb3-core, which has been my aim thus far. :)  I'll do it.
> <pilhuhn> Great - JOPR-203 has a EAR attached with a MDB in it - and the jxm-console shows keepalive millis, stats, min pool size, max pool size, delivery active and max messages

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira