Problems with PI 7.11 and IBM MQ Adapter (7.0)

[brian_arthern2]

Hi,

We are using the IBM MQ 7.0 classes to implement JMS connectivity from WebSphere to PI 7.11. We are experiencing a number od issues:

1. Two of the IBM classes seem to consume a lot of memory:

One instance of "com.ibm.mq.jmqi.remote.internal.system.RemoteConnectionPool" loaded by "library:com.sap.aii.adapter.lib" occupies 1,267,143,192 (37.25%) bytes. The memory is accumulated in one instance of "java.util.LinkedList$Entry" loaded by "<system class loader>".Keywords

library:com.sap.aii.adapter.lib

java.util.LinkedList$Entry

com.ibm.mq.jmqi.remote.internal.system.RemoteConnectionPool

166,095 instances of "com.ibm.msg.client.jms.internal.JmsQueueConnectionImpl", loaded by "library:com.sap.aii.adapter.lib" occupy 1,153,324,768 (33.91%) bytes. These instances are referenced from one instance of "java.util.HashMap$Entry[]", loaded by "<system class loader>"

2. On occasion, when we attempt to manually stop/start channels threads hang up waiting for locks. The stacktrace we have located seems again to relate to the IBM classes:

Thread 'System [26]', process 'server0', index '70'

"System [26]" Id=130 IN_WAIT_WITHOUT_TIMEOUT

cpu=10230.6 ms (system=431.44 / user=9799.15) allocated=571941136 B

user="PIDIRUSER" sessionId="1194218205" requestId="21622"

application="sap.com/com.sap.aii.af.cpa.app"

Thread is in wait() operation without a timeout: waiting on object monitor java.lang.Object (addr=0x0000000128d442e0)

at java.lang.Object.wait(J)V(Native Method)

at java.lang.Object.wait()V(Object.java:474)

at com.ibm.mq.jmqi.remote.internal.RemoteHconn.requestDispatchLock(I)Z(RemoteHconn.java:423)

at com.ibm.mq.jmqi.remote.internal.RemoteFAP.MQCTL(Lcom.ibm.mq.jmqi.handles.Hconn;ILcom.ibm.mq.jmqi.MQCTLO;Lcom.ibm.mq.jmqi.handles.Pint;Lcom.ibm.mq.jmqi.handles.Pint;)V(RemoteFAP.java:1750)

at com.ibm.msg.client.wmq.internal.WMQConsumerOwnerShadow.controlAsyncService()V(WMQConsumerOwnerShadow.java:293)

at com.ibm.msg.client.wmq.internal.WMQConsumerOwnerShadow.stop()V(WMQConsumerOwnerShadow.java:629)

at com.ibm.msg.client.wmq.internal.WMQSession.stop()V(WMQSession.java:1270)

at com.ibm.msg.client.jms.internal.JmsSessionImpl.stop(Z)V(JmsSessionImpl.java:1991)

at com.ibm.msg.client.jms.internal.JmsSessionImpl.stop()V(JmsSessionImpl.java:1897)

at com.ibm.msg.client.jms.internal.JmsConnectionImpl.stop()V(JmsConnectionImpl.java:774)

at com.ibm.mq.jms.MQConnection.stop()V(MQConnection.java:477)

at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.stop()V(ConnectorImpl.java:686)

at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.closeResources()V(ConnectorImpl.java:710)

at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doDisconnect()V(ConnectorImpl.java:480)

at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.disconnect()V(ConnectorImpl.java:460)

Has anyone experienced similar problems? Does anyone have suggested solutions (we are still waiting on SAP for help)?

many thanks

Brian

[Former Member]

HI

We had the similar issue and re-deploying the com.sap.aii.adapter.lib.sda solved the issue.

Thanks

Kiran Nekkanti

[Former Member]

We have been experiencing similar problems and are now finding that the messages are not being stripped of MQ from time to time and we have to stop/start the comm channels.