Skip to Content

SAP ME 5.2 - Production XML complete response message got exception

Hello,

Last week, we had a production outage for our ME 5.2 system. We did a restart of the NetWeaver cluster services, afterwards our production reported the strange behavior. Randomly, the completeSfc SFC from production XML function received the exception like "javax.transaction.xa.XAException: XA operation cannot be completed successfully", but not for all SFCs, only ramdonly happened. We checked the SFC in the system and actually it was completed successfully, just the response message got crashed, therefore our machine cannot handle this response properly. The solution to solve this was having another completely restart of the NetWeaver cluster.

Here are more errors from the NetWeaver log side. Anyone has an idea what could be the root cause of this kind of error?

JMS: JMSClient: Sending the following message content to the destination "rawAlarmQueue":

ALARM_ID[java.math.BigDecimal]=4708

CREATE_DATE[com.visiprise.globalization.impl.IcuDateTime]=2016-04-06T11:59:11.092Z

MESSAGE_HEADER[java.lang.String]=PRODUCTION_XML_ERROR (600)

MESSAGE_TEXT[java.lang.String]=Internal error: "javax.transaction.xa.XAException: XA operation cannot be completed successfully." (Message 1007)

XML=<?xml version="1.0"?><PRODUCTION_REQUEST xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <COMPLETE> <SFC_LIST> <SFC> <SITE>0786</SIT

  1. skipped...

ALARM_TYPE[java.lang.String]=PRODUCTION_XML_ERROR

NOTIFICATION_TYPE[java.lang.String]=ALARMNOTIFICATION

#2.0^H#2016 04 06 17:29:11:044#+0530#Error#com.sap.jms.client#

#BC-JAS-JMS#jms#005056BA1E9A02620000008900000AD8#7343350000000004#sap.com/me~ear#com.sap.jms.client.xa.XAResource#Guest#0#SAP J2EE Engine JTA Transaction : [070cfffffff600ffffffc925]#07AC89C9FBEE11E59B46000000700CF6#07ac89c9fbee11e59b46000000700cf6#07ac89c9fbee11e59b46000000700cf6#0#Thread[HTTP Worker [@1532606499],5,Dedicated_Application_Thread]#Plain##

  1. javax.jms.IllegalStateException: The Session is closed. id: 342

at com.sap.jms.client.session.JMSSession.checkClosed(JMSSession.java:901)

at com.sap.jms.client.session.JMSSession.commit(JMSSession.java:234)

at com.sap.jms.client.xa.SessionAdapter.commit(SessionAdapter.java:60)

at com.sap.jms.client.xa.XASession.xaCommit(XASession.java:84)

at com.sap.jms.client.xa.XAResource.commit(XAResource.java:43)

at com.sap.engine.services.jmsconnector.spi.ManagedSession$XAManagedResource.commit(ManagedSession.java:576)


Thanks & regards,

Leon

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Apr 11, 2016 at 07:46 AM

    Hi Leon,

    I guess "a restart of NetWeaver cluster services" is something different than "a complete restart of NetWeaver cluster". Then such errors are quite expected. It is possible that the system failed to send a successful response for SFC Complete due to XA issue that in turn tirggered alarm via JMS. Due to the same XA issue, the system failed to roll back the transaction - thus you see the SFC eventually completed successfully.

    Regards,

    Sergiy

    Add comment
    10|10000 characters needed characters exceeded