When the MBean name contains a "hierarchy" and the destination configuration does not contain a JNDIName attribute, like this: | <mbean code="org.jboss.jms.server.destination.QueueService" | name="jboss.messaging.destination:service=Queue,name=jaikiran/DLQ" | xmbean-dd="xmdesc/Queue-xmbean.xml"> | (note the use of name=jaikiran/DLQ) org.jboss.jms.server.DestinationJNDIMapper while registering the destination, will internally try to register it at queue/jaikiran/DLQ: 12:45:07,184 ERROR [ExceptionUtil] Queue[/queue/jaikiran/DLQ, name=jaikiran/DLQ] | ... | at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:540) | at org.jboss.jms.server.DestinationJNDIMapper.registerDestination(DestinationJNDIMapper.java | :142) | It considers the jaikiran/DLQ as one continuous name. But when a / is used for a name being bound to JNDI, the name gets parsed into sub-context. So the DestinationJNDIMapper is trying to bind it as follows: | queue | | | |--- jaikiran | | | |--- DLQ But since the jaikiran "sub-context" is not created, the JNDI bind fails. P.S: I am not claiming its a bug. It might even be an unsupported feature. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238972#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...