JMS connection error

,
1

Hi,

In our production environment. we are getting the below error for some transactions, but when we resubmit it without changing anything, its processing successfully. I did JNDI lookup and the connection alias is also enabled. Could you please help.

An error occurred invoking the processing service ICA_B2B_Transport.outbound.DespatchAdviceDSD:sendDAContractToJMS for this document. The original error was com.wm.lang.flow.FlowException: Error in sendDAContractToJMS: [ISS.0134.9009] Unable to send message to JMS provider “B2B_JMSConn_Out”: com.wm.app.b2b.server.ISRuntimeException: [9037] Unable to enlist JMS resource in transaction
at com.wm.lang.flow.FlowExit.getFailure(FlowExit.java:289)
at com.wm.lang.flow.FlowState.willExit(FlowState.java:238)
at com.wm.lang.flow.FlowSequence.invoke(FlowSequence.java:268)
at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:511)
at com.wm.lang.flow.FlowState.step(FlowState.java:389)
at com.wm.lang.flow.FlowState.invoke(FlowState.java:360)
at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1080)
at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:640)
at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:39)
at com.wm.app.b2b.server.in

Regards
Jyoti

2

You can try to disable/enable the JMS connection associated with this trigger.

If you still see the issue in the long run contact support there might be some fixes.

3

Hi,

Connection alias restart didn’t resolve the issue. We still face the same problem.
I need to contact support for this.
Meanwhile, could someone suggest some more solutions for this.

Regards
Jyoti

4

As 9.6 is out of support, did not get help from SAG support.

Regards
Jyoti

5

Since you are already OOM/S I would suggest you to see check the code for the affected services (refactor if needed) or install the latest fixes on a sandbox environment and try to reproduce the issue.

6

Hi Jyoti,

Usually by refreshing the JMS connection alias associated with the JMS trigger will resolve the issue.

Couple of things to check

Is it happening only for a specific trigger?
Is it happening in Lower environments as well for same trigger?
Also, what is the IS fix level in Production?

Regards,
Syed Faraz Ahmed

7

Hi Syed,

Its at the publishing end, when we are sending the doc using pub.jms:send service.
Its also very strange that, its happening only in Production, not any of the lower environment.
We have IS_9.6_Core_Fix5 installed in production.

Regards
Jyoti