Hi All,
We have an issue with our interfaces in SAP PI (version 7.0, SP 19) which connect to Websphere MQ (version 5.3) using JMS adapter (having deployed JMS drivers version 5.3) to pick messages from its queues. We have only One Queue Manager(other connections with this Queue manager have no issues reported) and 4 queues from which our 4 PI interfaces pick messages from . These interfaces were running fine from past six months and suddenly it was observed that the Messages greater than 10KB are not being picked up from MQ. Messages with Size upto 5KB are received by SAP PI. Messages with size 7 KB are coming into PI with much delay (nearly 1-2 hrs) . No changes have been done at MQ and at PI configurations from past six months. Earlier we used to pick messages of size upto 4 MB from the MQ with no issues.
The only change could be the Kernel Upgrade in PI at that time before the issue just came up.
Observed Behaviour at PI :
Communication Channel shows no error logs. All Channels have status as successfully connected to Queues. Found server logs : u201Ccom.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2019u201D.
Observed Behaviour at MQ :
Messages from MQ disappear ( looks like being picked up) and queues have uncommitted status however after few minutes the messages appear again on the original queues, status changes back to committed.
We have done every check like :
Stopped the PI Channels and started, deleted queues on MQ and recreated, Restarted PI instance. u2013 No results.
We have applied the SAP note : 1086303 which talks about parameter with name 'activateExceptionListener'. But no results.
The MQException: MQJE001: Completion Code 2, Reason 2019 u2013 guides to IBM TechNote : http://www-01.ibm.com/support/docview.wss?uid=swg21229508. This was not implemented in MQ server as there was no such settings available on the server. ( We donu2019t have WAS for MQ).
Even the network team has confirmed its not a issue with Network/Firewall. (There are 2 Firewalls between PI and MQ servers. There was no change on the Firewall Rule as confirmed by the Network Team).
Please suggest if you have faced this kind of issue. We are facing this issue in Production environment. Hence any response will be much help.