Why is JBoss trying to use HornetQ?

[mataratones]

We have a puzzling error caused by JBoss trying to use HornetQ unsuccessfully:

Caused by: javax.jms.InvalidDestinationException: Not a HornetQDestination:JBossQueue[quickstart_helloworld_Request_esb]

        at org.hornetq.jms.client.HornetQSession.createConsumer(HornetQSession.java:372)

        at org.hornetq.jms.client.HornetQSession.createConsumer(HornetQSession.java:358)

        at org.jboss.internal.soa.esb.rosetta.pooling.WrappedSession.createConsumer(WrappedSession.java:167)

        at org.jboss.internal.soa.esb.rosetta.pooling.JmsSession.createConsumer(JmsSession.java:229)

        at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:629)

The thing is, we don't use HornetQ for anything.  I recursively grep'd "hornetq" in the server profile directory and the only places it shows up are in jar files and logs -- it isn't in any configuration files.  Why would JBoss be trying to use HornetQ?

[nazia24]

Hi,

   May be this will answer your query

  IGetJavax.jms.InvalidDestinationException.ThisDestinationDoesNotExist

[jaikiran]

Derek Croxton wrote:

We have a puzzling error caused by JBoss trying to use HornetQ unsuccessfully:

Caused by: javax.jms.InvalidDestinationException: Not a HornetQDestination:JBossQueue[quickstart_helloworld_Request_esb]

        at org.hornetq.jms.client.HornetQSession.createConsumer(HornetQSession.java:372)

        at org.hornetq.jms.client.HornetQSession.createConsumer(HornetQSession.java:358)

        at org.jboss.internal.soa.esb.rosetta.pooling.WrappedSession.createConsumer(WrappedSession.java:167)

        at org.jboss.internal.soa.esb.rosetta.pooling.JmsSession.createConsumer(JmsSession.java:229)

        at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:629)

Moved the thread to JBoss ESB forum since the stacktrace suggests this might have to do with ESB.

[tcunning]

Derek,

Can we get some more background on this?   Are you trying to run helloworld?    Is this a custom application, maybe that didn't rename all the helloworld stuff?     What container are you using?