-
1. Re: MDB JMX name changes btwn 3.2.4 and 3.2.7?
starksm64 Feb 25, 2005 12:48 PM (in response to duslow)This issue in the release notes describes the change:
[JBAS-275] - 2 identical named mdbs cannot deploy
http://jira.jboss.com/jira/browse/JBAS-275?page=comments
If you need a fixed local jndi name you would have to use a local-jndi-name in the jboss.xml descriptor. The JSR-77 name should be updated to breakup the fixed vs random part into seperate
jboss.j2ee:binding=workflow-invoker-heavy-weight-mdb,jndiName=local/InvokerHWMDB,id=11947822,plugin=invoker,service=EJB
So that a pattern like this could be used:
jboss.j2ee:binding=workflow-invoker-heavy-weight-mdb,jndiName=local/InvokerHWMDB,plugin=invoker,service=EJB,* -
2. Re: MDB JMX name changes btwn 3.2.4 and 3.2.7?
duslow Feb 25, 2005 1:18 PM (in response to duslow)Thanks for the info. However, non of my MDB share the same names.
Here the are in 3.2.4:binding=workflow-invoker-heavy-weight-mdb,jndiName=local/InvokerHWMDB,plugin=invoker,service=EJB binding=workflow-invoker-light-weight-mdb,jndiName=local/InvokerLWMDB,plugin=invoker,service=EJB binding=workflow-invoker-normal-weight-mdb,jndiName=local/InvokerMDB,plugin=invoker,service=EJB binding=workflow-message-driven-bean-max1,jndiName=local/ReturnerMDB,plugin=invoker,service=EJB binding=workflow-message-driven-bean-max1-dlq,jndiName=local/WorkflowDLQMDB,plugin=invoker,service=EJB binding=workflow-submit-spec-mdb,jndiName=local/SubmitSpecMDB,plugin=invoker,service=EJB
and here they are again in 3.2.7:binding=workflow-invoker-heavy-weight-mdb,jndiName=local/InvokerHWMDB@11947822,plugin=invoker,service=EJB binding=workflow-invoker-light-weight-mdb,jndiName=local/InvokerLWMDB@4290768,plugin=invoker,service=EJB binding=workflow-invoker-normal-weight-mdb,jndiName=local/InvokerMDB@22973093,plugin=invoker,service=EJB binding=workflow-message-driven-bean-max1,jndiName=local/ReturnerMDB@15434767,plugin=invoker,service=EJB binding=workflow-message-driven-bean-max1-dlq,jndiName=local/WorkflowDLQMDB@14627758,plugin=invoker,service=EJB binding=workflow-submit-spec-mdb,jndiName=local/SubmitSpecMDB@32525990,plugin=invoker,service=EJB
-
3. Re: MDB JMX name changes btwn 3.2.4 and 3.2.7?
duslow Feb 25, 2005 2:03 PM (in response to duslow)Sorry for the confusion on my part. I was distracted by the jira link you posted that was referring to two MDBs in different jars with the same name.
Adding <local-jndi-name> to the jboss.xml as you described, got rid of the random number on the JMX service name.<message-driven> <ejb-name>InvokerMDB</ejb-name> <destination-jndi-name>queue/invoke</destination-jndi-name> <configuration-name>Workflow Invoker Normal Weight MDB</configuration-name> <local-jndi-name>local/InvokerMDB</local-jndi-name> </message-driven>
Unfortunately, XDoclet doesn't support (or at least I haven't figured out how yet) to add the local-jndi-name to the jboss.xml for an MDB. The local-jndi-name token is available as an attribute of the @ejb.bean XDoclet tag. However, that only applies to SSB, SB and Entities, not MDBs.
Thanks for the help.