XI_J2EE_ADAPTER_XI_HANDLER

Hello experts,
We are facing a critical problem .
We are getting the following error in IFR.
Message Data
Attribute Value
Engine Adapter Engine
Status System Error
Repeatable Yes
Cancelable Yes
Start 17.01.2008 17:11:50
End 17.01.2008 22:11:29
Sender Party
Sender Service BS_OSX
Sender Interface urn:sap-com:document:sap:rfc:functions
CONTROL_RECIPE_DOWNLOAD
Receiver Party
Receiver Service
Receiver Interface
Quality of Service Exactly Once
Error Category XI_J2EE_ADAPTER_XI_HANDLER
Error Code GENERAL_ERROR
Message 2870CC28B18314610720F1C004D00808
I have checked all setting in SLD,smicm,sxmb_adm,communication channels are working fine, SLD cache has been refreshed, Business system has Integration server attached to it.
But still i am not able to rectify the problem.
Please suggest something . How to rectify this problem
This is very urgent .
Regards
SAras Jain

RFC adapter received tRFC for CONTROL_RECIPE_DOWNLOAD with TID A0473CAB6356478FB7A2088D from OSX/070. Attempting to send message asynchronously
2008-01-17 22:17:00 Success Application attempting to send an XI message asynchronously using connection AFW.
2008-01-17 22:17:00 Success Trying to put the message into the send queue.
2008-01-17 22:17:00 Success Message successfully put into the queue.
2008-01-17 22:17:00 Success The application sent the message asynchronously using connection AFW. Returning to application.
2008-01-17 22:17:00 Success The message was successfully retrieved from the send queue.
2008-01-17 22:17:00 Success The message status set to DLNG.
2008-01-17 22:17:00 Error Received XI System Error. ErrorCode: SYSTEM_NOT_CONFIGURED_AS_XMB ErrorText: ErrorStack: System not configured as XI Integration Engine
2008-01-17 22:17:00 Error Transmitting the message to endpoint http://orxidd01:8002/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SYSTEM_NOT_CONFIGURED_AS_XMB:.
2008-01-17 22:17:00 Success The asynchronous message was successfully scheduled to be delivered at Thu Jan 17 22:22:00 EET 2008

Similar Messages

Error on file adapter (GENERAL_ERROR on XI_J2EE_ADAPTER_XI_HANDLER )

Hi Experts,
I have just configured a sender file adapter with content conversion in a PI 7.0. I will try to explain the problem:
1. I put the text file on the selected folder, to be taken.
2. The file is taken from the folder and archived in the archive folder.
Until here everything works fine, but from here:
- I can't watch the message in the sxmb_moni
- I can watch the message in the message monitoring in the Runtime Workbench. Here I can even see the XML well formed(the text file have been processed correctly)
The error log:
Message Data
Attribute Value
Engine Adapter Engine
{Status System Error
Repeatable Yes
Cancelable Yes
Error Category XI_J2EE_ADAPTER_XI_HANDLER
Error Code GENERAL_ERROR
Does anybody know where will be the error?
Regards
Gonzalo

Hi,
please check the following links related to your error category.
File (xml)>>xi>>IDoc
Problem in JDBC Reciver Channel
Problem in Webservice -> XI -JDBC
regards
mahesh.

Error Category      XI_J2EE_ADAPTER_XI_HANDLER

Hi
A couple of days we had problem in our Xi production server & we were unable to login into the server.
During that time the messages which got picked up from FTP went into Adapter Engine System Error.
Our Scenario is File to Idoc.
When I try to resend those messages through RWB its giving through PIAFUSER its givig wrong user id or password. Although the user id & pwd is correct.
Message Data
Attribute     Value
Status             System Error
Repeatable     Yes
Cancelable     Yes
Error Category      XI_J2EE_ADAPTER_XI_HANDLER
Error Code     GENERAL_ERROR
Start     12.08.2011 02:35:50
End     12.08.2011 07:08:59
Sender Party
Sender Service     CLMS
Receiver Party
Receiver Service
Interface     http://srl.in/clm_outbound
SRL_MI_CLM_SALES
Quality of Service     Exactly Once
Message     cf1c6b31-b3ed-45cb-08da-ebcbc1de3906
Reference
Conversation ID
Version     0
Edited     No
Serialization Context
Direction     OUTBOUND
Message Type     Send
Profile     XI
Connection     File_http://sap.com/xi/XI/System
Transport     HTTP
End Point     http://srlxiprd:8000/sap/xi/engine?type=entry
Authorization     SAPPasswordCredential(PIAFUSER):password=********:sapclient=900:saplang=
Sequential Number     0
Number of Retries     3
Failed     4
Retries     300000
Valid to
Persist Until     11.09.2011 02:35:50
Schedule Time     12.08.2011 06:22:55
Please give your valuable suggestion as I have lots of messages in system error.
Thanks

User XIAFUSER/PIAFUSER could have been locked.
Check the exchange profile and transaction SU01; try to reset the password.
Restart the Java Engine to activate changes in the exchange profile.
Regards
Pothana

Soap Adapter - XI_J2EE_ADAPTER_XI_HANDLER Error

Hello,
we have a very informative error here for
SOAP outbound adapter:
Sending to the SOAP-Adapter address ..../SOAP_Adapter/MessageServlet.... with the test tool in RWB we have this error:
Error category: XI_J2EE_ADAPTER_XI_HANDLER
Error code: GENERAL_ERROR
No entries in SXMB_MONI (of course!)
No idea, what has gone wrong!
Scenario is completed in ID!
What could be possible problems related to this fantastic error message?
We are on SP17,
Comm.channel monitoring shows no errors! (green light)
Best regards
Dirk

Hi Dirk,
can u see any messges in Message monitor on the RWB.
If yes, can u check the audit log and see what the problem is?
Regards
Sunita

XI_J2EE_ADAPTER_XI_HANDLER Error

Hi Experts,
I have done file to idoc scenario and file to file scenario.
after activating the objects in integ.directory , i couldnt see the processed msgs in sxmb_moni for both scenario.
In RWB comoponent monitoring when i see communication channel monitor it shows only outbound msgs but both comm.channel functioning properly.even i could see the msgs in mesage monitoring(except outbound msgs). the outbound log shows the msg executed succesfully waiting in que. after some times it shows status: system error, error category:XI_J2EE_ADAPTER_XI_HANDLER , error code:SEND_CONSUMER_ERROR. I think the mesages not going in to integ.engine.
                i thought it might be a cache problem .So I execute the Tcode SXI_CACHE it shows following error 1,Unable to Refresh Cache Contents 2, Error During Last Attempt to Refresh Cache. i double click the above error it shows following details.
                                           Incorrect XML display for AlertCategory
                                            Error during deserialization
                                             Data loss occurred when converting 011136c23c9430359b57c0ef8949c630
     Can you give me the solution
Thanks
Raja Mohamed

Hi,
Check these threads...
Re: File is picked up but never show the XML message in SXMB_MONI
SYSTEM_NOT_CONFIGURED_AS_XMB
CCM2.0 Config in NW2004s (PI7.0) u0096 XI Error
Regds,
Pinangshuk.

XI_J2EE_ADAPTER_XI_HANDLER - GENERAL_ERROR

Hi,
Scenario: RFC adapter to File adapter.
I am getting the following error:
Message Data
Attribute Value
Engine Adapter Engine
Status Waiting
Repeatable Yes
Cancelable Yes
Start 15.05.2007 19:57:18
End 15.05.2007 19:57:18
Sender Party
Sender Service CD1
Sender Interface urn:sap-com:document:sap:rfc:functions
ZXI_TEST
Receiver Party
Receiver Service
Receiver Interface
Quality of Service Exactly Once
Error Category XI_J2EE_ADAPTER_XI_HANDLER
Error Code GENERAL_ERROR
Message 0092C60810453891061093C41CD2CD1C
Reference
Can anyone help?
Thanks,
Leanne

Hi,
I have found error is the message, please help:
2007-05-15 20:07:18 Success The asynchronous message was successfully scheduled to be delivered at Tue May 15 20:12:18 SAST 2007.
2007-05-15 20:07:18 Success The message status set to WAIT.
2007-05-15 20:12:18 Success Retrying to send message. Retry: 3
2007-05-15 20:12:18 Success The message was successfully retrieved from the send queue.
2007-05-15 20:12:18 Success The message status set to DLNG.
2007-05-15 20:12:18 Error Received XI System Error. ErrorCode: SYSTEM_NOT_CONFIGURED_AS_XMB ErrorText:   ErrorStack: System not configured as XI Integration Engine
2007-05-15 20:12:18 Error Transmitting the message to endpoint http://jssxid0:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SYSTEM_NOT_CONFIGURED_AS_XMB:.
Thanks,
Leanne

Receiver Communication channel was not showning in C C Monitoring

Hi,
I am Doing File-to Idoc/Idoc-toFile Scenario. it is shwong these errors plz help meout
In MSG DATA
Error Category XI_J2EE_ADAPTER_XI_HANDLER
Error Code GENERAL_ERROR
In Audit Log
Transmitting the message to endpoint http://apollo:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 401 : Unauthorized.
reg,
suresh

Dear Suresh,
It appears be an authorization issue. Check the credentials given.
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Possible Tips:
Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
If the error is in Adapter Engine
then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
May be wrong password for user XIISUSER
May be wrong password for user XIAFUSER
for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message
Regards,
Naveen.

Communication chaneel error

Hi Experts,
My scenario is FileRFCFile Syncrinous. All the files being picked up from output tray by the Sender file CC.
and because of one error file suddenly Sender File CC is not picking remaining all the files in the tray. even after deleting the error file and after stopping and starting the Sender File CC, the new files came in the tray are not getting picked up.
kindly advice me how to resolve the issue.
Thanks,
Siva

Hi Abhijit,
Thanks for your reply,
The Error in auditlog is as ErrorCode: MESSAGE_NOT_FOUND
and Error Category : XI_J2EE_ADAPTER_XI_HANDLER
and Error code : CALL_CONSUMER_ERROR
Earlier somany times i got the same issue and by deleting the error file and restarting the Sender file CC by start and stop, the files has been picked up. But now the file adapter not picking the new files and it is persisting the old messsage id only which was for the error file.
Thanlks,
Siva

Problem in JDBC Reciver Channel

Hi Experts,
 My scenario is , transfer records from one table to another table in MS SQL Server.For that I have created a JDBC to JDBC Scenario. I am using same Business System for both Sender and Reciver Communication Channels. I have created two tables in SQL Server with same fields and mapped in message mapping accrodingly.
 I have written a SQL Queries in Sender as
 SELECT ..... SELECT * FROM EXAMPLE WHERE FLAG<>'0'
 UPDATE..... UPDATE EXAMPLE SET FLAG='0' WHERE FLAG<>'0'
 When i insert the records in EXAMPLE(source) table the flag field values are updated to '0'.
 But these records are not inserted into Destination table.
I have checked the result in Communication channel monitoring .. the result displayed for Sender Communication channel showing as "PROCESSED SUCCESSFULLY"
but where as in Reciver Communication Channel it is still showing as "FUNCTIONING"
What might be the problem...
Please help me in sloving this issue..
Thanks in Advance,
Murthy.

Hi Bhavesh,
 I can not provide XML Source for JDBC adapter as I can not get any message when i checked in SXMB_MONI.
 As you told me, I looked into Message Monitoring in RWB for messages in Integration Server and Adapter Engine.
 I could found the Messages for Sender Interface in Integratio severa, and it's status as System
Error. Here is the complete info.
Attribute Value
Engine Adapter Engine
Status System Error
Repeatable Yes
Cancelable Yes
Start 16.05.2007 12:09:14
End 16.05.2007 12:24:14
Sender Party
Sender Service WORK_DEMOAR_BS
Sender Interface http://prospecta.com.au/DemoAr/JDBC2JDBC
SENDER_MI
Receiver Party
Receiver Service
Receiver Interface
Quality of Service Exactly Once
Error Category XI_J2EE_ADAPTER_XI_HANDLER
Error Code GENERAL_ERROR
Message 297BF2A0037811DCB75B0015170C6BA8
Reference
But i could not found any messages for Reciver interface in Integratio Server.
Also i could not found any messages for Adapter Engine for both Sender and Reciver.
Thanks,
Murthy.

Isssue in File To RFC Scenerio

Hi Experts,
   I am sending a .DAT file to R/3 using PI.
   File gets successfully picked up from FTP into PI. But sxmb_moni is not showing any error messeges, nothing. In fact I know this is a perfectly OK file as few days ago it was successfully processing the same file, without errorrs.
I hav checked in messege monitering and got the following error.
Error Category XI_J2EE_ADAPTER_XI_HANDLER
Error Code GENERAL_ERROR
Received XI system error.error Code:SLD_NO_OWN_BS Error Text:Error Stack:error while reading ID of own business system from the SLd for system RXT and client 001 Internal error in Landscape Directory.
I hav checked the LOG in SLD and got the fllowing error.
#1470 03/10/2009 15:00:49.918 [SAPEngine_Application_Thread[impl:3]_18] WARNING com.sap.lcr.cimsrv.ChangePasswordServlet: Password change required for automated client. Please ensure that service client users don't have initial passwords. Alternatively, logon to the SLD user interface with the corresponding user and assign a new password. After the password has been changed, client settings must be updated accordingly.
I hav done no changes in any where,, no password change or no craetion of new client. This scenerio was working ok, but all of a sudden it started giving this strage issue. Only hint I can giv is,, the file size is some where around 2.5mb,, and i believe this is NOT a constraint..but may be I can be wrong.
Please comment experts.
Regards,
Arnab .

Hi! Arnab,
com.sap.lcr.cimsrv.ChangePasswordServlet: Password change required for automated client. Please ensure that service client users don't have initial passwords. Alternatively, logon to the SLD user interface with the corresponding user and assign a new password. After the password has been changed, client settings must be updated accordingly
According to my knowledge the issue is not related to development side. Please check with your basis guys to check all the conenctions like SLD conenctions and J2EE engine status and also regardign ABAP stack.
1. Got to ABAP stack and enter T code SLDCHECK.
2. Also goto T code SMICM and there restart j2ee engine by selecting options J2EE soft Restart in the top menu.
3. If still issues s there then if possible ask them to do entirre XI server restart once..
Also go through this SAP note and ask your basis guys if any patches are to be implemented.
[Note 1225611- com.sap.lcr.cimsrv.ChangePasswordServlet:|
[1225611|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1225611]
Regards::
Amar Srinivas Eli

HTTP Adapter Receiver -- Message not arrive

Hello,
i send an IDoc from an SAP System to the PI and then with the HTTP Adapter
to a non SAP System.
The Message didn't arrive.
The Message Monitor says 'Call Adapter'.
Any Ideas?
Regards
Patrick

Patrick
A similar issue has been discussed here:
XI_J2EE_ADAPTER_XI_HANDLER - GENERAL_ERROR
Unfortuantely it is a gnereic error.
Try extending the trace file in the log configurator in Visual Admin to see if you can get a better indication of what is triggering the error.
Try running RSXMB_ACTIVATE_ICF_SERVICES in SE38 to see if this kicks off the Integration Engine services.
Also, check page 29 from this guide:
https://websmp102.sap-ag.de/~sapidb/011000358700001697502004E.PDF

Mail-Sender-Adapter, FetchReport

Hello,
can anyone explain me how to use the FetchReport option in the Mail-Sender-Adapter?
In the Adapter-Audit-Protocol the Adapter I always get an error.
The SAP-Help pages are not very helpful, an in SDN there are no articles about this.
kind regards
Thorsten Gawantka

Hi Chris,
the Definition is imported already.
Here are the message-data:
Message-Daten
Attribut     Wert
Status     fehlerhaft beendet
Wiederholbar     Nein
Beendbar     Nein
Fehlerkategorie     XI_J2EE_ADAPTER_XI_HANDLER
Fehlercode     CALL_CONSUMER_ERROR
Start     30.04.2008 13:27:03
Ende     30.04.2008 13:27:03
Sender-Partner
Sender-Service     opx
Empfänger-Partner
Empfänger-Service
Interface     http://sap.com/xi/XI/Mail/30
FetchReport
Quality-of-Service     Best Effort
Message     5b2e4a20-16a8-11dd-c67c-00145e36a4e4
Referenz
Konversations-ID
Version     0
Bearbeitet     Nein
Serialisierungskontext
Richtung     OUTBOUND
Message-Typ     Call
Profil     XI
Verbindung     Mail_http://sap.com/xi/XI/System
Transport     HTTP
Endpunkt     http://op-sap-xi:8000/sap/xi/engine?type=entry
Berechtigung     SAPPasswordCredential(PIAFUSER):password=********:sapclient=001:saplang=
Sequenznummer     0
Anz. Wiederh.     0
Fehlg.     1
Wiederh.     0
and the audit-protocol:
Audit-Protokoll für Message: 5b2e4a20-16a8-11dd-c67c-00145e36a4e4
Zeitstempel     Status     Beschreibung
2008-04-30 13:27:03     Erfolgreich     Mail: calling the module processor for channel CC_AeroDB_Mail_Send
2008-04-30 13:27:03     Erfolgreich     MP: Tritt in den Modulprozessor ein
2008-04-30 13:27:03     Erfolgreich     MP: Lokales Modul localejbs/sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean wird verarbeitet
2008-04-30 13:27:03     Erfolgreich     Mail: message leaving the adapter (call)
2008-04-30 13:27:03     Erfolgreich     Die Anwendung versucht eine XI Message synchron zu senden über Mail_http://sap.com/xi/XI/System
2008-04-30 13:27:03     Erfolgreich     Versuch die Message in die Call-Queue zu stellen
2008-04-30 13:27:03     Erfolgreich     Message erfolgreich in Queue gestellt
2008-04-30 13:27:03     Erfolgreich     Die Message wurde erfolgreich aus der Call-Queue abgerufen
2008-04-30 13:27:03     Erfolgreich     Der Status der Message wurde auf DLNG gesetzt
2008-04-30 13:27:03     Fehler     XI-Systemfehler erhalten. ErrorCode: NO_RECEIVER_CASE_BE ErrorText:   ErrorStack: No receiver could be determined
2008-04-30 13:27:03     Fehler     Rückgabe synchroner Fehlerbenachrichtigung an rufende Anwendung: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:.
2008-04-30 13:27:03     Fehler     Die Übertragung der Message über http://op-sap-xi:8000/sap/xi/engine?type=entry ist fehlgeschlagen, weil: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
2008-04-30 13:27:03     Fehler     Der Status der Message wurde auf FAIL gesetzt
2008-04-30 13:27:03     Fehler     Zurück zur Anwendung. Ausnahme: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
2008-04-30 13:27:03     Fehler     Mail: error occured: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
2008-04-30 13:27:03     Fehler     Mail: error occured: com.sap.aii.af.mp.module.ModuleException: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE: caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
2008-04-30 13:27:03     Fehler     MP: Ausnahme aufgetreten mit Grund com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
2008-04-30 13:27:03     Fehler     Mail: failed to call the module processor: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
Now the question is, how do i define the receiver in an asynchrounious scenario? And what does the FetchReport option exactly?
thx for your help
Thorsten

No message reach into Integration Engine ...

Hello,
I have following problem. I send message to XI through SOAP adapter. But the message doesn't reach of Integration Engine. It is delivered into Adapter Engine and then it stays in status "Waiting". When open message detail in RWB I get these information:
Message Data
Attribute     Value
Engine     Adapter Engine
Status     Waiting
Repeatable     Yes
Cancelable     Yes
Start     29.08.2008 12:14:59
End     29.08.2008 12:14:59
+Sender Party     +
Sender Service     BS_GetSupperior
Sender Interface     http://sntcz.cz/xmlns/holidays
MI_Holiday
+Receiver Party     +
+Receiver Service     +
+Receiver Interface     +
Quality of Service     Exactly Once
Error Category     XI_J2EE_ADAPTER_XI_HANDLER
Error Code     GENERAL_ERROR
Message     55C9628075B311DDABE200301875333B
+Reference     +
... and in defaultTrace file occures this message:
#1.5#00301875333B0057000000DE0000109C00045596D2CD72D8#1220006176812#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#XISUPER#18255d00759d11ddc1a500301875333b#SAPEngine_Application_Thread[impl:3]_31##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#00301875333B004B0000009D0000109C00045596D2CE9B64#1220006176890#com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension#sap.com/com.sap.aii.af.soapadapter#com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension#XISUPER#2919##srvbr05_NW4_2798750#XISUPER#ecff64f075af11dda90200301875333b#XI SOAP[BS_GetSupperior_SOAP/BS_GetSupperior/]_2449##0#0#Error##Plain###no message ID available#
#1.5#00301875333B0049000001270000109C00045596D3111C00#1220006181250#XIRWB.com.sap.aii.mdt.api.server.MessageMonitoringBean#sap.com/com.sap.xi.mdt#XIRWB.com.sap.aii.mdt.api.server.MessageMonitoringBean#XISUPER#2920##srvbr05_NW4_2798750##f03f74c075af11ddb4ce00301875333b#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/Applications/ExchangeInfrastructure/RuntimeWorkbench#Plain###enrichMessageData(): Error during retrieving the end-to-end-monitoring information
Thrown:
com.sap.aii.rwb.endtoendmonitoring.util.Sxmb_Get_Pmi_Info_Fault_Exception:
     at sun.reflect.GeneratedConstructorAccessor358.newInstance(Unknown Source)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
     at java.lang.Class.newInstance0(Class.java:308)
     at java.lang.Class.newInstance(Class.java:261)
     at com.sap.aii.proxy.framework.core.JcoMarshaler.unmarshalException(JcoMarshaler.java:429)
     at com.sap.aii.proxy.framework.core.JcoProxy.send(JcoProxy.java:82)
     at com.sap.aii.proxy.framework.core.AbstractProxy$JcoProxyHelper.send(AbstractProxy.java:173)
     at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:141)
     at com.sap.aii.rwb.endtoendmonitoring.util.PMI_PortType.sxmb_Get_Pmi_Info(PMI_PortType.java:28)
     at com.sap.aii.mdt.api.server.MessageMonitoringBean.enrichMessageData(MessageMonitoringBean.java:965)
     at com.sap.aii.mdt.api.server.MessageMonitoringBean.setMessageList(MessageMonitoringBean.java:762)
     at com.sap.aii.mdt.api.server.MessageMonitoringBean.getPureMessageList(MessageMonitoringBean.java:568)
     at com.sap.aii.mdt.api.server.MessageMonitoringObjectImpl0.getPureMessageList(MessageMonitoringObjectImpl0.java:1016)
     at com.sap.aii.mdt.api.server.MessageMonitoring_Stub.getPureMessageList(MessageMonitoring_Stub.java:1772)
     at com.sap.aii.mdt.server.integrationserver.IntegrationServerMonitoringBean.getMessageList(IntegrationServerMonitoringBean.java:354)
     at com.sap.aii.mdt.api.server.MessageMonitoringBean.setMessageList(MessageMonitoringBean.java:744)
     at com.sap.aii.mdt.api.server.MessageMonitoringBean.getMessageList(MessageMonitoringBean.java:552)
     at com.sap.aii.mdt.api.server.MessageMonitoringObjectImpl1_1.getMessageList(MessageMonitoringObjectImpl1_1.java:657)
     at com.sap.aii.mdt.api.server.MessageMonitoring_Stub.getMessageList(MessageMonitoring_Stub.java:810)
     at com.sap.aii.mdt.util.WebUtil.generateTableViewModel(WebUtil.java:1254)
     at jsp_monitor_new1219936385390._jspService(jsp_monitor_new1219936385390.java:9)
     at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)
     at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
If I try to send message to XI directly through HTTP adapter the message is not delivered into Integration Engine.
Do you have any idea what to check or where could be problem?
Thank you in advance for every advice!
Best regards,
Zbynek

Hi Zbynek,
I think the problem is in the structure of the xml you want to send. I mean, that the structure of the message you are sending by means of SOAP adapter is not the same that the structure in the Inegration Repository.
When you test your message with a wrong BS it is sent to the IE and you can see this message in sxmb_moni with error status. It`s obvius, there is no configuration for this scenario. However if you test your scenario with right parametes but the content (xml structure) is wrong, the step when the content of the call is converted to the structure of the IR will fail. And the message doesn`t get the IE.
So check the content of your call.
I hope it is useful for you.
Regards,
Carlos

SOAP- XI- RFC "NO_RECEIVER_CASE_BE"

Hi:
The scenario is SOAP->XI->RFC.
When i try to execute the scenario i get an error "NO_RECEIVER_CASE_BE"
receiver determination is true
Edited by: sky yuyi on Dec 23, 2008 6:36 AM

HI
there are some error log from Message Display Tool (Detail Display) .
Error Category: XI_J2EE_ADAPTER_XI_HANDLER
Error Code :CALL_CONSUMER_ERROR
Audit Log for Message: b6577f11-d31e-11dd-cc12-000f1f6bbad3
Time Stamp Status Description
2008-12-26 07:27:55 Success SOAP: request message leaving the adapter (call)
2008-12-26 07:27:55 Success Application attempting to send an XI message synchronously using connection AFW.
2008-12-26 07:27:55 Success Trying to put the message into the call queue.
2008-12-26 07:27:55 Success Message successfully put into the queue.
2008-12-26 07:27:55 Success The message was successfully retrieved from the call queue.
2008-12-26 07:27:55 Success The message status set to DLNG.
2008-12-26 07:28:03 Error Received XI System Error. ErrorCode: NO_RECEIVER_CASE_BE ErrorText: ErrorStack: Es konnte kein Empfänger ermittelt werden.
2008-12-26 07:28:03 Error Returning synchronous error notification to calling application: XIServer:NO_RECEIVER_CASE_BE:.
2008-12-26 07:28:03 Error Transmitting the message using connection http://dlxt:8000/sap/xi/engine?type=entry failed, due to: XIServer:NO_RECEIVER_CASE_BE:.
2008-12-26 07:28:03 Error The message status set to FAIL.
pls give me some ideas.

Problem in Webservice - XI -JDBC

Hi Experts,
When I tried to execute the Webserive -> XI -> JDBC scenario using xmlSpy, I am getting the below. Could you please tell me what could be the reason?
<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>RecoverableException</code>
 <text><![CDATA[
com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.DeliveryException: Application:EXCEPTION_DURING_EXECUTE:
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:919)
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:258)
 at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
Regards
Sara

Hi Prateek & Sumit,
I have checked with the Message Monitoring in RWB. Here are the errors.
Error Category XI_J2EE_ADAPTER_XI_HANDLER
Error Code CALL_CONSUMER_ERROR
Adapter Engine Errors
Received XI System Error. ErrorCode: EXCEPTION_DURING_EXECUTE ErrorText: ErrorStack: com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_RESPONSE_: RuntimeException in Message-Mapping transformatio~
2007-06-19 01:19:56 Error Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.DeliveryException: Application:EXCEPTION_DURING_EXECUTE:.
2007-06-19 01:19:56 Error Transmitting the message using connection http://<Host>:8001/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Application:EXCEPTION_DURING_EXECUTE:.
2007-06-19 01:19:56 Error The message status set to FAIL.
Regards
Sara
Message was edited by:
 Sara D

XI_J2EE_ADAPTER_XI_HANDLER

Similar Messages

Maybe you are looking for