[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

Perhaps I should open a JIRA for this? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4239663#4239663 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4239663 ___ jboss-user mailing

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

Sure, thanks. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4239714#4239714 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4239714 ___ jboss-user mailing list

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

Opened: https://jira.jboss.org/jira/browse/JBMESSAGING-1667. Thanks, Richard. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4239884#4239884 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4239884

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

The mbean ... name=emails represents a MBean name. This name is expected to be unique within the MBean server (which effectively means it needs to be unique with the application server). View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4239339#4239339 Reply

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

After some discussion about this, with Richard, in the JCA forum this now looks like either a bug or an unsupported feature in JBoss Messaging http://www.jboss.org/index.html?module=bbop=viewtopicp=4238959#4238959 View the original post :

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

Can you explain why you think this is a bug in JBM 1.x, I don't follow your reasoning here... View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4238969#4238969 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4238969

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

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 |

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

You could add a feature request JIRA if you like, if you want JBM 1.x to also support sub contexts on the name too. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4238979#4238979 Reply to the post :

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

In JBM 1.x, if you want to do this kind of thing you need to use JNDIName as Howard mentioned at the beginning of this thread. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4238977#4238977 Reply to the post :

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

Tim, I'm happy to add a feature request if this is outside spec. Before I do, can I ask you to double check the spec because this did work in JBoss 4.2.3.GA and JBoss MQ? Regards, Richard. P.S. Using JNDIName doesn't really work, because the queue name itself is not heirachical, so you can

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

Hi, to work around, you can use JNDIName and the queue name at the same time. The fact is if you use JNDIName, the queue name won't be used in JNDI binding anymore, so you can safely specify a hierarchical name. View the original post :

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

gaohoward, Thanks for the tip. Is there no internal JBoss Messaging requirement that queue names (not JNDINames) be unique? For example, can I do... mbean ... name=emails |attribute name=JNDINameapp1/emails/attribute | /mbean | | mbean ... name=emails |attribute

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

I don't think so. However it may not be JBM issue. It should be that the microcontainer doesn't allow two mbeans of same name to be deployed. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4239244#4239244 Reply to the post :

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

Thanks Tim. I have jumped this discussion across to: http://www.jboss.org/index.html?module=bbop=viewtopicp=4238065#4238065 Regards, Richard. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4238066#4238066 Reply to the post :

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

you probably need to specify the JNDIName attribute inside the . View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4237554#4237554 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4237554

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

you probably need to specify the JNDIName attribute inside the mbean. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4237555#4237555 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4237555

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

gaohoward, Thank you for your quick reply. Unfortunately using JNDIName gives the same error ('app' not bound). It's probably fair to say that app isn't bound, but I was kind of hoping JBoss Messaging would create it automatically (like JBoss MQ did). Regards, Richard. View the original

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

Can you please post the entire configuration file which gives this error and also the entire exception stacktrace? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4237574#4237574 Reply to the post :

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

destinations-service.xml: ?xml version=1.0 encoding=UTF-8? | | !-- | Messaging Destinations deployment descriptor. | | $Id: destinations-service.xml 85945 2009-03-16 19:45:12Z dimit...@jboss.org $ | -- | | server | |!-- | The Default Dead Letter

[jboss-user] [JBoss Messaging] - Re: Migrating 4.2.3.GA to 5.1.0.GA - queue hierarchies not s

The stacktrace shows the exception is thrown from the JCA adapter, not from JBoss Messaging. The generic JCA adapter is part of the application server project, it's not handled by the JBoss Messaging team. Your best bet would be to post in the JCA users forum. View the original post :