System Error in RWB JMS Exception

[Former Member]

Hello,

We have an unsolved issue, Where..

Scenario :

(IDoc) R3 system (proxy) - PI system - JMS (MQ) - Printer system..

The Idocs are processed successfully in R3 and in ABAP Stack  (sxi_monitor) of PI, BUt gets an error in RWB component of PI with the following error on connection to JMS.. 

Error in RWB :

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: FormScapeMQon node: 3158151 having object id: 276d0e3d1a633dd8b5de9c88c0651f9f encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///SAP.FI.OUTPUT.TO.FORMSCAPE.PROD?targetClient=1, the message message: JMS Message class: jms_text  JMSType:         null JMSDeliveryMode: 1  JMSExpiration:   0  JMSPriority: 4  JMSMessageID:    null  JMSTimestamp: 1339539625758 JMSCorrelationID:005056a9-39b1-1ed1-ad9b-6b19c2385fbd  JMSDestination: queue:///SAP.FI.OUTPUT.TO.FORMSCAPE.PROD?targetClient=1  JMSReplyTo: null  JMSRedelivered:  false JMSXDeliveryCount:0 <?xml version="1.0" encoding="UTF-8"?> <OMA3><FS_HEADER><MASSEPRINT_ID>00000000000000006119</MASSEPR Another 32.089 character(s) omitted: javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue.

Facts  :

Seems PI is right as there is no mapping error.

JMS was not down

As there are a lot of successful messages with respect to this scenario and on the same time of other error messages.

So question -  When consulted with MQ team they said there is no issue. But issue points to JMS exception.. Is there anything we should find in PI or is the error elsewhere ??  Can light be shed upon this error ?? I have gone through posts and discussions but didn't come across such error.

[Former Member]

Hi Rajesh,

Ensure , if all parameters are maintained same at both your ends . Try to restart the channel once . Also do a delta refresh

Ask your MQ team to perform testing at their end as well

1. Verify MQ mparameters

2. confirm if listener is running, Trigger is running

3. Perform PING test

Also there can be possiblity of some defunct processes due to hung MQ listener process with the QMgr

There are several possible reasons for the messages not being delivered.                  

1. The other agents involved in the transfer are not running.          

2. The WebSphere MQ channels have not been configured for the other    

agents to be able to send the messages back to the command queue       

3. The other agents have had the messages removed from their           

SYSTEM.FTE.STATE.<agentName> queue so they are no longer aware of the  

transfers.                                                             

4. The SYSTEM.FTE.COMMAND.<agentName> has had all of its messages      

deleted from it. Note that the SYSTEM.FTE.COMMAND.<agentName> queue is 

used for new transfer request messages and for internal control messages

that are sent between agents.

Pls check, if any is applicable in your case

Thanks,

     Suji

[Former Member]

HI,

They upgraded their MQ. And the error has stopped.
We simply restarted the communication channel and sent it all again.

Thanks & Regards,

Rajesh.S

Solved

[former_member182412]

Hi Rajesh,

What is the size of the payload which you try to send it to JMS Queue, there is a max payload parameter in JMS MQ side if you send more than that parameter PI cant able to send the message to JMS MQ, please check with your MQ team what is the current parameter set it to.

Praveen.

[Former Member]

Hi Praveen,

I have checked with them and found further information about error when trying to resend...

MP: exception caught with cause com.sap.aii.adapter.jms.api.connector.ConnectorException: Connector for ConnectionProfile of channel: FormScapeMQon node: 3158151 having object id: 276d0e3d1a633dd8b5de9c88c0651f9f encountered error: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException: while trying to read the field 'ccsid' of an object loaded from field com.ibm.mq.MQSESSIONClient.comms of an object loaded from local variable '<0>' in sending to destination queue:///SAP.FI.OUTPUT.TO.FORMSCAPE.PROD?targetClient=1, the message message: JMS Message class: jms_text  JMSType:         null JMSDeliveryMode: 2  JMSExpiration:   0  JMSPriority: 4  JMSMessageID:    null  JMSTimestamp: 0  JMSCorrelationID:005056a9-2f03-1ee1-ad9b-6a44231b6356 JMSDestination:  null  JMSReplyTo:      null JMSRedelivered:  false <?xml version="1.0" encoding="UTF-8"?> <OMA3><FS_HEADER><MASSEPRINT_ID>00000000000000006119</MASSEPR Another 49.883 character(s) omitted: javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException: while trying to read the field 'ccsid' of an object loaded from field com.ibm.mq.MQSESSIONClient.comms of an object loaded from local variable '<0>'

Have questioned MQ team with the details of this.

Thank you for ur reply, The other successful messages had payload bigger than this one throwing error. And there are lots of such errors for many users !