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.

Similar Messages

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.

Adapter Framework unable to create outbound JCA connection

Hi All,
I have a requirement in which I have to send a request from Siebel to SAP & get a response from it.
I have deployed my process on Oracle AS BPEL console.
When I try to initiate my deployed process I get below mentioned error.
<summary>
http://127.0.0.1:8888/orainfra/wsil/adapters/applications/GetDetail_invoke.wsdl?wsdl [ GetDetailPortType::GetDetail(input_GetDetail,output_GetDetail) ] - WSIF JCA Execute of operation 'GetDetail' failed due to: Adapter Framework unable to create outbound JCA connection.
http://127.0.0.1:8888/orainfra/wsil/adapters/applications/GetDetail_invoke.wsdl?wsdl [ GetDetailPortType::GetDetail(input_GetDetail,output_GetDetail) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: javax.resource.spi.EISSystemException: IWAFManagedConnectionFactory:Exception javax.resource.ResourceException: Problem activating adapter. (JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [no sapjcorfc in java.library.path]. java.library.path [D:\product\10.1.3.1\OracleAS_1\jdk\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\product\10.1.3.1\OracleAS_1\opmn\bin;D:\product\10.1.3.1\OracleAS_1\opmn\lib;D:\product\10.1.3.1\OracleAS_1\bin;C:\WINDOWS;C:\WINDOWS\system32]). Check logs for more information
; nested exception is:
ORABPEL-12511
Adapter Framework unable to create outbound JCA connection.
http://127.0.0.1:8888/orainfra/wsil/adapters/applications/GetDetail_invoke.wsdl?wsdl [ GetDetailPortType::GetDetail(input_GetDetail,output_GetDetail) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: javax.resource.spi.EISSystemException: IWAFManagedConnectionFactory:Exception javax.resource.ResourceException: Problem activating adapter. (JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [no sapjcorfc in java.library.path]. java.library.path [D:\product\10.1.3.1\OracleAS_1\jdk\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\product\10.1.3.1\OracleAS_1\opmn\bin;D:\product\10.1.3.1\OracleAS_1\opmn\lib;D:\product\10.1.3.1\OracleAS_1\bin;C:\WINDOWS;C:\WINDOWS\system32]). Check logs for more information
Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console.
</summary>
I have installed Oracle Adapter 10.1.3.1 on Oracle SOA Suite 10.1.3.1 & then upgraded my SOA Suite to 10.1.3.3.
Its a very critical issue.
Please help me out of it.
Thanks & Regards,
Shanty

I have resolved this error.
If you are facing the same error then follow the following steps:
1. Shutdown the Oracle SOA Suite.
2. Copy sapjcorfc.dll into C:\WINDOWS\system32
3.Edit oc4j-ra.xml located at below locations
a. OracleHome\j2ee\home\application-deployments\default\jca-app-adapter
b. OracleHome\j2ee\home\connectors\jca-app-adapter\jca-app-adapter\META-INF
by editing the values
<config-property name="AdapterName" value="SAP"/>
<config-property name="Config" value="SAP_Target_You_Have_Created_in_iaexplorer"/>
Cheers,
Shanty

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!

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

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

Mail sender Adapter error: unable to create a socket

Hi,
I got the following error in CC - mail adapter:
exception caught during processing mail message; java.io.IOException: unable to create a socket
both for pops and imaps protocols
I could not find answers to how to fix it.Any help will be appreciated.
Are there any other logs,trace to get more info about the error?
Thank you.

Hi Rinku,
I checked the mail server url, acoount and password , if this was what you ment. I also read the wiki. It's a good one but describes simple pop and imap protocols.
I still have the same error message and I am using imaps and pops. I've read in forum post that I need to to implement (import) "SAP Cryptographic toolkit" and import a certificate to ABAP and Java part of XI.
Link: [Error in a Mail Adapter;
Do you know how to do it? ( I am new to XI)
Thank you for your help.
Nataliya

SOAP Receiver Adapter: DeliveryException: unable to create a socket

Hi all,
I have a RFC <-> XI <-> SOAP scenario, using HTTPS and I found this exeption (RW):
Received XI System Error. ErrorCode: GENERAL ErrorText: com.sap.aii.af.ra.ms.api.DeliveryException: unable to create a socket ErrorStack:
Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: unable to create a socket.
Transmitting the message using connection http://<hostname>:<portname>/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: unable to create a socket.
The message status set to FAIL.
Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: unable to create a socket.
Thanks in advance,
Daniela

Hi,
did you enable SSL?
http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/content.htm
Regards,
michal

Exception caught by adapter framework: error while processing message to ..

URGENT:
Legacy >XI>R3 interface
SAP XI (file_adapter --> RFC_adapter)
Friends.
 I need your help for next problem above:
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: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
Thanks very much for your helps
Nota: This error is XIPRO environment.
Message was edited by:
 Cristian Alejandro Toro Salazar
Message was edited by:
 Cristian Alejandro Toro Salazar

Hi Cristian,
>>>>functiontemplate from repository was
this SAP note 730870 - describes your issue
let me know if it helped
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

File Adapter - FTP - Unable to Create new pooled resource

Hi Friends,
I am getting the following error while using file adapter with FTP protocol...
Attempt to process file failed with Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: FTPEx: PASS command failed
Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: FTPEx: PASS command failed
Error Exception caught by adapter framework: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: FTPEx: PASS command failed
Error Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: FTPEx: PASS command failed.
Can someone help me to solve this probelm..
Regards,
Shyam.

Hi,
Try to check the directory you have specified in the CC and also check whether you are able to connect to the FTP server with those login credential and access the directory specified.
Also let me know whether it is working fine for other scenario's or not.
Regards,
Nithiyanandam

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.

SOAP unable to create a socket after OS upgrade OS/400 V5R4 to V7R1

Hello,
after we upgraded our OS from System i V5R4 to V7R1 we have problems with our SOAP adapters.
In the runtime workbench and also in the SXMB_MONI the following error occured:
SOAP: call failed: java.io.IOException: unable to create a socket
Message-Verarbeitung fehlgeschlagen. Grund: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
Before the OS upgrade the adapter rans without any errors and we tested the connection to the partner
with an system running V5R4 with success. So it seems to be an error that came with the OS upgrade.
Any idea? Had any one the same error after migration to V7R1? Thanks for your help.
Best regards,
Matthias

Hello,
we found out that the error is attached to DNS and Java stack. Our ABAP stack can set the url to the correct IP adress, if we configure a entry in SM59. Also the java stack calls our partner over SOAP with IP adress, but not with url. The urls are stored in the local host table, so we suppose that the java stack doesn't use the local dns table and doesn't ask our dns server for the right ip adress.
Does anybody know this issue? The only change we did is upgrade OS/400 from V4R4 to V7R1. If a mod see this, I think it make sence to move this thread into the forum SAP on DB2 UDB for i5/OS (DB4). Thank's.
Matthias

SOAP Adapter: java.io.IOException: unable to create a socket

Hi,
I am trying to use the soap adapter to connect to a URL and post a document. When I try, the adapter throws the following
java.io.IOException: unable to create a socket
Does anyone know what causes this?
I get it both with the SOAP Envelope turned on and off.
I am trying to post to a URL that is usually used for straight HTTPS posts, could this cause an issue? The only reason we are using the SOAP adapter is to be able to send attachments! Hence, SOAP adapter, no SOAP envelope.
Kind Regard,
Chris

Hi,
Had faced the same issue. The possible reasons were :
1. Either the target server might not be responding.
2. The Target URL configured in the communication channel might be wrong.
3. The port to which the message is being sent might not be opened which you need to cross-verify.
For me the issue was the port, which wasn't enabled from our end. The messages went past successfully once it was enabled.
Cheers!!
Jithin James.

Unable to create a socket

We are trying to receive an XML file from a partner (with SSL) through our PI system. About half of the files we receive during the day succeed normally. The other half fail with the following messages:
In CC monitor:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: unable to create a socket: java.io.IOException: unable to create a socket
SOAP: call failed: java.io.IOException: unable to create a socket
and in SXMB_MONI
com.sap.aii.af.ra.ms.api.DeliveryException: unable to create a socket
Does anyone know why this could be happening to only some of the files and not others when all other things are the same?

Hi Blake Haan,
I faced some times this issue.As of my analysis, It is various downtimes from your target system or error in your server. So might be that reason,These type of exceptions are came.
My suggestion is please resend these message from RWB-->Message Monitoring, Before that please check with your target sever support persons.
And please take some time to resend it those messages which are failed.
Thanks,
Sateesh

Exception caught by adapter framework: unable to create a socket

Similar Messages

Maybe you are looking for