Error in DB adapter

Hi,
i created a bpel process using DB adapter & deployed it in console. when i test that bpel process by giving input i am getting the following error.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'validateCCSelect' failed due to: JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
creditcard:validateCC [ validateCC_ptt::validateCCSelect(validateCCSelect_inputParameters,CcInfoCollection) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510
JCA Resource Adapter location error.
Unable to locate the JCA Resource Adapter via .jca binding file element
The JCA Binding Component is unable to startup the Resource Adapter specified in the element: location='eis/DB/MyDBConnection'.
The reason for this is most likely that either
1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or
2) the '' element in weblogic-ra.xml has not been set to eis/DB/MyDBConnection. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR).
Please correct this and then restart the Application Server
The invoked JCA adapter raised a resource exception.
please help me to solve this issue. i had created a DB connection and created a table in that connection before starting the bpel process.
thanks in advance,
Ayyadurai.M

hi,
i ve passed the correct input params. please find below the table which i created.
CCNo     FName     LName     SSN     Creditrating     Status
1234     Arun     Kumar     333     Good     valid
in test console i m passing CCNo(1234) as request in response is should get as 'valid'. but i am getting blank response for that. please help me to solve this issue.
thanks in advance,
ayyadurai.

Similar Messages

  • Error-Receiver File Adapter using Variable substitution when file is empty

    XI Experts,
    We are on PI 7.0, SP14.
    We are using variable subtitution to get the filename from source message. This works fine as long as we have data in the payload for filename element. But we have a scenario where we don't have to create file when certain condition does not exists in source message so in the message payload filename element will not exists in such condition and file will be empty and we should not create file.
    Parameter in the communication channel for Handling empty message is "Ignore".
    Does anyone knows how to handle this scneario. We don't want to default any file name in the message mapping if source file name element does not exists.
    We are following getting error in the Adapter engine.
    MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: The following variable was not found in the message payload: file: com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: The following variable was not found in the message payload: file
    Thanks
    MP

    You can implement this by writing the module to throw an exception or whatever method you want to execute.
    If you don't want to receive an error message then module is suitable for you.
    Gaurav Jain

  • Error:SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. --- There is an error in XML document (1, 447). --- Input string was not in a correct format.

    Hi All,
        We have a scenario of FTP-->PI---> Webservice.  While triggering the data in the FTP, it is failing in the PI with the below error
    SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 447). ---> Input string was not in a correct format.
    Can you please help?

    Hi Raja- It seems to be a data quality issue.
    Check for the value @ 1447 position in the xml message that you are trying to send to web service..
    may be a date filed/decimal value which is not in expected format.

  • Getting error in the adapter engine when sending a message

    Hi,
    I'm always getting this error in the adapter engine: Message processing failed. Cause: com.sap.aii.messaging.util.URI$MalformedURIException: no scheme
    The comm channel ends up in error because of messages having the above error.
    Could someone please help?
    Thanks.
    Mike

    Mike.
    Please check this links.
    Check your adapter and restarted.
    com.sap.aii.messaging.util.URI$MalformedURIException: invalid port number
    Re: Prerequisites to setup configure mail scenario.
    error in communication channel
    Error :Receiver File Channel not Initialized

  • File-IDoc scnario : Error in call adapter

    Hi Experts,
    I have developed File to IDoc scenario. And getting the following error in "Call Adapter" pipeline step. I have mapped the control record values in IDoc like Sender Partner, no, port and same for receiver.
    Have created:
    In XI: RFC destination to connect to ECC (sm59)
            Port for the above RFC sestination (idx1)
    In ECC: New logical system for source file system (BD54)
                Partner Profile for Source (we20)
    Also in Receiver_IDoc_CC, checked options for 1. Apply control record values from payload 2. Take Sender and Receiver from Payload
    <?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="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>Transaction IDX1: Port SAPEAQ_100, client , RFC destination contain errors</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: Transaction IDX1: Port SAPEAQ_100, client , RFC destination contain errors</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Please tell me if i am doing any mistake.
    Br,
    Nilz

    Hi,
    Adding to Björn
    Check the Port ( Tcode - idx1 ) Port SAPEAQ_100  & Select the Business System where you declared IDOC adapter -go to - Service  and check whether you have mentioned the right Logic System,System ID & Client.
    Cheers
    Agasthuri Doss

  • SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPT

    Hi there,
    I am trying to publish a file from SAP as web service using XI and SOAP Adapter.
    I am using ABAP proxy to get the data into XI.
    Designing and Configuration in XI has no problems because when i use File adapter the data is trasmitted to FTP server.
    But when I used SOAP Reciever adapter I am getting following error in RWB
    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 500 Error during parsing of SOAP header.
    <b>Scenario</b>: SAP ABAP Proxy -> XI -> WebService. Asynchronous.
    <b>SOAP</b> Receiver adaptor.
    <b>Target URL</b> http://<host>:<port number >/sap/xi/engine?type=entry&version=3.0&Sender.Service=SAPDC2653&Interface=urn:bzttest:00:hsa:test%5EOB_MI_BZT_TEST&QualityOfService=ExactlyOnce
    Do not use SOAP Envelop is checked.
    <b>SOAP Action</b> http://sap.com/xi/WebService/soap1.1
    What i am missing here? How should I solve this problem?
    Any help is appreciated,
    Thx,
    Yogi

    Say there's a bapi/rfc that you want to call on an R/3 backend (e.g. 4.6c).  On it's own, the R/3 system cannot expose the rfc/bapi as a web service, but XI can.  So in this case, the scenario would be:
    WS client -> XI -> R/3
    When XI "exposes" a web service, it is exposing a service for a receiving system (in the above example, the R/3 system).  XI itself does not provide or contain the service implementation.  When XI exposes a web service, it is always done via the <b>sender</b> soap adapter (i.e. if soap adapter is used).   Receiver soap adapter is used to call or consume an actual web service from an external application.
    Regards,
    Jin

  • Error in Call Adapter (IDOC- XI- FILE)

    Hello,
    i have got the following error message in the integration engine monitoring in the "call adapter" part:
       td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active HTTP response contains status code 503 with the description Service Unavailable XML element Envelope missing in SOAP message header (SAP XI Extension)
    What is the AFW application?????

    Hi Christian,
    Have a look at the following thread, it might be useful
    XI Server Malfunction:Error in Receiver Adapter
    Regards
    Suraj

  • Error in File Adapter: no alert generated

    Hi folks,
    I have a problem with monitoring our file adapters.
    In one scenario we occasionally get the following error:
    Fehler bei der Konvertierung des Dateiinhalts in XML an Position 0: java.lang.Exception: ERROR converting document line no. 2 according to structure 'eTSFlatDetailStructure':java.lang.Exception: ERROR in configuration / structure 'eTSFlatDetailStructure.': More elements in file csv structure than field names specified!
    So I have build an alert category with me as recipient and an alert rule in Runtime Workbench with the following attributes:
    - Rule active
    - Alert-category as I have created above
    - Bound to Message: no
    - Error occures in Adapter Engine -> File Adapter
    I have tested the Category... it works... but the rule does not fire any alert.
    Has anyone an idea how to solve this problem?
    Thanks
    Greetings
    Habib Sarbas

    Hi,
    the report generates following output:
    20090507072803,7018210          0  07.05.2009    09:28:03      0AFE24F09F47460132CAD06697A18964
    *Error records received from AF on host rd-srxt0_RXT_00 (sysid: RXT client:  ). Try to send Alert...
    20090507072803,7045260          0  07.05.2009    09:28:03      0AFE24F09F47460132CAD06697A18964
    *Find rule for (From:vkeTSFlatBPM:vkeTSFlatBPM_var01_eTSSender:mi_eTSFlat_var01_out_asyn:urn:rsd-de:xi:ZRSD_XI_01:vkeTSBPM To::::)
    20090507072803,7063530          0  07.05.2009    09:28:03      0AFE24F09F47460132CAD06697A18964
    *No matching rule found
    I also tried to specify the conditions with service, interface and namespace, but this is only possible if i switch bound to message to yes...
    but the error occurs in file adapter... there is no message generated...

  • Error in BPE Adapter Processing

    Hi Experts,
    I have a scenario in which data flow from JDBC => BPE => ECC.
    while sending data from JDBC to BPE adapter, faced below error in SXMB_MONI.
    "Error in BPE Adapter Processing"
    In SXMB_MONI, Overall status displays as "Manual Restart Possible" error as attached below.
    I completed the all configuration related to SWF_XI_CUSTOMIZING and SXI_CACHE.
    also my Integration process has return code 0 in SXI_CACHE.
    I also want to know what are the software's required in PI related to BPM for both JAVA and ABAP Stack. i have a SAP PI System with version 7.31.
    Please guide me to solve this error and also inform me if any configuration related to BPE adapter is missing or not.

    hi dear,
    Tried the reports which are mentioned in the notes and followed the link
    but we couldn't resolve the same. can u please help us to move ahead to resolve our issue.
    any corrections / suggestion regarding the same.
    Permanent error in BPE inbound processing

  • Error in resource adapter cleanup.. javax.resource.ResourceException: java.

    Hi,
    I am getting the following error in my Oracle AS 10g R3 on Solaris .
    Error in resource adapter cleanup.. javax.resource.ResourceException: java.sql.SQLException: Closed Connection
    in log file:apps/oracle/oc4j_home/j2ee/homeMYAPP/log/homeMYAPP_default_group_1/oc4j/log.xml
    (Click on the log file link to download the log or view it as plain text)
    Can any one explain why this error comes.
    Regards,
    Kumar

    Hi,
    I am getting the following error in my Oracle AS 10g R3 on Solaris .
    Error in resource adapter cleanup.. javax.resource.ResourceException: java.sql.SQLException: Closed Connection
    in log file:apps/oracle/oc4j_home/j2ee/homeMYAPP/log/homeMYAPP_default_group_1/oc4j/log.xml
    (Click on the log file link to download the log or view it as plain text)
    Can any one explain why this error comes.
    Regards,
    Kumar

  • Security Error in Mail adapter

    Hi all,
    In the sender side i am using mail adapter and also i had enabled the security. So the mail adapter is going to validate the mails. But when its going to validate its giving the following error in the Adapter Moniter...
    "java.security.PrivilegedActionException: com.sap.aii.af.security.impl.exception.MessageSecurityException: MessageSecurityException in Method: VerifySMIME.run(). MessageSecurityException: LocalizedMessage: SMIMEException in Method: verifySMIME( MessageContext, CPALookupObject ). LocalizedMessage: SMIMEException in method: verifySignedData( InputStream, X509Certificate, OutputStream ). An I/O error occurs while writing to the OutputStream.. "
    Please help me to find problem.

    Hello Beena,
             I have already tested the same and its working fine.
    As I mentioned earlier in some cases the mails are sent properly but in few others it is failing.
    I am not able to understand the reason for this discrepancy.
    Regards,
    Mayank

  • Automatic restart of Error-Message in Adapter-Engine (Job?)

    Hi,
    we are working on PI 7.11 and facing following problem:
    Often in message-monitoring error-messages are forgotten because of wrong date-selections by the monitorer (not enough days back). It would be very nice, if there is a function witch is repeating error-messages in adapter-engine automaticly and witch can be scheduled.
    Does anybody know something about an excisting program / function on PI?
    Regards
    Jürg

    Hi,
         By default if any failure occurs in adapter engine (in case of receiver,during delivery to target system)
    it will retry 3 times after a period interval of 5 minutes..this is by default even this can be change if needed with the help of the proeprties at NWA/VA...
    but in case of failures at IE level (mappings,...) then you need to schedule the report RSXMB_RESTART_MESSAGES....
    search SDN if like to know more about the reports...
    HTH
    Rajesh

  • File to Mail Scenario- Error in Mail Adapter

    Hi,
    I am working on File to Mail Scenario- I am getting the below Error in Mail Adapter
    Delivering the message to the application using connection Mail_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.sdk.xi.srt.BubbleException: Failed to call the endpoint  [null "null"]; nested exception caused by: java.io.IOException: no receiver address specified.
    Could any one please provide a solution
    Rgards,
    Varun

    Please recheck the mail adapter configuration.Check the url field.
    Ref for Mail adapter
    /people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure
    http://help.sap.com/saphelp_nw04/helpdata/en/02/265c3cf311070ae10000000a114084/frameset.htm

  • System error in File Adapter

    hi experts,
    I have a File to File (FTP) scenario.
    The message caught the system error in the Adapter engine with out any error message.
    the last message noted in the adapter engine is
      Success File adapter receiver: processing started; QoS required: ExactlyOnce
    Please suggest to resolve the error.
    Thanks in advance,
    MK

    Raj,
    As i mentioned above,
                                      the last message noted in the (audit log)adapter engine is
    Success File adapter receiver: processing started; QoS required: ExactlyOnce
    Agasthuri Doss,
                               There are no error messages.
                   It shows the message: Processing started
                                                     Polling interval started. Length: 60.0 seconds
                                                      Processing finished successfully
            And the file is deleted from the source directory.
    Edited by: mk.xi on Feb 25, 2008 1:51 PM

  • SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCE

    Hi ,
    I am getting below error in SOAP reciever channel.
    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: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection SOAP_http://sap.com/xi/XI/System is currently not started. at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:996) at sun.reflect.GeneratedMethodAccessor501_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2662_10002.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275) at sun.reflect.GeneratedMethodAccessor326_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy114_10002.process(Unknown Source) at com.sap.aii.adapter.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:175) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:470) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:163) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82) at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:74) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:425) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)

    Hi,
    Can you please elaborate more on your problem.
    Regards,
    Raghu.

  • BPM dont return (catch) error occured in Adapter

    Guys,
    I created my scenario with  BPM.
    Details:
    Design:
    MI_TESTE_SEND_outb - Outbound, Sync
    MI_TESTE_outb - Abstract, Sync
    MI_TESTE_ABS - Abstract, Async
    MI_TESTE_inb - Inbound, Async
    BPM
    Send1 - Open Bridge,
    mesage - MI_TESTE_ABS
    sync message - MI_TESTE_outb
    Receive1 - Async
    message - MI_TESTE_ABS, create new transaction
    Receive2 - Close Bridge of Receive1
    message - MI_TESTE_ABS
    Configuration:
    No errors in configurations, i create SOAP Adapter Receiver for use in Receive1 from BPM
    The send is a RFC Sender.
    When i launch the process, in SOAP Adapter occurs errors (url invalid), but in SXI_MONITOR dont show errors, otherwise, my process is completed and ok.
    That occurs because the error found in Adapter and my BPM dont catch the error.
    Can anybody tell me, how can i catch the error from Adapter in my BPM? How can i return from RFC the that error?

    João,
    Could you explain the scenario plz? Coz the steps which u've given is confusing a lot.
    raj.

Maybe you are looking for