3 Replies Latest reply on Nov 2, 2011 5:45 AM by ataylor

Exposing core queues via JNDI?

jdahlbom Nov 1, 2011 11:14 AM

For purposes of using a core bridge, I have defined a queue in hornet-configuration.xml, and set it as a source for a core bridge (as in the bridge example):

<address>/jms/notificationRequestQueue</address>

</queue>

</queues>

<queue-name>jms.queue.notificationQueue</queue-name>

<forwarding-address>jms.queue.notificationQueue</forwarding-address>

<reconnect-attempts>-1</reconnect-attempts>

<static-connectors>

<connector-ref>netty-remote</connector-ref>

</static-connectors>

</bridge>

</bridges>

Now, I need to expose that (core) queue through JNDI so that my application can use it.

So far I have been able to trivially expose any queues to JNDI by defining them in the hornetq-jms.xml,

but this one needs to be defined before the bridge, so that option is not available.

How do I expose a Hornetq core queue to JNDI (as JMS queue)?

1. Re: Exposing core queues via JNDI?

clebert.suconic Nov 1, 2011 2:24 PM (in response to jdahlbom)

It doesn't make much sense to expose core-queues through JNDI. Core-queues are just strings.. you can just create a producer on a core-queue such as coreSession.createProducer("my-address"); or coreSession.createConsumer("my-queue");
Actions
2. Re: Exposing core queues via JNDI?

jdahlbom Nov 2, 2011 5:18 AM (in response to clebert.suconic)

Thank you for the tip, that clarified the core queue concept for me a bit.

I reverted to using JMS bridge instead of the core bridge.
This approach got me further on faster, even though it is not
entirely solved yet. But that's an issue for another post..
Actions
3. Re: Exposing core queues via JNDI?

ataylor Nov 2, 2011 5:45 AM (in response to jdahlbom)

I reverted to using JMS bridge instead of the core bridge.
I would recommend usingf the core bridge as it will outperform the JMS bridge, is there a reason you cant use it?
Actions

Go to original post