1 Reply Latest reply on Feb 24, 2011 4:32 PM by Tom Cunningham

    javax.jms.JMSException: There is no administratively defined queue with name:queue/"queuename"

    Mads Moelgaard Andersen Newbie

      Hi

      I've been seing this a couple of times lately.

       

      javax.jms.JMSException: There is no administratively defined queue with name:queue/"queuename"

       

      Setup:

      server1 SOA-P 4.3 CP02 with ear deployed

      server2 SOA-P 4.3 CP02 with esb deployed

       

      ESB Services from server2 has been registered on server1.

       

      deployment.xml and jbm-queue-service.xml of the esb appears to be OK.

       

      the esb message queues are defined on an oracle db.

       

      Services on the esb are called using serviceInvoker.deliverAsync

       

      I wonder alot about jbossesb-properties.xml what the purpose is for that file?

       

      I'ev read JBoss ESB 4.3 Message Store pdf, but everything is not clear to me?

       

       

      If I want to expose services through the esb is the file mandatory or optional?

       

      If mandatory I guess the properties "dbstore" must always to point to the oracle DB either as a StandaloneConnectionManager or a J2eeConnectionManager is that correct?

       

      If not, what then?

       

      If the file is optional how are messages then delivered to the proper queue?

       

      I know these questions might seem trivial - but the answers might make a great difference to me :-)

       

      Thanks in advance.

       

      Best regards

      Mads M Andersen