We are using sonic 8.5 and We have a following requirement
We need to send a message to a say Q1 and We need to activate another ESB Process when we recive the reply from another Q say Q2
Is it Possible to use Sonic Dispatch step for this.
My Dispatch sample given following time out message it want trigger the destination ESB
Appriciate if anyone can help on this
/**********
Error Message: | Time out interval of `30` seconds has been exceeded while waiting for response from endpoint `Sample.Q5` corresponding to address `DispatchResponse:PROCESS` (Call timed-out) (Call timed-out) (Error Code:XQ_SERVICE_EXCEPTION) | ||
Step Name: | RequestReplyDispath | Service: | dev.Dispatch |
Process Name: | RequestReplyDispatch | Top Process: | RequestReplyDispatch |
Container Name: | dev_ESBCore | Host: | THARANGAH |
Details: | com.sonicsw.xq.XQServiceException: Time out interval of `30` seconds has been exceeded while waiting for response from endpoint `Sample.Q5` corresponding to address `DispatchResponse:PROCESS` (Call timed-out) (Call timed-out) at com.sonicsw.xq.service.dispatch.DispatchService.doService(DispatchService.java:112) at com.sonicsw.esb.service.common.impl.AbstractSFCServiceImpl.service(AbstractSFCServiceImpl.java:267) at com.sonicsw.xqimpl.service.debug.DebugServiceInterceptor.intercept(DebugServiceInterceptor.java:118) at com.sonicsw.xqimpl.service.XQServiceChain$XQInterceptorServiceWrapper.intercept(XQServiceChain.java:495) at com.sonicsw.xqimpl.service.XQServiceChain$XQInterceptorServiceWrapper.service(XQServiceChain.java:484) at com.sonicsw.xqimpl.service.XQServiceChain.service(XQServiceChain.java:152) at com.sonicsw.xqimpl.service.ServiceMessageHandler.callService(ServiceMessageHandler.java:424) at com.sonicsw.xqimpl.service.ServiceMessageHandler.handleMessageCommon(ServiceMessageHandler.java:236) at com.sonicsw.xqimpl.service.ServiceMessageHandler.handleMessage(ServiceMessageHandler.java:99) at com.sonicsw.xqimpl.service.XQDispatcher.onMessage(XQDispatcher.java:436) at com.sonicsw.esb.itinerary.model.EsbStepNode.doExecute(EsbStepNode.java:269) at com.sonicsw.esb.itinerary.model.EsbStepNode.execute(EsbStepNode.java:167) at com.sonicsw.esb.process.model.impl.DefaultActivityNode.offerIncoming(DefaultActivityNode.java:140) at com.sonicsw.esb.itinerary.engine.ItineraryEngine.executeProcess(ItineraryEngine.java:317) at com.sonicsw.esb.itinerary.engine.ItineraryEngine.handleToken(ItineraryEngine.java:177) at com.sonicsw.esb.itinerary.engine.ItineraryEngine.handleMessage(ItineraryEngine.java:167) at com.sonicsw.xqimpl.endpoint.container.EndpointContextContainer.onMessage(EndpointContextContainer.java:112) at com.sonicsw.xq.connector.jms.JMSEndpointMessageListener.onMessage(JMSEndpointMessageListener.java:243) at progress.message.jimpl.Session.deliver(Session.java:3078) at progress.message.jimpl.Session.run(Session.java:2481) at progress.message.jimpl.Session$SessionThread.run(Session.java:2873) Caused by: com.sonicsw.xq.XQEndpointTimeoutException: Call timed-out at com.sonicsw.xq.connector.jms.JMSEndpointConnection.verifyReplyMessageAndRetry(JMSEndpointConnection.java:1302) at com.sonicsw.xq.connector.jms.JMSEndpointConnection.callWithQoS(JMSEndpointConnection.java:1512) at com.sonicsw.xq.connector.jms.JMSEndpointConnection.callWithQoS(JMSEndpointConnection.java:1360) at com.sonicsw.xq.connector.jms.JMSEndpointStandalone.callWithQoS(JMSEndpointStandalone.java:255) at com.sonicsw.xq.service.dispatch.DispatchService.doService(DispatchService.java:108) ... 20 more |
*************/