MQ error: MQJMS2007

[Former Member]

Team,

We just upgrade from PI 7.0 SP11 to SP12 and all our MQ screnario are not fonctionning anymore ... we are getting the MQJMS2007 error (see below)

Any hints will be appreciated !!

A+

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: CC_JMS_out_ExtractofClaimtogetMileageon node: 239676450 having object id: 6653bdc9e77730a3b1eced808d94e7fd encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///SAP_XI1.BATCH.COSTMILE_APRT_INB?CCSID=500&targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 1183471233046 JMSCorrelationID:4688c1c3-c823-0361-e100-0000a57.

[Former Member]

Michel,

If the size of the message exceeds the message size mentioned in MQ then you get this MQJMS2007 error.

There is parameter called Maximum Message Length in the MQ. This has to be increased.

Example: If you are expecting a message of 10000 KB then increase this paramter value to 10000 KB.

<b>Regards,

Sridhar</b>

[Former Member]

Hi Sridhar,

Is this parameter on the MQ side or on the JMS (MQ) adapter side ?

What is weird, is everything was functionning perfectly up to the time we decide to go with SP12 ...

A+

[Former Member]

.

[Former Member]

Any Luck on this one..we are currently facing similar kind of error:

MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: CC_R_JMS_MATRICSToECC114_ACKon node: 203681450 having object id: ac4f4f5b61793872a403ec3ad546e979 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///TQ1E.KFCAT.DEV.ASAPTOMATMM.REMOTE?targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 1188331798094 JMSCorrelationID:46d4af9f-6f63-1ef4-e100-00000a3597fc JMSDestin.

Any thoughts would be greatly appreciated.

Regards,

Srujanks

[Former Member]

Hi Srujanks,

The MQJMS2007 error is a generic one and, thus it could lead to many sources, The research and the finding we made when we got the error was:

1) The queue is set to not persistent (mode) and in your Com Channel you try to persist

2) The length of the payload might exceed the length available on that queue

3) If you are dealing with French (or Asian or Spanish, etc) base character, the queue might not has been set to accept such multi bytes stream. (é, è, etc.)

None of theses situations was our case.

We find out that our queue has been define for

none persisting

and our communication channel was

also define to be not persistent

. But for some reason the JMS Adapter under SP12 was forcing the persisting mode

We have been asked by SAP Support to look at the OS note 873861 but it did not help us very much.

Finally, SAP has release a fix for that and if you open an SAP support ticket, I believe you will get it. This fix will be in the next SP

Hope it help !

A+

[Former Member]

Thanks a lot, Michel. I will be proceeding with your suggestion and find out what our team wants to do to resolve this issue.

Regards,

Srujan

[Former Member]

Did you get a solution to this? I'm experiencing the same problem.

[Former Member]

Hi Dave,

As stated to my earlier message to Srujan, it is an SAP bug with the SP12 version under PI 7.0.

We got a fix from SAP and it has resolved the issues.

Good luck / Michel

[Former Member]

Hi,

I having the problem as you had.

My problem lies with using remote queue. Please check my thread.

@Michel: can you provide the SAPnote that SAP provide you as a fix for your problem?

Appreciate to know how the fix will work.

[Former Member]

Michel,

The parameter is on MQ Side.

It will be in present in MQ Channel and MQ Queue. Change the value of the parameter on both channel and queue to the required size.

In MQ Explorer under Queue Manager you can see Queues and under Queue Manager --> Advanced --> you can see Channels

1) In MQ Explorer under Queue Manager you can see Queues. Go to properties of MQ Queues --> Extended , here you will find parameter "Max message length". Change the parameter on both channel and queue to the size required.

2) In MQ Explorer under Queue Manager --> Advanced --> you can see Channels.

Go to Properties of MQ Channels --> Extended, here you will find parameter "Max message length". Change the parameter on both channel and queue to the size required.

Till the message size is less that what has been mentioned in the parameter "Maximum Message Length" there is will no error. Once the message size crosses the size mentioned in the Channel and Queue then you get this error.

Regards,

Sridhar

[Former Member]

Hi Sridhar ,

Thank for your response, I'll be back at my client site, tomoroow and i'll check all that and let you know the outcome !

Merci ! A+

[Former Member]

Hi Sridhar,

It seems that it is a bug related with the adaptor framework under PI 7.0 SP12.

We have opened an SAP support msg and SAP had (last friday) a quick look at it and said the adaptor framework under SP12 might have a bug ... let see

[Former Member]

Hi ,

Problem Details : Error Receiver JMS Channel : MQJMS2007

SAP PI Version : 7.1 EHP1

IBM MQ Series Version : 6.0

Scenario: IDOC > PI7.11> JMS (IBM MQ6.0)

Error Details in Audit log (Runtime Work Bench):

MP: exception caught with cause com.sap.aii.adapter.jms.api.connector.ConnectorException: Connector for ConnectionProfile of channel: CC_JMS_IN_APLon node: 8568850 having object id: 1822616df514394186dbf3ba348d8558 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///APLL.MTS.NETWEVPI_DELIVERY_IDOC.PUT?CCSID=819&targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 1320796791633 JMSCorrelationID:4eb95ee5-5918-1110-e100-800034634752 JMSDestination: queue:///APLL.MTS.XXXXX_NETWEVPI_DELIVERY_IDOC.PUT?CCSID=819&targetClient=1 JMSReplyTo: null JMSRedelivered: false JMSXDeliveryCount:0 EDI_DC40 510000000013776275346C 3012 DELVRY03 ZDELVRY3 D Another 90,865 character(s) omitted: javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue

Adapter Framework caught exception: Connector for ConnectionProfile of channel: CC_JMS_IN_APLon node: 8568850 having object id: 1822616df514394186dbf3ba348d8558 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///APLL.MTS.XXXX_NETWEVPI_DELIVERY_IDOC.PUT?CCSID=819&targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 1320796791633 JMSCorrelationID:4eb95ee5-5918-1110-e100-800034634752 JMSDestination: queue:///APLL.MTS.DUPONT_NETWEVPI_DELIVERY_IDOC.PUT?CCSID=819&targetClient=1 JMSReplyTo: null JMSRedelivered: false JMSXDeliveryCount:0 EDI_DC40 510000000013776275346C 3012 DELVRY03 ZDELVRY3 D Another 90,865 character(s) omitted: javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue

Delivering the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.jms.api.connector.ConnectorException: Connector for ConnectionProfile of channel: CC_JMS_IN_APLon node: 8568850 having object id: 1822616df514394186dbf3ba348d8558 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///APLL.MTS.XXXXX_NETWEVPI_DELIVERY_IDOC.PUT?CCSID=819&targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 1320796791633 JMSCorrelationID:4eb95ee5-5918-1110-e100-800034634752 JMSDestination: queue:///APLL.MTS.DUPONT_NETWEVPI_DELIVERY_IDOC.PUT?CCSID=819&targetClient=1 JMSReplyTo: null JMSRedelivered: false JMSXDeliveryCount:0 EDI_DC40 510000000013776275346C 3012 DELVRY03 ZDELVRY3 D Another 90,865 character(s) omitted: javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue.

Regarding this error, we found some notes in https://websmp110.sap-ag.de/notes.

Notes : sapnote_0001450509 and sapnote_0000873861.

Can you please confirm that these SAP notes are also applicable for MQ Series Version 6.0 ?

[Former Member]

I guess it should work once you restart the adapter engine or deactivate and activate each communication channel individually

Rgds,

Ravi

[Former Member]

We tried it (deactivating and reactivating ) the communication channel and we are still getting the error ... We are thinking of going back to SP11.

Let me know if you have any ideas !

Thanks