Queue lookup failing (because it is not being created)

[petal1]

Hello,

I'm struggling with the configuration of HornetQ. I am migrating from JBoss4.0.4.GA (which had JBoss MQ) to JBoss6.0.0.Final with HornetQ.

I had an issue last week where the lookup of a queue was failing. I noticed on my old JBoss4.0.4 machines that a netstat -an showed:

    Proto  Recv-Q Send-Q Local Address           Foreign Address         State

    tcp              0          0  0.0.0.0:1099             0.0.0.0:*               LISTEN

but on JBoss6 showed:

    Proto  Recv-Q Send-Q Local Address           Foreign Address         State

    tcp              0          0  127.0.0.1:1099             0.0.0.0:*               LISTEN

I changed the JBoss startup command to include "-b 0.0.0.0" and my lookup (from an external Java client program running on the same machine) was successful.

Today, I restarted JBoss (again with "-b 0.0.0.0") and the lookup fails - javax.naming.NameNotFoundException: MyQueue not bound. Sure enough I cannot see the queue in admin-console. I'm not sure what's different - why are my queues and topics not being created when JBoss starts? I have a file deploy/hornetq/myqueues-hornetq-jms-service.xml with the following contents:

    <configuration xmlns="urn:hornetq"

               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

               xsi:schemaLocation="urn:hornetq /schema/hornetq-jms.xsd">

        <queue name="MyQueue">

            <entry name="/queue/MyQueue"/>

        </queue>

    </configuration>

and my java jndi lookup program is:

    env.put (javax.naming.Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");

    env.put (javax.naming.Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");

    env.put (javax.naming.Context.PROVIDER_URL, "jnp://localhost:1099");

    context = new InitialContext(env);

    Object o = context.lookup("queue/MyQueue");

Can anyone please tell me why I have seen the inconsistent behaviour, and what is wrong with the hornetq configuration - because from what I've seen having the config file present should be enough to have the queue created when JBoss is started.

Thanks,

Paul

[ataylor]

if you are getting "javax.naming.NameNotFoundException: MyQueue not bound" its because either the queue hasnt been deployed or you are using the wrong jndi name. Take a look at one of the HornetQ examples, there are plenty of them.

[petal1]

As I said in my post, I can see the queue is not deployed. I included the location, name, and contents of the queue configuration file in my post - and they would appear to match the documentation as far as I can tell, so there should be no reason that the queue is not deployed.

[jbertram]

Any errors in your log when you start the server?

[petal1]

No errors in boot.log or server.log.

boot.log and server.log contain the following two lines repeated several times:

13:35:55,311 INFO  [HornetQActivation] awaiting topic/queue creation queue/MyQueue

13:35:57,337 INFO  [HornetQActivation] Attempting to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1f06324 destination=queue/MyQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15)

and I cannot see the queue using jboss admin-console.

[jbertram]

Try renaming myqueues-hornetq-jms-service.xml to myqueues-hornetq-jms.xml.

[petal1]

Thank you!

I had already renamed the files as you suggested but had reverted to the wrong names accidentally.