Deployed MDB names changed from 3.2.6 to 3.2.7. Problem mark

[fpa1974]

The problem I am experiencing is related to the fact that the name of the deployed MDB (the MBean name wrapping it) seemed to have changed from something like:

jboss.j2ee:binding=message-driven-bean,jndiName=local/ExampleMDB,plugin=invoker,service=EJB

in 3.2.6 to something like:

jboss.j2ee:binding=message-driven-bean,jndiName=local/ExampleMDB@8158597,plugin=invoker,service=EJB

in 3.2.7.

The problem with this is that I used to have an MBean that had a depends statement in order to make sure the MDB gets deployed before the MBean. As it can be seen above this can be easily done in 3.2.6 but in 3.2.7 with the addtion of the '@8158597' string to the MDB name the solution I had is obviously not working especially since the number above changes for each server restart.

Any suggestions on how this can be achieved in 3.2.7 would be appreciated.

Thanks,
Florian

[harleybl]

Florian,

Did you ever find a workaround for this or a fix.
We are experiencing the same problem with Jboss 4.0.2.
In our application we have one EJB which needs to call
a service in another one in order to get data, however
the initial context lookup fails.

-Harley Blumenfeld

[starksm64]

See 'Why is there a "@xxxxxx" in my local ejb JNDI name?' in this faq:
http://wiki.jboss.org/wiki/Wiki.jsp?page=HowDoIAccessALocalHome

[fpa1974]

Thanks Scott. I looked at the source code and figured out the fact that local-jndi-name has to be specified. I think this is the best way to handle this.

On a side note what I did before doing the local-jndi-name is using a bit of the JMX notifications that are fired in JBoss to handle this dependency locally. Basically at MBean deployment time (start() method being called) the MDB is checked if it was deployed, if not I subscribe to the 'service started' JMX notification and when the MDB gets deployed the code in the start() method of the MBean is executed. I would not recommend this method necessarily since the specifying of the local-jndi-name is easier and reuses the JBoss dependency resolver but it could be used for some other cases.

Florian