In upgrading from 3.2.4 to 3.2.7 and have discovered that the JMX service names for MDBs have changed.
In 3.2.4 it was: jboss.j2ee:binding=workflow-invoker-heavy-weight-mdb,jndiName=local/InvokerHWMDB,plugin=invoker,service=EJB In 3.2.7 it is: jboss.j2ee:binding=workflow-invoker-heavy-weight-mdb,jndiName=local/[EMAIL PROTECTED],plugin=invoker,service=EJB The issue I have is that I have a custom JMX administrative component that is used to manage the MaxPoolSize MDB settings at run-time and thus my JMX component requires that the MDB(s) are deployed first prior to my JMX component starting. In 3.2.4, I solved the dependency via XDoclet by simply adding the following to my custom MBean class. * @jboss.depends object-name="jboss.j2ee:binding=workflow-invoker-heavy-weight-mdb,jndiName=local/InvokerHWMDB,plugin=invoker,service=EJB" | It appears that in 3.2.7, the server is appending a random number to the jndiName section of the MDB JMX name. This prevents me from being able to reference that service as a dependency since the appended number changes on each restart of the application. Why was this number added and can it be turned off so that the name is static? If this cannot be turned off, what is the new sanctioned way to make JMX service calls to the deployed MDBs? Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867929#3867929 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867929 ------------------------------------------------------- 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-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
