Problem with destination's name using slash

[hendra_netm]

Hi guys,

Currently, I am using JBoss 1.3.0.GA with JBoss 4.2.0
I get strange behavior when using slash in queue name.

For example this queue name: /var/spool/test
will generate this exception: javax.naming.NameNotFoundException: spool not bound

<mbean code="org.jboss.jms.server.destination.QueueService"

 name="jboss.messaging.destination:service=Queue,name=/var/spool/test"

 xmbean-dd="xmdesc/Queue-xmbean.xml">

 <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>

 <depends>jboss.messaging:service=PostOffice</depends>

</mbean>

Fortunately, you can bound such name using server peer's deploy queue method.

Is this a bug? Or there is a rule about destination's name that forbids such kind of name?

Thank you for your attention.

Best Regards,
Hendra

[hendra_netm]

In linux the exception message is quite different:

Queue name: /var/spool/test
javax.naming.NameNotFoundException: var not bound

Any idea what the cause of this exception?

Best Regards,
Hendra

[mskonda]

I don't think (I may be wrong) that JBM supports subcontext creation during destination deployment (useful feature though).

That is, in your case, for creating /var/spool/test, it first has to create a context called var followed by another subContext call spool and then another subContext called test which, to my knowledge, JBM doens't do.

Thanks
/M

[hendra_netm]

hi /M,
Thanks for your comment.

It seems that JBM trying to do subcontext deployment.
In Windows, somehow, var context is available, so it continues to check spool sub-context, which is not available, then the exception is generated.

I suspect the culprit is not the deployer though, since I can deploy queue with that kind of name using JMX-Console.

The problem may lies somewhere inside the translation of destination's XML file.


In windows, I got another funny behavior.
Somehow, I can deploy queue using this name: /var/usr/test

I change the name into: /var/user/test, and it is failed (get this exception: javax.naming.NameNotFoundException: user not bound)
When I changed the name back to /var/usr/test, it is failed as the queue is still active??

This seems like bug, but I am not sure.

Best Regards,
Hendra

[timfox]

The queue/topic name should not contain a slash.

If you want to deploy the queue/topic at a specific place in the JNDI tree (e.g. /a/b/) then use the JNDIName attribute for this.

[hendra_netm]

Hi Tim,

Is it possible to set the JNDI name differently than the queue name in configuration? Or should I do it only via JMX?

Best Regards,
Hendra

[timfox]

Sure, just use the JNDIName attribute:

http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.CR2/html/configuration.html#conf.destination.queue.attributes.jndiName