Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Problem with Adapter Engine

Hello,

I have problem with adapter engine. I had a few scenarios (Mail-To-File, File-To-File, SOAP-To-File) and they was working fine. But once after refreshing of XI cache it stoped. Now when I send some message to XI, it doesn't reach of Integration Engine. I can see the messages in RWB but they are in status "Waiting" and after a few attempts they change status to "System Error". In SXMB_MONI they are not displayed.

This is audit log of one of the messages:

2008-09-03 09:03:47 Success Mail: calling the module processor for channel MailReceivingChannel

2008-09-03 09:03:47 Success MP: entering

2008-09-03 09:03:47 Success MP: processing local module localejbs/sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean

2008-09-03 09:03:47 Success Mail: message leaving the adapter (send)

2008-09-03 09:03:47 Success Application attempting to send an XI message asynchronously using connection AFW.

2008-09-03 09:03:47 Success Trying to put the message into the send queue.

2008-09-03 09:03:48 Success Message successfully put into the queue.

2008-09-03 09:03:48 Success The application sent the message asynchronously using connection AFW. Returning to application.

2008-09-03 09:03:48 Success The message was successfully retrieved from the send queue.

2008-09-03 09:03:48 Success The message status set to DLNG.

In defaultTrace file I found following :

#1.5#00301875333B00570000002600001410000455F8822D0EF4#1220425731046#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage, boolean)#J2EE_GUEST#0####8db634d0798611ddcf0c00301875333b#SAPEngine_Application_Thread[impl:3]_28##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during conversion of XI message#http://srvbr05:8000/sap/xi/engine?type=entry#+ +#1.5#00301875333B00600000003A00001410000455F89410C82A#1220426031171#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage, boolean)#J2EE_GUEST#0####dc134860798711dd9ac200301875333b#SAPEngine_Application_Thread[impl:3]_2##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during conversion of XI message#http://srvbr05:8000/sap/xi/engine?type=entry#+ +#1.5#00301875333B005F0000003C00001410000455F8A5F47E02#1220426331281#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage, boolean)#J2EE_GUEST#0##srvbr05_NW4_2798750#XIAFUSER#7ba54f00798711ddc63800301875333b#SAPEngine_Application_Thread[impl:3]_11##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during conversion of XI message#http://srvbr05:8000/sap/xi/engine?type=entry#+ +#1.5#00301875333B005F0000003D00001410000455F8A5F480EC#1220426331281#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage, boolean)#J2EE_GUEST#0##srvbr05_NW4_2798750#XIAFUSER#7ba54f00798711ddc63800301875333b#SAPEngine_Application_Thread[impl:3]_11##0#0#Error##Java###Failed to transmit message due to .#2#73ba4a30-7986-11dd-a7bd-00301875333b(OUTBOUND)#com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during conversion of XI message#

#1.5#00301875333B005F0000003E00001410000455F8A5F62C0E#1220426331390#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage, boolean)#J2EE_GUEST#0##srvbr05_NW4_2798750#XIAFUSER#7ba54f00798711ddc63800301875333b#SAPEngine_Application_Thread[impl:3]_11##0#0#Error##Java###Retries exceded, set message to status NON_DELIVERED.#1#73ba4a30-7986-11dd-a7bd-00301875333b(OUTBOUND)#+ #1.5#00301875333B00030000000200001410000455F9B21A1953#1220430829953#com.sap.engine.services.deploy##com.sap.engine.services.deploy######086d7f11799311dda81b00301875333b#SAPEngine_System_Thread[impl:5]_37##0#0#Error#1#/System/Server#Plain### Operation startApp over application sap.com/com.sap.aii.af.cpa.app finished with errors on server 2798750. For more detailed information see traces of Deploy Service.# #1.5#00301875333B00030000003500001410000455F9B2EA07CE#1220430843578#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.traceSample()######086d7f11799311dda81b00301875333b#SAPEngine_System_Thread[impl:5]_37##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework#Plain###Ignore this and the following trace messages in the method traceSample(). It is just a sample for using the trace API!# #1.5#00301875333B00030000003700001410000455F9B2EA0B3B#1220430843578#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.traceSample()######086d7f11799311dda81b00301875333b#SAPEngine_System_Thread[impl:5]_37##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework#Plain###A error trace message with signature, category and text# +#1.5#00301875333B00030000003900001410000455F9B2EA0D4E#1220430843578#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.traceSample()######086d7f11799311dda81b00301875333b#SAPEngine_System_Thread[impl:5]_37##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework#Java###A error trace message with signature, category, text and .#1#parameters#

#1.5#00301875333B00030000003B00001410000455F9B2EA0EF5#1220430843578#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.traceSample()######086d7f11799311dda81b00301875333b#SAPEngine_System_Thread[impl:5]_37##0#0#Error##Plain###A error trace message with signature and text only#

#1.5#00301875333B00030000003C00001410000455F9B2EA0FAA#1220430843578#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.traceSample()######086d7f11799311dda81b00301875333b#SAPEngine_System_Thread[impl:5]_37##0#0#Error##Java###A error trace message with signature, text and #1#parameters#+ +#1.5#00301875333B00030000003D00001410000455F9B2EA1256#1220430843578#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.traceSample()######086d7f11799311dda81b00301875333b#SAPEngine_System_Thread[impl:5]_37##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework#Java###Assertion failed: #1#Logging severity level is not set to 'None'#

Moreover when I check SLD -> Administration -> Content Maintenance -> XI Adapter Engine there is not any adapter engine. Is it normal?

I think there is some problem with adapter engine but I don't know where and how to find out that. Could someone help me a give me some advice? Thank you in advance!

Best regards

Zbynek

Former Member

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question