MQJMS2007: failed to send message to MQ queue

[Former Member]

Hi Experts ,

Messages failing to reach MQ .

Flow : ECC ---> PI ---(via JMS channel ) -

---

> Mqueues

Error message :-- Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connector for ConnectionProfile of channel: CC_ADM_Central_JMS_CostOfSales_BGTMQ_Receiveron node: 315706250 having object id: 3421802333e835d8b655985600def47b encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///PKW.BGT.SAP.COSTOFSALES.XML?targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 1319196071093 JMSCorrelationID:4e97b7da-938f-00ad-e100-80000ad38114 JMSDestination: queue:///PKW.BGT.SAP.COSTOFSALES.XML?targetClient=1 JMSReplyTo: null JMSRedelivered: false JMSXDeliveryCount:0 <?xml version="1.0" encoding="UTF-8"?> <ZZFUNC01><IDOC BEGIN="1"><EDI_DC40 SEGMENT="1"><TABNAM>EDI_D Another 7,470 character(s) omitted: javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue

Temporary workaround: Restarting the channels and resending the failed messages from the adapter engine and they are flowing successfully

What could be the possible root cause , am facing the issue from past few weeks . Can anyone let me know if this is the issue with the JMS receiver channel or with the Mqueues end ?

[Former Member · Accepted solution]

1.

> Please set the parameter "Reconnect If Exception Text Starts With" to "MQJ*"

> Set the parameter "Wait before reconnect" = 10000

> Also the parameter "Wait After Message Error" = 10000

2. Please ensure the note below is applied (then check "Connect on Demand" option).

#1535589 - JMS Connect on Demand: java.lang.NullPointerException

After both, the connection should work correctly on the receiver JMS channel. Please monitor and let us know.

[Former Member]

The error should also contain a reason code, which is missing in your post. It is most likely that n/w problem or non-availability of the MQ queue while sending the message is causing the failure. Check SAP Note 873861 (J2EE JMSAdapter: 1st msg failed after MQSeries shutdown) to deal with the problem.

If you are using JMS senders on any of your interfaces, use mq series clinet v7 jar files (refer Note 747601 - J2EE JMSAdapter: MQSeries libraries)

Check the following notes for more information

Note 1086303 - XI JMS Adapter and IBM Websphere MQ: FAQ

Note 1450509 - JMS Adapter - IBM MQ reconnect and message retry issues