Status: Closed (View Workflow)
Affects Version/s: JBossAS-5.1.0.GA
Fix Version/s: 6.0.0.M1
Similar Issues:Show 10 results
JBAS-7051 ManagedObjects are exposed for JBossMQ topics and queues - the MOs have the same component type as the MOs exposed for JBossMessaging destinations JBAS-6624 EJB3 Session Bean metrics JBAS-6877 EJB3 Entity Cache Metrics JBAS-6808 expose cluster partition name via some ManagedObject JBAS-6221 Implement some kind of jboss.xml template mechanism within EJB3 JBAS-4886 Incorrect order/dependency shutting down MDBs JBAS-7008 expose a ManagedObject for EJB3 Entity Beans JBAS-4438 Implement optional redelivery delay for MDBs JBAS-7633 Allow for configuring default resource adaptor name for the EJB3 MDBs JBAS-7137 MDBs dont register local-jndi-name when provided in jboss.xml
<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