XI ERROR IN ADAPTER FRAMEWORK

HI All,
we are getting the below error message
ERROR:
com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: resource error: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE:
Connection pool RfcClient[CC_BS_ECDCLNT130_RFCLookup]174f31f5971337d6af4e1e49826d9077 is exhausted.
The current pool size limit (max connections) is 1 connections.
Please help me in solving this.
Thanks:
Giridhar N

Please check this links:
Re: Connection pool exausted
http://help.sap.com/saphelp_nw04/Helpdata/EN/f6/daea401675752ae10000000a155106/content.htm
Thank you,
Shyam

Similar Messages

Error on Adapter Framework with Seeburger component

Hi,
I have the Generic EDI component from Seeburger Adapter, and I have a communication channel using the FTP Adapter from Seeburger with the module localejbs/Seeburger/solution/generic-edi, and when execute the communication channel, I have an error with the solution, the error is:
"Exception caught by adapter framework: Path to object does not exist at solution, the whole lookup name is localejbs/Seeburger/solution/generic-edi.".
I see the Seeburger documentation about installation and configuration from FTP Adapter, but I don´t find information about this error, somebody help me please with information about this error, what configuration I need review or where find documentation about this problem?.
We post a note about this problem on the OSS, the content of the note is:
We have installed the Seeburger's FTP adapter in SAP XI.
A communication Channel is calling this adapter nd executing a module called localejbs/Seeburger/solution/generic-edi. When the adapter is called the next error is shown;
Exception caught by adapter framework: Path to object does not exist at
solution, the whole lookup name is localejbs/Seeburger/solution/generic-edi.
Delivery of the message to the application using connection
FTP_http://seeburger.com/xi failed, due to:
com.sap.aii.af.ra.ms.api.RecoverableException: Path to object does not
exist at solution, the whole lookup name is
localejbs/Seeburger/solution/generic-edi.:
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at solution, the whole lookup name is
localejbs/Seeburger/solution/generic-edi..
Also, the host-ftp solution was used instead of the generic-edi with the same result.
The system we have is SAP PI 7.0 SPS09 with Seeburger 1.6.
Thanks and greetings,
Hervey.

Hi,
I have the same problem. What was the solution?
Regards
Kristian

Error in Adapter FrameWork

Dear All,
While doinf File to File scenerio, i m getting following error in Mesage Monitoring in Runtime Workbench "Transmitting the message to endpoint http://trexserver:8000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 403.."
Plz tell me what this error is all about and how this can be solved.
Reg,
nishu

Hi Nishu,
Just check the mentioned possibilities for your error one by one:
1.Did you maintain Client, userid, password, and lang information in SICF transaction -> sap/xi/engine? Double click on service and check whether you have entered correct information.
2.Then you might check the roles of the XIISUSER in SU01. In some case there are some double roles, i.e., two times the role SAP_XI_IS_SERV_USER assigned. One might have the date of the last update, the other one might have apparently the older version. Delete the older roles manually and the error should disappear.
3.to send messages to xi you need a service id / pwd which is specific to your landscape usually its xiappluser. Contact your basis group for password.
4.can you also try the following;
Visual Admin -> start the service,
"com.sap.aii.af.ms.app".
Please go through the followings links also :
http://help.sap.com/saphelp_nw04/helpdata/en/82/f4993c03e0cd37e10000000a11405a/content.htm
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
I hope the info provided help you solve your problem.
Regards,
Abhy

Regarding error showing as exception caught by adapter framework

hi all.
here in my scenario iam doing a file to rfc.
but when iam sending a file to rfc and when i see in sxmb_moni its showing as sucess.
bue when i look at runtime workbench under message monitoring (tab) it was showing as
MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception thrown in method process. The transaction is marked for rollback.: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback..
SO WHAT COULD BE THE ERROR IS THE EROR THAT WS SHOWING RELATED TO XI R SAP R3(system that was recieving)
waiting for the excellent answer.
cheers.
seeta ram.

HI Matias.
yes i did with the custom Rfc and the result is still the same
and to be more confident i was creates another xi scenario from file to Standerd Bapi BAPI_COMPANYCODE_GETDETAIL by creating a simple file with only one field and mappedwith only the request Message type of this Bapi and tested it.
and even this scenario is also showing the same in reciever rfc and under runtime work ench its showing the same as my old scenario and it is as follows
2007-10-15 10:47:51 Success Message successfully received by messaging system. Profile: XI URL: http://jssxid0:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2007-10-15 10:47:51 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2007-10-15 10:47:51 Success Message successfully put into the queue.
2007-10-15 10:47:51 Success The message was successfully retrieved from the receive queue.
2007-10-15 10:47:51 Success The message status set to DLNG.
2007-10-15 10:47:51 Success Delivering to channel: ReceieverChannel_RFC
2007-10-15 10:47:51 Success MP: entering
2007-10-15 10:47:51 Success MP: processing local module localejbs/RfcAFBean
2007-10-15 10:47:51 Error MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
2007-10-15 10:47:51 Error Exception caught by adapter framework: Exception thrown in method process. The transaction is marked for rollback.
Time Stamp Status Description
2007-10-15 10:47:51 Error Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception thrown in method process. The transaction is marked for rollback.: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback..
2007-10-15 10:47:51 Success The asynchronous message was successfully scheduled to be delivered at Mon Oct 15 10:52:51 SAST 2007.
2007-10-15 10:47:52 Success The message status set to WAIT.
2007-10-15 10:52:52 Success Retrying to deliver message to the application. Retry: 1
2007-10-15 10:52:52 Success The message was successfully retrieved from the receive queue.
2007-10-15 10:52:52 Success The message status set to DLNG.
2007-10-15 10:52:52 Success Delivering to channel: ReceieverChannel_RFC
2007-10-15 10:52:52 Success MP: entering
2007-10-15 10:52:52 Success MP: processing local module localejbs/RfcAFBean
2007-10-15 10:52:52 Error MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
and the message in sxmb_moni shows as it is processed sucessfully and
at reciever rfc as
Receiver channel 'ReceieverChannel_RFC' for party '', service 'CD103' (internal name 'RfcClient[ReceieverChannel_RFC]')
Client data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=103, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=mandapativ, jco.client.sysnr=00, jco.client.ashost=168.89.182.33}
Repository data: {jco.client.lang=en, jco.client.snc_mode=0, jco.client.client=103, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=mandapativ, jco.client.sysnr=00, jco.client.ashost=168.89.182.33}
Current pool size: 0, maximum pool size : 1
waiting for your great answer.
cheers.
seeta ram.

Message status "Holding" - Message monitoring adapter framework

Hello,
We have some messages with the status "Holding" in a queue in the message monitoring in the adapter framework.
Normally you have to restart the first message of that queue. The message with the status "system error". Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.
I already read the blog about "[How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417100)ID1887311350DB01819286872323159351End?blog=/pub/wlg/3566]"
The blog does not mention what to do when the first message (sequential number) is not available anymore.
Is it possible to restart the messages in the queue in that case?
Thanks
Kind regards
Frank

Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.
I assume that the message was deleted.....in this case the next message in the queue will be blocking the queue....so try resending this message....even the blog mentions that you either solve the error or cancel the message....so now start from the second message....if possible solve the error for this message....if not possible to resolve then cancel it so that rest of the queue gets processed
From the blog:
Now the erroneous message is the first message in the display. You can look at the error reason, try to fix the problem and
resend or cancel the message to release the queue.
Regards,
Abhishek.

PI 7.11: Adapter Framework caught exception: null

Hi,
I've a ABAP Proxy - to - SOAP scenario.
Message mapping works.
In the communication channel monitor I get the following error:
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException
Adapter Framework caught exception: null
In the log viewer in NWA I see the following two messages:
Marked transaction for rollback for meesage 516e304f-b083-8e3e-e100-00000a01095f(INBOUND). Reason: <null>
Caught exception com.sap.engine.interfaces.messaging.api.exception.MessagingException from application code with msgKey: 516e304f-b083-8e3e-e100-00000a01095f(INBOUND)
The payload for calling SOAP receiver looks like that:
<m:setEmployee xmlns:m="http://test.com" xmlns:fo="http://www.w3.org/1999/XSL/Format">
 <ns1:e xmlns:ns1="http://test.com">
 <address_Mail_Incoming_Type>
 <email>test.com</email>
 <phone>7890</phone>
 </address_Mail_Incoming_Type>
 <badge_ID>123</badge_ID>
 <cost_Center>321</cost_Center>
 <date_Hired>1980-01-01T00:00:00.000Z</date_Hired>
 <date_Of_Birth>1950-01-01T00:00:00.000Z</date_Of_Birth>
 <department>123</department>
 <division>ABC</division>
 <employee_Category>A</employee_Category>
 <employee_Code>1000</employee_Code>
 <employee_Id>1000</employee_Id>
 <employee_Status>ACTIVE</employee_Status>
 <first_Name>A</first_Name>
 <last_Name>B</last_Name>
 <letter_code_3>FRI</letter_code_3>
 <location>123</location>
 <position>123</position>
 </ns1:e>
 </m:setEmployee>
When I copy this payload into SOAP UI (surrounded by <soapenv:Envelope>, <soapenv:Header> and <soapenv:Body>), the WS call works.
The URL for the receiving CC should be ok (same as in SOAP UI), the "Do not use SOAP Envelope" checkbox is not flagged.
What can be the reason for that error message?
Thanks in advance!

I've now changed the setting of the external definition to "Using RPC style", but I'm still running into the same error than before:
10.02.2012 14:51:03 Information SOAP: sending a delivery error ack ...
10.02.2012 14:51:03 Error Adapter Framework caught exception: null
10.02.2012 14:51:03 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException
10.02.2012 14:51:03 Information SOAP: sent a delivery error ack
10.02.2012 14:51:03 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
The payload of the CC looks exactly the same than before:
<?xml version="1.0" encoding="UTF-8"?>
<m:setEmployee xmlns:m="http://test.com" xmlns:fo="http://www.w3.org/1999/XSL/Format">
 <ns1:e xmlns:ns1="http://test.com">
 <address_Mail_Incoming_Type>
 <email>test.com</email>
 <phone>123</phone>
 </address_Mail_Incoming_Type>
 <badge_ID>123</badge_ID>
 <cost_Center>123</cost_Center>
 <date_Hired>1990-01-01T00:00:00.000Z</date_Hired>
 <date_Of_Birth>1950-01-01T00:00:00.000Z</date_Of_Birth>
 <department>123</department>
 <division>ABC</division>
 <employee_Category>PERM</employee_Category>
 <employee_Code>1000</employee_Code>
 <employee_Id>1000</employee_Id>
 <employee_Status>ACTIVE</employee_Status>
 <first_Name>A</first_Name>
 <last_Name>B</last_Name>
 <location>ABC</location>
 <position>123</position>
 </ns1:e>
</m:setEmployee>
If I copy that payload (without <?xml version="1.0" encoding="UTF-8"?>) into SOAPUI (surrounded by SOAP envelope), the WS call works without any problem.
Why doesn't it work from PI?
Another question:
Why is it putting <ns1:e> into the payload of the new interface and <ns0:e> for the existing interface (which is working, see Re: PI 7.11: Adapter Framework caught exception: null)?
Could that be the reason why data is not sent properly to the SOAP receiver?

" Error while sending message: 500 Internal Server Error" RNIF Adapter

Hi,
I have configured B2B integration as   Sender : RNIF adapter & Receiver: XI Adapter.
I am able to test the configuration successfully in ESR and ID. But, whille testing with RWB using same test data, i am getting the following error:
Error while sending message: 500 Internal Server Errot.
     Could you anybody help me, what could be the reason? Even i am not getting any error messages in SXMB_MONI.
Thanks
Laxman

Hope this helps..
-Is the 500 internal SErver Error in RWB is only for this issue and the message is successfully processed in SXMB_MONI?
   Could be the PI Service User :PIAFUSER(Adapter framework user) login crendential issue or run out time error.
Try taking the payload from sxmb_moni and enter it in RWB > Adater engine> Test Message Tab > give proper sender interface information , enter payload and try sending message.   check what is behaviour

Error in Adapter engine of receiver soap adapter

Hi All,
There is one production issue i am currently facing in receiver SOAP adapter while interacting with third party web service(Asynchronous call).
Below is the description i am getting in audit logs.
Success SOAP: completed the processing
Error SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Success SOAP: sending a delivery error ack ...
Success SOAP: sent a delivery error ack
Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired.
Error The message status set to NDLV.
Moreover this is a production issue and interface was running fine till last friday.
Has someone ever faced this issue ?
Please provide your valuable inputs on this.
Thanks
Anku

Hi,
Search in sdn with your error message string,you will find ton of links.
HTTP401 error occurs for many reasons.
still no solution let us know..
Regards,
Raj

Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator

Hello Experts,
I am configuring the scenario ( AS2 to EDISeparator and EDISeparator to IDOC ).
Can you please help me with the error below which is from the either the EDISeparator Receiver channel or the EDISeparator Sender channle.
09.06.2014 17:52:18.709
Information
Message is encrypted with 1.3.14.3.2.7 algorithm
09.06.2014 17:52:18.778
Information
AS2 Message is signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.779
Information
AS2 Message message signature is validated, signer ID is X509CertSelector: [ Serial Number: 1624063516 Issuer: CN=Mendelson AS2 TEST,OU=Integration,O=Mendelson,L=Berlin,ST=Unknown,C=GE matchAllSubjectAltNames flag: true ]
09.06.2014 17:52:18.784
Information
AS2 document size is 350 Bytes
09.06.2014 17:52:18.784
Information
Payload charset converted from ISO-8859-15 to ISO-8859-15
09.06.2014 17:52:18.785
Information
B2B EdifactConverterModule : EDI format detected as EANCOM
09.06.2014 17:52:18.785
Information
B2B EdifactConverterModule: Message will be read as ISO-8859-1.
09.06.2014 17:52:18.785
Information
MP: processing local module localejbs/EdifactConverterModule
09.06.2014 17:52:18.785
Information
0}: The module-paramteter "eancom.subversion.prefix" is not set. Using default value "false"
09.06.2014 17:52:18.786
Information
0}: The module-paramteter "eancom..audit" is not set. Using default value "false"
09.06.2014 17:52:18.791
Information
MP: processing local module localejbs/CallSapAdapter
09.06.2014 17:52:18.791
Information
Application attempting to send an XI message asynchronously using connection AS2_http://sap.com/xi/XI/AS2
09.06.2014 17:52:18.792
Information
Trying to put the message into the send queue
09.06.2014 17:52:18.831
Information
Message successfully put into the queue
09.06.2014 17:52:18.831
Information
The application sent the message asynchronously using connection AS2_http://sap.com/xi/XI/AS2. Returning to application
09.06.2014 17:52:18.836
Information
MIC (DeJYUIusqQj6aaYRASdHhAo+4J0=) is calculated using SHA1 algorithm.
09.06.2014 17:52:18.838
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:18.843
Information
Message status set to DLNG
09.06.2014 17:52:18.845
Information
MDN is succcessfully signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.859
Information
Trying to put the message into the send queue
09.06.2014 17:52:18.912
Information
Message successfully put into the queue
09.06.2014 17:52:18.913
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:18.918
Information
Message status set to DLNG
09.06.2014 17:52:18.961
Information
Trying to put the message into the send queue
09.06.2014 17:52:19.001
Information
Message successfully put into the queue
09.06.2014 17:52:19.001
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:19.006
Error
MP: exception caught with message No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.006
Information
Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator
09.06.2014 17:52:19.006
Information
Message status set to DLNG
09.06.2014 17:52:19.009
Error
Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.010
Error
Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.015
Information
The asynchronous message was successfully scheduled to be delivered at Mon Jun 09 17:57:19 CEST 2014
09.06.2014 17:52:19.015
Information
Message status set to WAIT

Hello Ruchir Sinha and Dimitri Sannen,
I think I have progressed a bit. Just unsure of the usage of the Module configuration .I now get a new error (see below) and the updated config details are :
Sender Interface :
Receiver Interface :
Sender AS2 config :
Receiver EDISeparator config :
Sender EDISeparator config :
Receiver IDOC config :
IDoc details configured but not added in this document
16.06.2014 11:52:35.414
Information
The message was successfully retrieved from the send queue
16.06.2014 11:52:35.420
Information
Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator
16.06.2014 11:52:35.420
Information
MP: processing local module localejbs/ModuleProcessorExitBean
16.06.2014 11:52:35.420
Information
Message entered AF MP exit bean and will now be passed to the JCA adapter
16.06.2014 11:52:35.420
Information
Message status set to DLNG
16.06.2014 11:52:35.433
Information
UNA segment UNA found
16.06.2014 11:52:35.444
Information
Parsed UNB segment 333333333/014 to 111111111/014
16.06.2014 11:52:35.445
Information
Parsed UNH segment ORDERS D96A
16.06.2014 11:52:35.514
Information
Searching sender channel for Eancom message part message with Message type ORDERS, Message version number D, Message release number 96A, Interchange sender identification 333333333, Interchange sender identification code qualifier 014, Interchange recipient identification 111111111, Interchange recipient identification code qualifier 014, Message Subversion EAN008, Message Agency UN
16.06.2014 11:52:35.579
Information
Sender channel (Channel) keys: ObjectId=7abf551ddbb638268f91af80ec1c04c8 values: ToPartySchema= Attributes=(Attributes:Channel:EDISeparator:INBOUND) values: edisep.advanced=false snd.interchangeSenderId=.* snd.tradacommessagetype=.* snd.xpath= snd.xpath.value= snd.filterCondition=equal snd.edifactMessageReleaseNumTxt= snd.tradacomMessageTypeUsingFreeText=false snd.eancomMessageReleaseUsingFreeText=false snd.eancomMessageVersionFreeText= snd.odetteMessageType=.* snd.edifactMessageVersion=.* snd.xml.splitPath=null snd.eancomMessageVersion=.* snd.odetteMessageVersion=.* snd.edifactMessageRelNumUsingFreeText=false snd.otherVersionReleaseIndustryIdentifierCodeEnabled=false adapterStatus=active snd.vdaMessageType=.* snd.eancomCONTRLMessageRelease=3 snd.odetteMessageTypeTxt= snd.tradacommessageversion=.* snd.edifactMessageVerNumUsingFreeText=false snd.edifactMessageTypeUsingFreeText=false snd.xpathUsingFreeText=false snd.interchangeSenderIdCode=.* snd.otherVersionReleaseIndustryIdentifierCode=.* snd.odetteMessageTypeUsingFreeText=false snd.tradacomreccode=.* snd.edifactMessageVersionFreeText= snd.edifactInterchangeRecipientIdentification=.* eoio.sequenceId= snd.edifactMessageTypeTxt= snd.odetteMessageVerNumUsingFreeText=false snd.eancomMessageVerNumUsingFreeText=false snd.interchangeReceiverId=.* snd.eancomMessageRelease=.* snd.tradacomsendername=.* snd.tradacomMessageTypeTxt= snd.vdaLieferantenNummer=.* snd.interchangeReceiverIdCode=.* snd.edifactInterchangeSenderIdentificationCode=.* snd.odetteMessageVersionFreeText= snd.versionReleaseIndustryIdentifierCode=.* snd.edifactInterchangeSenderIdentification=.* snd.edifactMessageType=.* snd.eancomMessageType=.* snd.xpathTxt= snd.vdaMessageTypeTxt= deliverySemantics=eo snd.eancomMessageReleaseTxt= snd.plainmessagetype=.* snd.xml.split=false snd.edifactMessageRelease=.* snd.vdaMessageTypeUsingFreeText=false snd.tradacomrecname=.* edisep.addParameterParams=TableData: edisep.addParameterParams {} snd.encoding=iso885915 snd.vdaKundenNummer=.* snd.tradacomsendercode=.* snd.edifactCONTRLMessageRelease=3 snd.edifactInterchangeRecipientIdentificationCodeQualifier=.* snd.transactionSetIdentifierCode=.* Service=ASJAVA_DX5 Channel=B2BSE00002_O2C_ORDERS_PO_ECC_READ_EDISeparator EngineType=CA Party= TransProt=XI TransProtVers=1.0.0 FromPartySchema= FromPartyAgency= Direction=I MsgProt=EANCOM MsgProtVers=1.0.0 EngineName= AdapterType=EDISeparator AdapterSWCV=06c536e6fafe11e0bb1cea8f0a4290b1 ToPartyAgency= AdapterNamespace=http://sap.com/xi/XI/EDISeparator found. New message ID is f18894a8-f53b-11e3-a748-00001e96c7e2
16.06.2014 11:52:35.586
Error
MP: exception caught with cause javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.586
Error
Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.590
Error
Exception caught by adapter framework: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.591
Error
Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule

Exception caught by adapter framework

Hi
My scenario is based file -->RFC with BPM (parforEach) and multimapping.
File adapter is picking data according to input file, but RFC couldn't able to process each split data. I am gettign following error.
2006-09-11 10:39:07 Error Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
2006-09-11 10:39:07 Error Delivery of the message to the application using connection AFW failed, due to: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
Any idea how to resolve this issue..!
Regards
Sankar!

Hi..
Does this way i mapped file to BAPI, is this correct way ?
does we change the BAPi structure like this in target side?
Source Structure: TargetStructure
Messages (1:1) Message(1:1)
Message1(1:1) Message1(1:1)
MT_Request(1:1)
Recordset(0:U) --> BAPI_INCOMINGINVOICE(0:U)
HDR (0:1) HeaderData(1:1)
LINEITEM(0:U)
 field1(0:1) ---> filed1(0:1)
 field2(0:2)
 HDR--->GLACCOUNTDATA(0:1)
LINEITEM(0:U)---> item(0:U)
field3(0:1) ---> field(0:1)
field4(0:1) ---> field2(0:1)
and my BPM is :
Receive>Transfromation->Block with asyncSEND--->
Receiver : File_MI
Trasformation: IM, sorec: File_AI and tar: BApi_AI
Block -->parForeach, multi: BAPI_AI, curr: BAPI_AI
asyncSend-->BAPi_AI
Note: My input file should have various headers with associated line items...!
Thanks,
Sankar!

Adapter Framework caught exception - 401

Hi,
I am trying to use NTLM authentication using Axis adapter in PI 7.1 SP7 but getting 401 error.
Axis adapter works for Basic auth.
SAP Note 856597 talks about giving PI user security role xi_adapter_soap_message. Haven't found the equivalent navigation of visual admin in NWA.
Details from message monitoring
Information Axis: getting handler trp of java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
Error Axis: error in invocation: (401)Unauthorized
Error Adapter Framework caught exception: (401)Unauthorized
Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: (401)Unauthorized.
Any help is appreciated.
Thanks
Kiran Gollapudi

Hi guys,
Even the message being old, there are some of you that may want a hint on how to solve this problem.
First of all, please refer to the generic description of the error that may help one of you:
401 Unauthorized
Description: The request requires user authentication
Possible Tips:
u2022 Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
u2022 If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
u2022 If the error is in Adapter Engine
u2013then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
u2022 May be wrong password for user XIISUSER
u2022 May be wrong password for user XIAFUSER
u2013 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
Alternatively, ensure you maintain the correct password for all the service users according to one of the notes
below, taking into account your system version:
PI 7.1:
#999962 - PI 7.10: Change passwords of PI service users
XI 7.0
#936093 - XI 7.0: Changing the passwords of XI service users
XI 3.0
#721548 - XI 3.0: Changing the passwords of the XI service users
Hope I could helped.
Regards,
Caio Cagnani

Exception caught by adapter framework: RfcAdapter: receiver channel not in

Hi friends,
I am doing a file-RFC-file scenario. This is based on the blog: /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit The company ID is sent to the RFC through a xml file. RFC will return the company details which will be written again into a xml file.
My source file is getting picked up. But while sending the company ID to the RFC, i am getting an error. It says: Exception caught by adapter framework: RfcAdapter: receiver channel not in list of running clientPools:. I have checked the RFC and is running perfectly.
Can anybody help me to solve this error?
Regards,
Divija.

Hi,
it is better to restart the RFC adapter engine.
Is this RFC adapter is active in the Adapter Monitoring ?
Also change the RFC adapter configuration and activate it. Then activate the Receiver Agreement.
Also refer SAP note -730870 ( question no 17 and 20)
Regards,
Moorthy

Exception caught by adapter framework: unable to create a socket

Hi All,
I am using Idoc to XI To SOAP scinario. I got a alert asying that some messsage id is error. When i am trying to monitor that massage by taking help of the messgae id in the alert the message was successful in the SXMB_MONI,. Then i Went to message monitoring There the message statu was syetem error. Errror log is *Exception caught by adapter framework: unable to create a socket*. The communication channel was inactive wehere as the statsu of the channel was active in the directory... what is the reasonm for this error. and how to resilev this.

As pointed already, a socket exception occurs when then message cannot pass the Firewall settings....there will be a port configured to send message to the SOAP receiver.....ask network guys to make relevant settings so that the port is free from Firewall restrictions.
@Supriya --> Active/ Inactive status of the channel in ID and in CC monitoring are different things.
To change the status of your CC in RWB --> Stop & Start your SOAP CC....the channel will remain inactive till no message is passed through it....once a message is passed the status will change to success/ error.
You can also change the CC status to Automatic.
Regards,
Abhishek.

Debugging for exceptions caught by adapter framework

I am getting an error ' Exception caught by adapter framework while processing message to remote system..'
Is there any way to debug in such cases.
while executing sxmb_moni i am getting status processed successfully but getting an error in the runtime workbench of XI in message monitoring for component adapter engine.

Tamoghna,
This error comes when the adapter is not able to communicate with the target system. eg, if it is a JMS scenario, and the host is not reachable then you get this error. If you are in a domain, try to give fully qualified system name or ip address.
regards,
Felix

ICH :Exception thrown by adapter framework

i am working on a scenario for Supplier Managed Inventory
Process flow for initial data transfer is from R/3 (IDoc)>XI(XML)>SCM(XML)
We are using sap standard mappings to perform the conversion to XML. SXMB_MONI in XI shows "processed successfully" but getting error in runtime workbench in message monitoring of component 'adapter engine'. the error log is showing:
Error Exception caught by adapter framework:
error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was.
Error Delivery of the message to the application using connection AFW failed, due to: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was .
I am sending Product Activity Notification Idoc PROACT01. what adapter should i use. I tried using HTTP and XI adapter and it is not working. now i am trying RFC adapter and standard mappings from SCM Content , but getting this error. How can I troubleshoot this?

Hello Tamoghna,
If I've understood your scenario well, you should be using the IDoc Adapter. Assuming that you have an IDoc from the sending system, you need not do any XML conversion. This will avoid any XML related errors.
The error appears to be connection related. Please check that your Target system connection properties are defined in XI (TCode SM59). Also make sure the ALE name in the SLD is correct.
Let me know.
Regards,
Homiar.

XI ERROR IN ADAPTER FRAMEWORK

Similar Messages

Maybe you are looking for