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
kennardconsulting wrote : if I declare a heirarchical JNDI queue in my
destinations-service.xml it shouldn't fail just because I don't also deploy an
app that depends on it.
|
You mean, if you create a queue with that hierarchical JNDI name and don't
deploy any applications which use this
And please also post the exact queue configuration file contents. The first
post contains a combination of JBoss MQ and JBoss Messaging queue
configurations. Just want to make sure we are discussing about the correct file.
View the original post :
I just tried this with the default DLQ configuration that comes with JBoss:
mbean code=org.jboss.jms.server.destination.QueueService
| name=jboss.messaging.destination:service=Queue,name=DLQ
| xmbean-dd=xmdesc/Queue-xmbean.xml
| attribute
kennardconsulting wrote : The JBoss Messaging guys (you have them to blame
for this :) suggested I refer this issue to you.
|
Let us get back to the same forum entry and pick some info from there, I see
activations...@1030063(ra=org.jboss.resource.adapter.jms.jmsresourceadap...@e0863a
Also did you confirm from the JNDI view if the Queues are bound to JNDI
properly, I don't think so.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4238706#4238706
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4238706
jaikiran,
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
jaikiran,
Thank you for staying with me. Your patience is most appreciated.
Unfortunately what you suggested did not work.
Even if it had, I'm not sure it would have been a good idea because jboss.xml
is app-specific whereas destinations-service.xml is 'JBoss wide': if I declare
a
18:31:23,437 WARN [JmsActivation] Failure in jms activation
org.jboss.resource.adapter.jms.inflow.J
|
msactivations...@1030063(ra=org.jboss.resource.adapter.jms.jmsresourceadap...@e0863a
destination=que
| ue/avant-ss/imports1 destinationType=javax.jms.Queue tx=true durable=false
