[jboss-user] [JCA/JBoss] - Re: 4.2.3.GA to 5.1.0.GA regression - heirarchical JNDI name

[jaikiran]

"kennardconsulting" wrote : 
  | Your example uses the attribute JNDIname, but the queue name is still just DLQ...
  | 
  | <mbean code="org.jboss.jms.server.destination.QueueService"
  |   | name="jboss.messaging.destination:service=Queue,name=DLQ">
  | 
  | ...it is the queue name I wanted to be heirarchical. I thought by putting it under a heirarchy with the app name I could avoid naming conflicts in future? I am probably mistaken, however this worked in JBoss 4.2.3.

Ah, i see what you are saying, now :) And i could reproduce it too with the default DLQ:

<mbean code="org.jboss.jms.server.destination.QueueService"
  |       name="jboss.messaging.destination:service=Queue,name=jaikiran/DLQ"
  |       xmbean-dd="xmdesc/Queue-xmbean.xml">
  |       <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
  |       <depends>jboss.messaging:service=PostOffice</depends>
  |    </mbean>
This one fails to deploy:

12:45:07,184 ERROR [ExceptionUtil] Queue[/queue/jaikiran/DLQ, name=jaikiran/DLQ] startService
  | javax.naming.NameNotFoundException: jaikiran not bound
  |         at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
  |         at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
  |         at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
  |         at org.jnp.server.NamingServer.rebind(NamingServer.java:244)
  |         at org.jnp.server.NamingServer.rebind(NamingServer.java:247)
  |         at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:575)
  |         at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:540)
  |         at org.jboss.jms.server.DestinationJNDIMapper.registerDestination(DestinationJNDIMapper.java:142)
  |         at org.jboss.jms.server.destination.QueueService.startService(QueueService.java:150)
  | 

Let's get back to your original post in the JBoss Messaging forum to discuss this, since this now looks like a bug in JBoss Messaging or an unsupported feature.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238959#4238959

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4238959