JMS Receiver Adapter Catching MQ Exceptions

[Former Member]

Hi Experts,

We are running into an issue with our JMS receiver adapter failing PI. We are trying to send transactions via the adapter to a MQ Series' queue but it is failing after no transactions have been sent after a period of 3 hours or more. The only way we can flush the queue is to change the setting on the adapter to Bypass, restart the adapter and then resend the message. Once we do this, everything runs fine throughout the day. It seems to be the amount of time between transactions be processed on the queue. For instance, last night the last transaction processed successfully was at 7:36pm EST. Then around 11:40pm EST we tried sending another and this is when we caught an exception from MQ once again. We have tried everthing that we know of u2013 we thought it might have been a background job running on PI that causes the issue but last night proved that it wasnu2019t the issue since it occurred before midnight. I feel that the issue is between our JMS connection and your MQ. Below is the message log of the transaction:

What course of action should we take next in diagnosing the issue?

Audit Log for Message: 1c728f10-2044-0441-0a04-604e2cf00000

Time Stamp Status Description

2009-05-21 22:40:48 Success Message successfully received by messaging system. Profile: XI URL: http://bus0157:52000/MessagingSystem/receive/AFW/XI Credential (User): PIPISUSER

2009-05-21 22:40:48 Success Using connection JMS_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.

2009-05-21 22:40:48 Success Message successfully put into the queue.

2009-05-21 22:40:48 Success The message was successfully retrieved from the receive queue.

2009-05-21 22:40:48 Success The message status set to DLNG.

2009-05-21 22:40:48 Success Delivering to channel: JMS_IDOC_SPK_RCV

2009-05-21 22:40:48 Success MP: Entering module processor

2009-05-21 22:40:48 Success MP: Processing local module localejbs/SAP XI JMS Adapter/ConvertMessageToBinary

2009-05-21 22:40:48 Success MP: Processing local module localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService

2009-05-21 22:46:48 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP

Time Stamp Status Description

2009-05-21 22:46:48 Error Exception caught by adapter framework: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP?targetClient=1 JMSReplyTo: null JMSRe

2009-05-21 22:46:48 Error Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP.

[Former Member]

Please check this notes whether they solve / match your problems:

Note 948016 - Websphere MQ reconnect issue for JMS receiver channel

Note 915410 - Problems with connection retry after JMS queue unavailabilit

[Former Member]

Hi - Thanks for replying. In the meantime, I was able to talk to someone who manages the queue manager on the MQ - it seems they had the TCP Keepalive setting set to false which was causing our issue.

Laura

[Former Member]

Hello Laura,

I wondered in your implementation if you are using a separate Queue (BDR.TO.SPKREDP) per message type?

Many thanks,

Aaron

[Former Member]

Hi Aaron,

No - we are actually using the same message queue for all transactions we are sending to MQ.

Thanks,

Laura

[Former Member]

Ok, would you mind taking a look at my forum question titled "Multiple Message Types into one Websphere Message Queue", it may be an easy one for you since you are already doing this!

Best regards,

Aaron

[|]

[Former Member]

Hi Aaron,

I replied to your thread - hope it makes some sense.

Laura