7 Replies Latest reply on Jul 29, 2009 8:57 AM by Daniel Bevenius

    Problem in configuration of ESBService

    viral mehta Newbie

      Hi I am using jboss esb 4.4 GA and I am facing problem on calling esb service ..

      In my application I have configured esb service as below in jboss-esb.xml

      <service category="ProcessService" name="EndTask" description="To initiate the process" >
       <listeners>
       <jms-listener name="process_endTask"
       busidref="endTaskProcess"
       maxThreads="1"/>
       </listeners>
       <actions>
       <action class="com.tcs.sgv.wfms.actions.EndTaskAction"
       process="endTaskRequest" name="EndTaskAction">
       </action>
       </actions>
       </service>


      and for this service I had initially configured listener as below



      <jms-bus busid="endTaskProcess">
       <jms-message-filter dest-type="QUEUE" dest-name="queue/endtask_Request_queue" />
       </jms-bus>



      and then I changed the listener by altering queue name as below to follow some naming standards

       <jms-bus busid="endTaskProcess">
       <jms-message-filter dest-type="QUEUE" dest-name="queue/process_endTaskRequest_queue" />
       </jms-bus>



      but after this change I am always getting run time error as below


      org.jboss.soa.esb.couriers.CourierException: javax.jms.JMSException: This destination does not exist !QUEUE.queue/endtask_Request_queue_reply
       at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageProducer(JmsCourier.java:360)
       at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:188)
       at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:201)
       at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.messageTo(ActionProcessingPipeline.java:521)
       at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.replyTo(ActionProcessingPipeline.java:443)
       at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:376)
       at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
       at java.lang.Thread.run(Thread.java:595)
      
      
      
      Caused by: javax.jms.JMSException: This destination does not exist !QUEUE.queue/endtask_Request_queue_reply
       at org.jboss.mq.server.JMSDestinationManager.createQueue(JMSDestinationManager.java:613)
       at org.jboss.mq.server.JMSServerInterceptorSupport.createQueue(JMSServerInterceptorSupport.java:111)
       at org.jboss.mq.server.TracingInterceptor.createQueue(TracingInterceptor.java:259)
       at org.jboss.mq.server.JMSServerInvoker.createQueue(JMSServerInvoker.java:117)
       at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:139)
       at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:419)
       at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:398)
       at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:761)



      I dint get from where esb is putting its reply on this reply_queue which at all not present in any of my configurations..

      Thanks and Regards
      vnm

        • 1. Re: Problem in configuration of ESBService
          viral mehta Newbie

          in additon in runtime follwing error is generated


          10:22:39,220 WARN [ServiceInvoker] Possible configuration error while using Courier for EPR [JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue
          /process_endTaskRequest_queue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProp
          erties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:Refer
          enceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connect
          ion-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDG
          E/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ]] and Service [ProcessSe
          rvice:EndTask] and Message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/process_endTaskRequest_queue/>, <wsa:ReferencePrope
          rties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1
          :1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>,
          <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferencePro
          perties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted :
          false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ReplyTo: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/e
          ndtask_Request_queue_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.fac
          tory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:Referenc
          eProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection
          -factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:message-selector : jbossESBresponseUUID='feea564d-c421-4a11-bbe7-0a4d7788d988'/>, <wsa:Refer
          enceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transa
          cted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ]]. Unable to create Message Consumer
          10:22:39,261 INFO [LeaveApprovalImpl] htMoveTab====={LgSubInitOwner=-, SubjId=7011, DocDesc=Leave Request of TCS SO1, UnitID=DP101_US1, LgSubInitEmp=-, UserN
          ame=DP101_US1, Node_id=ND242, DeptId=DP101, LocID=LC1, DocTitle=1556/TCS/2009, InitEmp=ET1003, LangID=en_US, NodeRefID=JB12819, JobID=JB12819, InitOwner=DP101
          _SO1, DocTypeId=DT5, appPkyId=EL1924, doc_cur_ver=1.00, DocId=DC9360}
          10:22:39,274 INFO [ServiceInvoker] Unresponsive EPR: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/process_endTaskRequest_queue/>, <wsa:Re
          ferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url
           : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type
           : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:
          ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:t
          ransacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] for message: header: [ To: JMSEpr [ PortReference < <wsa:Addres
          s jms://127.0.0.1:1099/queue/endtask_Request_queue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/
          >, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.int
          erfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProper
          ties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-m
          ode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] Re
          plyTo: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/endtask_Request_queue_reply/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.
          url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jb
          ossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:sp
          ecification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:message-selector :
          jbossESBresponseUUID='feea564d-c421-4a11-bbe7-0a4d7788d988'/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknow
          ledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/>
           > ] ]


          And now what amazed me the most is all errors including the error I mentioned in my previous post dont come always at runtime but comes frequanlty in between succesfull hits


          • 2. Re: Problem in configuration of ESBService
            bingozzz bingozzz Newbie

            your esb project must include a jms queue config file.
            you can define a jms queue and a reply queue:

            <depends optional-attribute-name="DestinationManager">
            jboss.mq:service=DestinationManager



            <depends optional-attribute-name="DestinationManager">
            jboss.mq:service=DestinationManager

            • 3. Re: Problem in configuration of ESBService
              viral mehta Newbie

              Hi cammette,
              I have already configured queue and reply queue in jbmq-queue-service.xml...Tats not an issue

              Thanks & Regards
              vnm

              • 4. Re: Problem in configuration of ESBService
                Daniel Bevenius Master

                Hi,

                sounds like you have a stale EPR in the database.
                You can simply clean out you database if this is not a production system.
                Or you can read about setting 'org.jboss.soa.esb.failure.detect.removeDeadEPR' in the jbossesb-properties.xml file.
                More information about that property can be found in the AdministrationGuide.pdf, see the section "Clustering and Fail-over support" or simply search for the property specified above.

                Regards,

                /Daniel

                • 5. Re: Problem in configuration of ESBService
                  viral mehta Newbie

                  Hi Daniel,
                  Thanks for your reply...I am going to try whatever u mentioned..But one thing I want to ask is that my jboss esb is using default hsqldb so the persistance is temporary at runtime and under this scenario can this type of prob should cm?

                  • 6. Re: Problem in configuration of ESBService
                    viral mehta Newbie

                    Hi Daniel,
                    Thank you so much for your solution...It is working now..

                    Thanks & Regards
                    vnm

                    • 7. Re: Problem in configuration of ESBService
                      Daniel Bevenius Master

                      Hi vmn,

                      glad you have this working now :)

                      I want to ask is that my jboss esb is using default hsqldb so the persistance is temporary at runtime and under this scenario can this type of prob should cm?

                      This database is in-memory but will persists data to server_name/data/hypersonic upon shutdown.
                      So if you are in development can simply shutdown your server and remove that directory.

                      Regards,

                      /Daniel