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.

Similar Messages

  • 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.
    <b>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>.</b>
    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
    <b>Note: My input file should have various headers with associated line items...!</b>
    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: <b>Exception caught by adapter framework: RfcAdapter: receiver channel not in list of running clientPools:</b>. 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

  • 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: error while processing message to ..

    URGENT:
    <b>Legacy >XI>R3 interface</b>
    <b>SAP XI (file_adapter --> RFC_adapter)</b>
    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"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • 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.

  • 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 showing at Reciever mail Communication chanel

    hi all.
    i was created a proxy to mail scenario and i did tested this interface a long ago .at that time its working fine.
    but now when i retested the same interface and when i look at reciever mail CC under runtime work bench showing error as
    "Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.UnsupportedEncodingException: iso-8859-8-i"
    "failed to send mail: java.io.UnsupportedEncodingException: iso-8859-8-i"
    "Delivery of the message to the application using connection Mail_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.UnsupportedEncodingException: iso-8859-8-i."
    "Mail: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.UnsupportedEncodingException: iso-8859-8-i"
    "Exception caught by adapter framework: java.io.UnsupportedEncodingException: iso-8859-8-i"
    "MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: java.io.UnsupportedEncodingException: iso-8859-8-i"
    i dont think its a development issue the reason being i was tested the same interface a few days back and it was fine but now i got a problem.
    waiting for a cheerful answer.
    bye.
    sita ram.

    You can use the XMLAnonymizerBean to change the encoding in an XML document.
    Put UTF-8 as target. If you have hebrew characters, they can be represented in UTF-8 as well.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/45/d169186a29570ae10000000a114a6b/frameset.htm
    If you have a plain text, you can change the encoding with the MessageTransformBean
    http://help.sap.com/saphelp_nw2004s/helpdata/en/57/0b2c4142aef623e10000000a155106/frameset.htm
    set parameter:
    Transform.ContentType    text/plain;charset="UTF-8"

  • JDBC Receiver Error: Resource Pool Exception

    Hi All,
    I am having a scenario where my messages are flowing from SAP to legacy system using JDBC as the receiver adapter and at the legacy system it is updating the Oracle Database. It was all running succesfully from long back. Now I got the following error (in every communicaton channel which using the JDBC adapter, I chcekd this in communication channel monitoring) in Runtime Workbench --> Message Monitoring --> Adapter Engine.
    Error Category XI_J2EE_ADAPTER_JDBC
    Error Code PROCESSING_ERROR
    2009-09-16 22:03:35 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
    2009-09-16 22:03:59 Error Exception caught by adapter framework: Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection to URL 'jdbc:oracle:thin:@XX.XX.XX.XX:XXXX:XXXX': SQLException: ORA-04031: unable to allocate 3968 bytes of shared memory ("shared pool","unknown object","sga heap(1,0)","transaction")
    I have checked in SDN where I get information about : Cannot establish connection to URL 'jdbc:oracle:thin:@XX.XX.XX.XX:XXXX:XXXX':. But I am not getting any information about SQLException: ORA-04031: unable to allocate 3968 bytes of shared memory ("shared pool","unknown object","sga heap(1,0)","transaction").
    Can any body please let me know about the error which I am getting and how can I resolve it.
    Thanks in advance.

    Thanks Abhishek for ur reply.
    This means that it not the technical job in which I can provide any help. Our DBA they all are client.
    I have read in SDN that it cannot establish connection to URL because either Oracle is down or JDBC parameters have been changed (like user name/password).
    If enough resource pools are not available...enough space / resources seems to be unavailable then what needs to be done from my side (as the client always ask me what needs to be done then and by whom).
    Thanks
    Zeba

  • Error in Oubound message using Seeburger Adapter

    Hi,
    I'm getting this error on the Adapter engine when trying to generate an outbound EDI message with Seeburger adapter:
    2007-01-24 13:33:29      Error      Unable to forward message to JCA adapter. Reason:
    Fatal exception: com.seeburger.xi.connector.queue.QueueEntryRejectedException:
    Entry rejected due to error in resource management: null, Entry rejected due to
    error in resource management: null     
    2007-01-24 13:33:29      Error      MP: exception caught with cause
    javax.resource.ResourceException: Fatal exception:
    com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry rejected due
    to error in resource management: null, Entry rejected due to error in resource
    management: null     
    2007-01-24 13:33:29      Error      Exception caught by adapter framework: Fatal
    exception: com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry
    rejected due to error in resource management: null, Entry rejected due to error
    in resource management: null     
    2007-01-24 13:33:29      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: Fatal exception:
    com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry rejected due
    to error in resource management: null, Entry rejected due to error in resource
    management: null: javax.resource.ResourceException: Fatal exception:
    com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry rejected due
    to error in resource management: null, Entry rejected due to error in resource
    management: null.     
    Any ideas?
    Rgds,
    Yves

    Yves,
    I think there is some problem in invoking the seeburger adapter. Have you installed the adapter? Also after installing you have to import the metadata. Check this document for further help:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
    ---Satish

  • Exception in Adapter Framework

    Hi,
    I'm receiving the following error from my Adapter Framework:
    Exception caught by Adapter Framework: Cannot lookup the ra connectionfactory. Reason: Path to object does not exist at XXXXX, the whole lookup name is deployedAdapters/XXXXXX
    This error occurs in the 'delivering' step from Integration Engine to Adapter Enging: messages continue staying in that status. When I restart the Adapter Engine, the message are set to System Error, so I can work around it, but I'm more interested in why this error occurs.
    I'm using a XI 3.0 system, SP 17.

    Hi
    the adapter has to register in JNDI with the name "deployedAdapters/sample_ra/shareable/sample_ra" as you have specified in ra.xml.
    check whether  the   SPIManagedConnectionFactory,java file and the SampleRA.xml file, the JNDI name in both the files is deployedAdapters/sample_ra/shareable/sample_ra.
    The JNDI name should be:
    deployedAdapters/com.sap.aii.adapter.sample.ra/shareable/com.sap.aii.adapter.sample.ra
    Check the name in NWA: Problem Management -> JNDI Browser.
    Adjust your adapter metadata accordingly.
    Thanks

  • Xi adapter framework

    hello
    I have a scenario RFC 2 WS sync and the message does not leave the XI to the WS.
    the message that I see in the sxmb is
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Missing faultcode; HTTP 200 OK</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    any suggestions?
    Kfir

    this is what I see there and it doesnt lead me anywhere.
    am I right by saying that the message did not leave the XI? becuase I am not sure about it.
    2009-03-02 10:23:23 Success Message successfully received by messaging system. Profile: XI URL: http://mgnt371:50000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
    2009-03-02 10:23:23 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
    2009-03-02 10:23:23 Success Message successfully put into the queue.
    2009-03-02 10:23:23 Success The message was successfully retrieved from the request queue.
    2009-03-02 10:23:23 Success The message status set to DLNG.
    2009-03-02 10:23:23 Success Delivering to channel: AdobeMailService_SOAP_RCV
    2009-03-02 10:23:23 Success MP: Entering module processor
    2009-03-02 10:23:23 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    2009-03-02 10:23:23 Success SOAP: request message entering the adapter with user J2EE_GUEST
    2009-03-02 10:23:23 Success SOAP: Web Services Security processing...
    2009-03-02 10:23:23 Success SOAP: apply Web Services Security...
    2009-03-02 10:23:23 Success SOAP: Web Services Security applied.
    2009-03-02 10:23:24 Error SOAP: call failed: java.io.IOException: Missing faultcode; HTTP 200 OK
    2009-03-02 10:23:24 Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Missing faultcode; HTTP 200 OK: java.io.IOException: Missing faultcode; HTTP 200 OK
    2009-03-02 10:23:24 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Missing faultcode; HTTP 200 OK: java.io.IOException: Missing faultcode; HTTP 200 OK
    2009-03-02 10:23:24 Error Exception caught by adapter framework: Missing faultcode; HTTP 200 OK
    2009-03-02 10:23:24 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: Missing faultcode; HTTP 200 OK: java.io.IOException: Missing faultcode; HTTP 200 OK. Setting message to status failed.
    2009-03-02 10:23:24 Error The message status set to FAIL.
    2009-03-02 10:23:24 Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: Missing faultcode; HTTP 200 OK: java.io.IOException: Missing faultcode; HTTP 200 OK.

  • Io exception : The network adapter could not establish a connection

    Hi,
    I installed an agent on Solaris 9 hosted database 9.2.0.1. All is up But when I try to connect database, I receive this error message :
    Io exception : The network adapter could not establish a connection
    thanks for your help
    David

    Thanks for the solution. Today I was stucked up because of same issue and your solution worked for me too ...
    Thanks,
    Sujit

Maybe you are looking for

  • It says my session has timed out when I try and update an iOS game.What should I do to fix it?

    IT says my session has timed out when I try to update and ios game.What should I do to update my games?

  • 2nd Generation and iOS 4.3 (Not the question you are expecting.)

    Now before you get mad at me, I know 4.3 will never come out for 2nd gen iPod touches or any lower generation of iPod. I have a bit of a different question. I reset my Ipod because it was being kind of screwy lately, but when it went to get all of my

  • Simple two level structure

    This is a two part exercise... 1.  Complete ABAP program zstudent_registration.  The program will display the first level list.  The list consists of fields: <i>course_id course_name course_type programme </i> (The records come from the database tabl

  • Memory card reader

    I've got a HP Pavilion dv4-1225dx Entertainment Notebook PC and my SONY 2GB Memory Stick PRODUO can't be read. (in specs:  "5-in-1 integrated Digital Media Reader for Secure Digital cards, MultiMedia cards, Memory Stick, Memory Stick Pro, or xD Pictu

  • Uninstalling issues?

    I am running Logic Pro 9 on an Imac & I would like to uninstall Mainstage & Garage band as I don't use them & I want to make room for other softwares.If I do so will it affect Logic by any chance? I find the 'garage band' efects on plugins in Logic.W