JMS-Not Getting Reply

I am using pub.jms:sendAndWait publishing service to get a reply from subscriber service pub.jms:reply. while running subscribing service I’m getting this error:
I’m doing a POC in which from publisher I’m sending input values and in subscriber I’m doing a simple math operation and getting result of math operation as a reply to the publisher’s end.
Launch started: 2023-01-18 15:44:14.894
Configuration name: sendOperationResults
Configuration location: C:/Users/Innovantage/workspace105/.metadata/.plugins/org.eclipse.debug.core/.launches/sendOperationResults.launch

com.wm.app.b2b.server.ServiceException: [ISS.0134.9999] JMS subsystem experienced an unexpected error: [ProducerFacade#sendReply] No ReplyContext found.
at pub.jms.reply(jms.java:350)
at sun.reflect.GeneratedMethodAccessor150.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:411)
at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:739)
at wm.bci.internal.BciServiceInvokeNotifier.process(BciServiceInvokeNotifier.java:32)
at com.wm.ps.serviceMock.ServiceInterceptor.process(ServiceInterceptor.java:360)
at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46)
at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:61)
at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:250)
at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:56)
at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:178)
at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:334)
at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:41)
at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:401)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:611)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:423)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:381)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:253)
at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:236)
at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:267)
at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:668)
at com.wm.lang.flow.FlowState.stepIncremental(FlowState.java:582)
at com.wm.lang.flow.FlowState.invoke(FlowState.java:471)
at wm.server.flowdebugger.stepFlow(flowdebugger.java:1088)
at wm.server.flowdebugger.execute(flowdebugger.java:551)
at sun.reflect.GeneratedMethodAccessor149.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:421)
at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:739)
at wm.bci.internal.BciServiceInvokeNotifier.process(BciServiceInvokeNotifier.java:32)
at com.wm.ps.serviceMock.ServiceInterceptor.process(ServiceInterceptor.java:360)
at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46)
at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:61)
at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:250)
at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:56)
at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:178)
at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:334)
at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:41)
at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:401)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:611)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:423)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:381)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:253)
at com.wm.app.b2b.server.comm.DefaultServerRequestHandler.handleMessage(DefaultServerRequestHandler.java:127)
at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:163)
at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:223)
at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:430)
at com.wm.util.pool.PooledThread.run(PooledThread.java:134)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.wm.app.b2b.server.jms.JMSSubsystemException: [ISS.0134.9999] JMS subsystem experienced an unexpected error: [ProducerFacade#sendReply] No ReplyContext found.
at com.wm.app.b2b.server.jms.producer.ProducerFacade.sendReplyFromTrigger(ProducerFacade.java:787)
at pub.jms.reply(jms.java:343)
… 51 more

Launch completed: 2023-01-18 15:44:14.895

Hi Zainul,

can you share a screenshot fo the service where you prepare the Reply showing the mappings for pub.jms:reply?

For me it looks like you are not mapping the original context from the received message to the context in the reply message.Therefore the pub.jms:sendAndWait step is not recognizing the replied message to the send message and cannot continue.

Regards,
Holger



screenshot 1 (subscribing service)
screenshot 2(publishing service)
I’m getting data through a reply from subscribing service and also getting data in subscribing service, which is being published through the publisher.

but while I’m debugging my service all steps going fine except reply service

Hi Zainul,

please refer to the “Using webMethods Integration Server to Build a Client for JMS” guide for further informations about replying to a JMS message.

Regards,
Holger

@Zainul_Abideen Error Message : com.wm.app.b2b.server.jms.JMSSubsystemException: [ISS.0134.9999] JMS subsystem experienced an unexpected error: [ProducerFacade#sendReply] No ReplyContext found.

Reason for the above error is due to NO JMSReplyMessage is from subscriber side. So Make sure your subscriber was able to send back the reply Message within the timeout value.

Kindly make sure your IS is able where able to publish to TOPIC/QUEUE and subscribe to TOPIC/QUEUE individually. if this is working fine then narrow down to your service timeout config

if you have setup the timeout value in pub.jms:sendAndWait or pub.jms:waitForReply ? Because this could also one other reason for noReplyContext eventhough your reply service is sending replyMessage

Note : I am able to re-produce the same error message this is caused by no showing up of the JMSReplayMessage from consumer side.