cancel
Showing results for 
Search instead for 
Did you mean: 

MQ - Problems with receiver adapter

Former Member
0 Kudos

Hello experts,

has anybody experience with this kind of MQ error:

Message-Verarbeitung fehlgeschlagen. Grund: com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: jms_rcv_aleg on node: 517708350 having object id: 336a5d371e443540b9cf6fcdb922228a encountered error: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195 MQJE046: Unsupported codeset : 0 in sending to destination queue:///somevalue targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 0 JMSCorrelationID:08c08110-6001-1091-0804-a2873c90c93c JMSDestination: null JMSReplyTo: null JMSRedelivered: false <?xml version="1.0" encoding="UTF-8"?> <ns1:aleg_auftrag_webkarat_rc xmlns:ns1="http://somevalue.de/ka Another 101 character(s) omitted: javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195 MQJE046: Unsupported codeset : 0

Some additional background information: The MQ system is restarted once a day at midnight. The first message after restart always fails. To solve this I configured the receiver channel with the follwing parameters:

Wait After Message Error (msecs): 900000

Wait Before Reconnect (msecs): 600000

Reconnect if Exception Text Starts with: MQJMS2007

Handling of Pending XI Messages: Bypass Pending Warning and Send Message to JMS (Duplicates Possible)

The SAP note 948016 says something about the JMS-Parameter CONNECTION_TEST_POLL=true. After configuration I received an error, that the adapter is not able to create a temporary queue.

Thanks for all help on this topic

Frank

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Kumar,

the provided links did not help. Furthermore the IBM ones point to reason code 2059, but mine is 2195.

Frank

Former Member
0 Kudos

Hi Frank,

We are experiencing same MQ error on our PI production system.

Were you able to resolve the issue?

Thanks

Ravi Mallepalli

Former Member
0 Kudos

Please refer to-

former_member556603
Active Contributor
0 Kudos