13 Replies Latest reply on Mar 25, 2011 4:50 AM by Tom Fennelly

    Messaging Queue error in ESb Deploy

    Vishal Novice

      Hi,

      I occassionally get an error on jboss esb server console saying some perticular message queue is not administratively defined but that queue seems to be started properly from the messages and also it works fine

      Vishal

        • 1. Re: Messaging Queue error in ESb Deploy
          Tom Fennelly Master

          More info please. Log snippets etc.

          • 2. Re: Messaging Queue error in ESb Deploy
            Vishal Novice

             

            00:20:39,000 ERROR [ExceptionUtil] SessionEndpoint[m5-88axm2qf-1-0i8bm2qf-4x9w1n-21o4c5] createQueue [v5-o8axm2qf-1-0i8bm2qf-4x9w1n-21o4c5]
            javax.jms.JMSException: There is no administratively defined queue with name:queue/nt_NTDest
             at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createQueue(ServerSessionEndpoint.java:289)
             at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$createQueue$aop(SessionAdvised.java:105)
             at org.jboss.jms.server.endpoint.advised.SessionAdvised$createQueue_6431069199924553036.invokeNext(SessionAdvised$createQueue_6431069199924553036.java)
             at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
             at org.jboss.jms.server.endpoint.advised.SessionAdvised$createQueue_6431069199924553036.invokeNext(SessionAdvised$createQueue_6431069199924553036.java)
             at org.jboss.jms.server.endpoint.advised.SessionAdvised.createQueue(SessionAdvised.java)
             at org.jboss.jms.wireformat.SessionCreateQueueRequest.serverInvoke(SessionCreateQueueRequest.java:74)
             at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
             at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:795)
             at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101)
             at org.jboss.remoting.Client.invoke(Client.java:1634)
             at org.jboss.remoting.Client.invoke(Client.java:548)
             at org.jboss.remoting.Client.invoke(Client.java:536)
             at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
             at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
             at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$createQueue$aop(ClientSessionDelegate.java:297)
             at org.jboss.jms.client.delegate.ClientSessionDelegate$createQueue_6431069199924553036.invokeNext(ClientSessionDelegate$createQueue_6431069199924553036.java)
             at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
             at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
             at org.jboss.jms.client.delegate.ClientSessionDelegate$createQueue_6431069199924553036.invokeNext(ClientSessionDelegate$createQueue_6431069199924553036.java)
             at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
             at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
             at org.jboss.jms.client.delegate.ClientSessionDelegate$createQueue_6431069199924553036.invokeNext(ClientSessionDelegate$createQueue_6431069199924553036.java)
             at org.jboss.jms.client.delegate.ClientSessionDelegate.createQueue(ClientSessionDelegate.java)
             at org.jboss.jms.client.JBossSession.createQueue(JBossSession.java:250)
             at org.jboss.internal.soa.esb.rosetta.pooling.JmsSession.createQueue(JmsSession.java:170)
             at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:511)
             at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:414)
             at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:402)
             at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:232)
             at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:214)
             at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:280)
             at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:248)
             at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
             at java.lang.Thread.run(Unknown Source)
            00:20:39,015 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
            00:20:39,000 ERROR [ExceptionUtil] SessionEndpoint[t5-o8axm2qf-1-0i8bm2qf-4x9w1n-21o4c5] createQueue [w5-o8axm2qf-1-0i8bm2qf-4x9w1n-21o4c5]
            javax.jms.JMSException: There is no administratively defined queue with name:queue/nt_tg
             at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createQueue(ServerSessionEndpoint.java:289)
             at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$createQueue$aop(SessionAdvised.java:105)
             at org.jboss.jms.server.endpoint.advised.SessionAdvised$createQueue_6431069199924553036.invokeNext(SessionAdvised$createQueue_6431069199924553036.java)
             at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
             at org.jboss.jms.server.endpoint.advised.SessionAdvised$createQueue_6431069199924553036.invokeNext(SessionAdvised$createQueue_6431069199924553036.java)
             at org.jboss.jms.server.endpoint.advised.SessionAdvised.createQueue(SessionAdvised.java)
             at org.jboss.jms.wireformat.SessionCreateQueueRequest.serverInvoke(SessionCreateQueueRequest.java:74)
             at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
             at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:795)
             at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101)
             at org.jboss.remoting.Client.invoke(Client.java:1634)
             at org.jboss.remoting.Client.invoke(Client.java:548)
             at org.jboss.remoting.Client.invoke(Client.java:536)
             at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
             at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
             at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$createQueue$aop(ClientSessionDelegate.java:297)
             at org.jboss.jms.client.delegate.ClientSessionDelegate$createQueue_6431069199924553036.invokeNext(ClientSessionDelegate$createQueue_6431069199924553036.java)
             at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
             at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
             at org.jboss.jms.client.delegate.ClientSessionDelegate$createQueue_6431069199924553036.invokeNext(ClientSessionDelegate$createQueue_6431069199924553036.java)
             at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
             at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
             at org.jboss.jms.client.delegate.ClientSessionDelegate$createQueue_6431069199924553036.invokeNext(ClientSessionDelegate$createQueue_6431069199924553036.java)
             at org.jboss.jms.client.delegate.ClientSessionDelegate.createQueue(ClientSessionDelegate.java)
             at org.jboss.jms.client.JBossSession.createQueue(JBossSession.java:250)
             at org.jboss.internal.soa.esb.rosetta.pooling.JmsSession.createQueue(JmsSession.java:170)
             at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:511)
             at org.jboss.internal.soa.esb.couriers.JmsCourier.pickupPayload(JmsCourier.java:414)
             at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:402)
             at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:232)
             at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:214)
             at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:280)
             at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:248)
             at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
             at java.lang.Thread.run(Unknown Source)
            00:20:39,015 INFO [QueueService] Queue[/queue/nt_NTDest] started, fullSize=200000, pageSize=2000, downCacheSize=2000
            


            you can see nt_Dest has been started successfully but still exceptions why are they there and how to get rid of them ?

            thanks

            • 3. Re: Messaging Queue error in ESb Deploy
              Kevin Conner Master

              You would appear to have a problem with your dependencies, the listener has started *before* the queue.

              • 4. Re: Messaging Queue error in ESb Deploy
                Vishal Novice

                thanks for reply how do i check or modify this ?

                • 5. Re: Messaging Queue error in ESb Deploy
                  Vishal Novice

                  how to ensure that the listenere doesnot stars before Queue ?

                  • 6. Re: Messaging Queue error in ESb Deploy
                    Daniel Bevenius Master

                    You specify this in the deployment.xml:

                    <jbossesb-deployment>
                    <depends>jboss.esb.quickstart.destination:service=Queue,name=quickstart_helloworld_Request_esb</depends>
                    <depends>jboss.esb.quickstart.destination:service=Queue,name=quickstart_helloworld_Request_gw</depends>
                    </jbossesb-deployment>


                    Almost all of the quickstart do this so you can take one an modify it.

                    regards,

                    /Daniel


                    • 8. Re: Messaging Queue error in ESb Deploy
                      Igor JStarter Novice

                      Did that really solve your problem ???

                       

                      I imported the deployment.xml from a quickstart, edited the new queue, added it to build path...

                       

                      But still i get the same error...

                       

                      Caused by: javax.jms.JMSException: There is no administratively defined queue with name:/queue/CdrClientQueue

                       

                      HOW TO DEFINE A NEW QUEUE ???

                       

                      Please help!

                      • 9. Re: Messaging Queue error in ESb Deploy
                        seb fou Newbie

                        i get this error, after renamed a queue.

                        Try to clear JBM Tables or or drop the /data folder if you use hsqldb

                        and restart

                        • 10. Re: Messaging Queue error in ESb Deploy
                          Igor JStarter Novice

                          What JBM tables ? How can I do that ? I can't find any /data table in mysql.

                           

                          I'm trying to create a queue on two ways :

                           

                          1. Administration console -> Resources -> JMS destination and i get:

                          Failed to add Resource (see app server log  for additional details):  java.lang.RuntimeException:Failed to process  template. ->  java.lang.RuntimeException:java.io.FileNotFoundException:  D:\KKISSWORK\jboss-5.1.0.GA\server\default\deploy\queue\CdrClientQueue-service.xml  (The system cannot find the path specified) ->  java.io.FileNotFoundException:D:\KKISSWORK\jboss-5.1.0.GA\server\default\deploy\queue\CdrClientQueue-service.xml  (The system cannot find the path specified)

                           

                          2. I create the deployment.xml, the jbm-queue-service and defined the new queue and i get :

                          Caused by: javax.jms.JMSException: There is no administratively defined queue with name:/queue/CdrClientQueue

                          Do I need to make a war file (to be sure that the queue starts before the listener) ?

                           

                          3. there is an option session.createQueue(name, object). Is this an option ?

                           

                          Omg.)

                          • 11. Re: Messaging Queue error in ESb Deploy
                            Igor JStarter Novice

                            I'm I getting closer ?

                             

                            Exception in thread "main" javax.naming.NameNotFoundException: CdrClientQueue not bound ?

                            • 12. Re: Messaging Queue error in ESb Deploy
                              Sohan Agate Newbie

                              Hi Even I am having the same problem.Has anybody found a solutiion to this problem????please post in the forum

                              • 13. Re: Messaging Queue error in ESb Deploy
                                Tom Fennelly Master

                                Guys... please refer to the quickstarts.  The vast majority of them are using JMS listeners and are configured with the dependencys etc as they should be.  Play with one of them first... modify... break... fix etc.