CLIENT_SEND_FAILED

Hi,There
We are SP 18,patch level 2.
After we adapted to SP 18(17->18), Some problem occured.
We are using "Proxy". This Problem is Sender Proxy of R/3 side.
Problem is blow.
This "CLIENT_SEND_FAILED" occur hardly ever, not always.
And After Auto-retry start, IS connection become to success.
Please give your help.
Regards,
Miru
=============================================
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
  <SAP:Category>XIServer</SAP:Category>
  <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
  <SAP:P1>112</SAP:P1>
  <SAP:P2>HTTPIO_PLG_ICM_CONNECT_FAILED-Fehlermeldung beim Senden der Daten.</SAP:P2>
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText />
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack>Error when sending by HTTP (error code: 112, error text: HTTPIO_PLG_ICM_CONNECT_FAILED-Fehlermeldung beim Senden der Daten.)</SAP:Stack>
  <SAP:Retry>A</SAP:Retry>
  </SAP:Error><b></b>
Message was edited by: taewoo kim

Hi, all
Thank fro your replay.
I  increased ICM_TIME_OUT.
I really appreciate your help.
regards,
Miru

Similar Messages

  • CLIENT_SEND_FAILED error code: 500, error text: Internal Server Error

    Hi,
    Developed Proxy <-->PI<-->JDBC SELECT scenario and getting the following error.
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
      <SAP:P1>500</SAP:P1>
      <SAP:P2>Internal Server Error</SAP:P2>
      <SAP:P3>(See attachment HTMLError for details)</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error while sending by HTTP (error code: 500, error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    When I cross checked the JDBC Receiver communication channel in Runtime Work Bench
    request and response were successfull. RWB shows the following message.
    2009-06-12 09:34:50 Information The message was successfully received by the messaging system.
    2009-06-12 09:34:50 Information Message successfully put into the queue.
    2009-06-12 09:34:50 Information The message was successfully retrieved from the request queue.
    2009-06-12 09:34:50 Information The message status was set to DLNG.
    2009-06-12 09:34:50 Information Delivering to channel: DB2ReceiverTableSPT
    2009-06-12 09:34:50 Information JDBC Adapter Receiver processing started, required QoS BestEffort
    2009-06-12 09:34:50 Information JDBC Adapter Receiver Channel DB2ReceiverTableSPT:
    2009-06-12 09:36:35 Information Database request processed successfully.
    2009-06-12 09:36:35 Information The message was successfully delivered to the application using connection JDBC_http://sap.com/xi/XI/System.
    2009-06-12 09:36:35 Information The message status was set to DLVD.
    I had gone thru all the previous threads related to 'CLIENT_SEND_FAILED' but
    those did not solve my problem.
    Can some one help me to solve this issue.
    Thanks,
    Vijay.

    I made necessary changes as per the blog. Appended '_response' for JDBC response structure.
    Still I am facing same problem.
    Strange....delibarately gave the link so that you can cross-check the JDBC config on receiver side...I assume that the proxy is configured properly with the Sync communication....also mapping is done accordingly...
    Regards,
    Abhishek.

  • HTTPIO_PG_MI_ERROR with error code 102:CLIENT_SEND_FAILED

    Hi Experts ,
    I  was getting HTTPIO_PG_MI_ERROR with the  error test showing Error WHILE SENDING BY HTTP with Error code showing like 102 in the R/3 system , and  the interface is synchronous mode.
    Please help me ..
    Thnks in Advance.

    Hi,
    i am sory small correction in the  the error it is 
       with error code 102:CLIENT_SEND_FAILED with the test HTTPIO_PLG_MPI_ERROR
    thnks so much

  • CLIENT_SEND_FAILED HTTP ERROR 500 Internal Server Error

    Hello Experts,
        I have a scenario from Proxy->SOAP.  I am facing the below error.  I have many other Scenarios from Proxy -> SOAP all of them are working fine except this.
    I am using NW07_06_REL With SP 06
    <?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>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
      <SAP:P1>500</SAP:P1>
      <SAP:P2>Internal Server Error</SAP:P2>
      <SAP:P3>(See attachment HTMLError for details)</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error while sending by HTTP (error code: 500, error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    HTML Error
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not create Message from TransportMessage. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIMessage creation failed (inbound). Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage. Reason: com.sap.aii.af.sdk.xi.mo.MalformedMessageException: Unexpected length of element <sap:Main><sap:Interface @sap:namespace> = xxxxx; nested exception caused by: com.sap.aii.af.sdk.xi.util.XMLScanException: Unexpected length of element <sap:Main><sap:Interface @sap:namespace> = XXXXXX
    The message clogs in the qRFC Queue. Not able to re-process it.
    I have already checked Most of the threads on the SDN, They didn't help me.
    Any help greatly appreciated
    Edited by: Kannan Narayanan on Dec 28, 2010 3:29 AM

    --> Error while sending by HTTP (error code: 500, error text: Internal Server Error)
    Answer: 500 internal Server Error is due to server down or network related problems.
    Import the wsdl in xmlspy or SOAPUI and see the behavior first. If the error is same, you can conclude it due to other end .(i meant server that host webservice causing it). we have very similar issues in our end. This is server down error mostly.
    Hope I answered your question.

  • CLIENT_SEND_FAILED 500 Timeout Error

    Hi Guys,
    i am getting below error in PI MONI, can any one please help me how to resolve this isuue.
    This interface is File to Proxy(ECC).
    <?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>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
      <SAP:P1>500</SAP:P1>
      <SAP:P2>Timeout</SAP:P2>
      <SAP:P3>(See attachment HTMLError for details)</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error while sending by HTTP (error code: 500 , error text: Timeout) (See attachment HTMLError for details)</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    Thanks,
    Siva.

    Hi,
         Is your scenario synchronous?
    Did you get a chance to look at below links:
    Re: CLIENT_SEND_FAILED for sync calls
    INTERNAL CLIENT_SEND_FAILED Internal Server Error 500 Error while sending b
    Regards,
    Naveen

  • PI Java Mapping NullPointerException

    Hi Gurus,
    I'm having some troubles doing the mapping through java mapping in PI.
    I've done the java class in the SAP NWDS and imported it on PI through the ESR.
    Now i'm trying to test through the SOAP and i've found the following error in the "Communication Channel Monitor":
    500   Internal Server Error  SAP NetWeaver Application Server/Java AS 
    java.lang.NullPointerException: while trying to invoke the method com.sap.aii.af.sdk.xi.lang.Binary.getBytes() of a null object returned from com.sap.aii.af.sdk.xi.mo.xmb.XMBPayload.getContent()
    And the following error in the SXMB_MONI:
    <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
      <SAP:P1>500</SAP:P1>
      <SAP:P2>Internal Server Error</SAP:P2>
      <SAP:P3>(See attachment HTMLError for details)</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error while sending by HTTP (error code: 500 , error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>
    I've developed the code below:
    public class PI_Mapping_IF extends AbstractTransformation {
      public void transform(TransformationInput in, TransformationOutput out)    throws StreamTransformationException  {  
      this.execute(in.getInputPayload().getInputStream(), out.getOutputPayload().getOutputStream()); 
      public void execute(InputStream in, OutputStream out)  throws StreamTransformationException { 
      try  
      // Inicio do java mapping
      getTrace().addInfo("JAVA Mapping Iniciado"); //Log para o PI/XI
      // Declarações referentes ao XML de entrada
      DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
      DocumentBuilder db = dbf.newDocumentBuilder();
      Document xml_in = db.parse(in);
      // Declarações referentes ao XML de saída
      Document xml_out = db.newDocument();
      TransformerFactory transformerFactory = TransformerFactory.newInstance();
      Transformer transformer = transformerFactory.newTransformer();
      // Remove o standalone
      xml_in.setXmlStandalone(true);
      // Declara a estrutura que a RFC irá receber
      Element root = xml_out.createElement("ns1:ZFSD_VMOI_UPLOAD_CF_PG");
      root.setAttribute("xmlns:ns1","urn:sap-com:document:sap:rfc:functions");
      xml_out.appendChild(root);
      Element i_cenario = xml_out.createElement("I_CENARIO");
      root.appendChild(i_cenario);
      Element t_input = xml_out.createElement("T_INPUT");
      root.appendChild(t_input);
      Element item = xml_out.createElement("ITEM");
      t_input.appendChild(item);
      Element STRING = xml_out.createElement("STRING");
      item.appendChild(STRING);
      Element t_return = xml_out.createElement("T_RETURN");
      root.appendChild(t_return);
      Element item_r = xml_out.createElement("ITEM");
      t_return.appendChild(item_r);
      Element message = xml_out.createElement("MESSAGE");
      item_r.appendChild(message);
      // Verifica se existe algum filho no nó
      NodeList nodos = xml_in.getChildNodes(); 
      if (nodos.item(0) != null)
      getTrace().addInfo("O nó(XML) possui filhos"); //Log para o PI/XI
      // Declaração de variáveis
      String ident = ""; // <Ident>
      String buyer = ""; // <BuyerLineItemNum>
      String result = ""; // <Ident>;<BuyerLineItemNum>;<Date>;<QuantityValue>
      // Inicia a extração das informações do XML
      try{
      // Recupera o nó ShipToParty
      NodeList nodeShip = xml_in.getElementsByTagName("ns0:ShipToParty");
      Node node = nodeShip.item(0);
      Element elemXML = (Element) node;
      try{
      NodeList nodeIdent = elemXML.getElementsByTagName("ns0:Ident");
      Element nameElement = (Element) nodeIdent.item(0);
      nodeIdent = nameElement.getChildNodes();
      // Recupera o valor da chave <Ident>
      ident = PI_Mapping_IF.VerifyNull(((Node) nodeIdent.item(0)).getNodeValue());
      }catch(Exception e){
      result += "0.0;";
      // Recupera o nó ListOfMaterialGroupedPlanningDetail
      NodeList nodeBuyer  = xml_in.getElementsByTagName("ns0:MaterialGroupedPlanningDetail");
      for (int i = 0; i < nodeBuyer.getLength(); i++) {
      node = nodeBuyer.item(i);
      elemXML = (Element) node;
      try{
      // Preenche a chave BuyerLineItemNum
      NodeList nodeBuyerLine = elemXML.getElementsByTagName("ns0:BuyerLineItemNum");
      Element elemBuyerLine = (Element) nodeBuyerLine.item(0);
      nodeBuyerLine = elemBuyerLine.getChildNodes();
      buyer = PI_Mapping_IF.VerifyNull(((Node) nodeBuyerLine.item(0)).getNodeValue());
      }catch(Exception e){
      buyer += "0;";
      result = ident+";"+buyer+";";
      Node nodeDt_Qnt = nodeBuyer.item(i);
      Element elemDt_Qnt = (Element)nodeDt_Qnt;
      NodeList nodeValores = elemDt_Qnt.getElementsByTagName("ns0:ScheduleDetail");
      for (int j = 0; j < nodeValores.getLength(); j++) {
      node = nodeValores.item(j);
      elemXML = (Element) node;
      try{
      // Preenche a chave Date
      NodeList modelExtra = elemXML.getElementsByTagName("ns0:Date");
      Element extraElement = (Element) modelExtra.item(0);
      modelExtra = extraElement.getChildNodes();
      result += PI_Mapping_IF.VerifyNull(((Node) modelExtra.item(0)).getNodeValue())+";";
      }catch(Exception e){
      result += "//;";
      try {
      // Preenche a chave QuantityValue
      NodeList modelURL = elemXML.getElementsByTagName("ns0:QuantityValue");
      Element urlElement = (Element) modelURL.item(0);
      modelURL = urlElement.getChildNodes();
      result += PI_Mapping_IF.VerifyNull(((Node) modelURL.item(0)).getNodeValue())+";";
      } catch (Exception e) {
      result += "0.0;";
      // Marca o final do registro
      result += "||";
      // Preenche os nós itens
      Text srcxml = xml_out.createTextNode(result);
      STRING.appendChild(srcxml);
      result = "";
      buyer = "";
      }catch(Exception e){
      // Remove o standalone
      xml_out.setXmlStandalone(true);
      // Preenche o Cenario
      Text cenario = xml_out.createTextNode("P&G");
      i_cenario.appendChild(cenario);
      // Preenche mensagem de retorno
      Text msgxml = xml_out.createTextNode("XML lido com sucesso!");
      message.appendChild(msgxml);
      // Escreve a saida do XML            
      transformer.transform(new DOMSource(xml_out), new StreamResult(out));
      getTrace().addInfo("Fim da execução do Java Mapping");
      } catch (ParserConfigurationException e) {
      getTrace().addWarning(e.getMessage());
      throw new StreamTransformationException("Can not create DocumentBuilder.", e);
      } catch (SAXException e) {
      e.printStackTrace();
      } catch (IOException e) {
      e.printStackTrace();
      } catch (TransformerConfigurationException e) {
      e.printStackTrace();
      } catch (TransformerException e) {
      e.printStackTrace();
    Am i doing anything wrong in the code? Where can this nullpointerexception be triggered?
    Thanks.

    These three xml are the same:
    <?xml version="1.0"?><a:xml xmlns:a="urn:123">root</a:xml>
    <?xml version="1.0"?><xml xmlns="urn:123">root</xml>
    <?xml version="1.0"?><ns0:xml xmlns:ns0="urn:123">root</ns0:xml>
    But your code will work only with last one, because it doesn't bound namespace to prefix ns0.

  • IDOC stuck in PI with Loop error ( R/3 - PI - SCM SNC scenario)

    Hi,
      I am sending a PO as an IDOC from R/3 to SNC, the receiver side configuration was made with XI adapter with HTTP protocol. I am getting the IDOC received in PI but with below error. Any help is highly appreciated.
    Aso I am not sure if the receiver communication channel should be XI server host and url or SNC host.
    <?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>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">LOOP_IN_MESSAGE_ROUTING</SAP:Code>
      <SAP:P1>is.23.saptest1</SAP:P1>
      <SAP:P2>CENTRAL</SAP:P2>
      <SAP:P3>XI</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText>Loop in message flow found: system is.23.saptest1, pipeline CENTRAL with inbound adapter XI already processed (see hoplist header)</SAP:AdditionalText>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Thanks,
    Menaga

    Every one thanks for your reply, first I tried changing my communication channel parameters which I had the PI host name and port and now I changed to SCM host name and port with path prefix /sap/xi/engine/?type=entry...I got the below error.
    <?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>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
      <SAP:P1>404</SAP:P1>
      <SAP:P2>Not Found</SAP:P2>
      <SAP:P3>(See attachment HTMLError for details)</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error while sending by HTTP (error code: 404, error text: Not Found) (See attachment HTMLError for details)</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    Thanks,
    Menaga

  • SQL to XI Scenario (message delivery problem)

    Hi All
    Scenario is:
    Sender Communication Channel is polling data from SQL.
    From SQL around 2,75,000 records need to be picked up.
    Communication Channel has successfully picked up data.
    When i see communication channel monitoring getting an error
    "Transmitting the message to endpoint http://hkbxiprd:8000/sap/xi/engine?type=entry using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server."
    What is this error and how to sove it.
    As XI sender channel already picked up data so flag in SQL side is also updated so cant try to pick up data again from SQL. All the records got stuck in adapter engine.
    I also tried to resend the message but still getting the same Error Message.
    Please suggest what can be done.
    Regards
    Dheeraj Kumar

    Hi All
    Now i have set icm/HTTP/max_request_size_KB = 2097152
    Sender communication channel successfully picked up records and sent to Integration Engine.
    Now the problem is now it got stucked into smq2.
    When i am checking my moni it is showing message in automatic restart.
    inside error it is showing
    <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2>HTTPIO_PLG_CANCELED-Fehlermeldung beim Senden der Daten.</SAP:P2>
    What i can do next please suggest
    Regards
    Dheeraj Kumar

  • File to Proxy Scenario Error

    Hi Experts,
    I am working on File To Proxy Scenario. I am getting the below Error: The Messages in SXMB_MONI are going to AUtomatically Restart Status. I see some Queues with RETRY Status in SMQ2. When i am testing from SPROXY, the Table is Updated with the Corresponding Values. But when i place the file in the ftp folder then i am getting this error.
    <?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>XIServer</SAP:Category>  
    <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>  
    <SAP:P1>500</SAP:P1>  
    <SAP:P2>Internal Server Error</SAP:P2>  
    <SAP:P3>(See attachment HTMLError for details)</SAP:P3>  
    <SAP:P4 />  
    <SAP:AdditionalText />  
    <SAP:Stack>Error while sending by HTTP (error code: 500, error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>  
    <SAP:Retry>A</SAP:Retry>  
    </SAP:Error>
    Please check and do the needful .
    Regards,
    GIRIDHAR

    Hi Giridhar,
    The problem is with connection. Please check the below discussion
    HTTP returns status is 500(Internal Server Error)
    Problem in ABAP proxy........ | SCN
    regards,
    Harish

  • HTTP 500 Internal Server Error in SXMB_MONI

    Hello,
    Getting HTTP 500 Internal Server Error while running some Synchronous Scenario of ECC -> PI -> Legacy system (SOAP adapter). Following are the errors received in SXMB_MONI.
    <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.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error</SAP:AdditionalText>
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
      <SAP:P1>500</SAP:P1>
      <SAP:P2>Internal Server Error</SAP:P2>
      <SAP:P3>(See attachment HTMLError for details)</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error while sending by HTTP (error code: 500 , error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Both the errors are not regular but comes up every now and than. If the scenario is re-run from ECC than it works.
    Please advise.
    Thanks a lot

    Thanks a lot Nidhi. I am looking at the notes provided.
    Thanks a lot Lars. Please find the content of HTML content:
    java.lang.ClassCastException: class com.sap.engine.interfaces.messaging.spi.transport.TransportHeaders:interface:com.sap.aii.af.ms.ifc9(at the rate)com.sap.engine.boot.loader.ResourceMultiParentClassLoader(at the rate)6f9702b1(at the rate)alive incompatible with class com.sap.engine.interfaces.messaging.spi.transport.HTTPHeaders:interface:com.sap.aii.af.ms.ifc(at the rate)[email protected]1(at the rate)alive
         at com.sap.engine.messaging.impl.core.transport.http.MessagingServlet.doPost(MessagingServlet.java:447)
         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:162)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
         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:73)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:461)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
         at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         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:78)
         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:78)
         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:78)
         at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
         at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Regards

  • Queue stopped in sxmb_moni

    Hi,
    I am getting the problem in sxmb_moni when the XML message goes from one integration process to  SOAP adapter and a mapping is called.The queue status is Queue Stopped. When i click on that queue it shows status as SYSFAIL.When i double click on that queue again it shows Status Text
    as "XI Error CLIENT_SEND_FAIL . INTERNAL :Queue Stoppe ".
    And the trace for that message is
       <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Message Split According to Receiver List
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
      <SAP:P1>35</SAP:P1>
      <SAP:P2>HTTPIO_ERROR_CUSTOM_MYSAPSSO-Fehlermeldung beim Senden der Daten.</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error while sending by HTTP (error code: 35, error text: HTTPIO_ERROR_CUSTOM_MYSAPSSO-Fehlermeldung beim Senden der Daten.)</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    Please help me with this issue...

    Queue Stopped
    For your message processing in sxmb_moni...in the Qstatus column you will be seeing a red circle with stop written in it...
    ->double click it
    ->it will show you status of the Q....number of messages in the Q...
    -> double-click on the number of entries
    -> you will see a detailed report
    -> double click on the first entry
    -> you will see the message processing due to which the Q got blocked
    -> on the toolbar above (in the same page) you will find the option of Restart...click it....select the tracing level as retain....
    this will cause the message processing to restart and all the messages blocked in the Q will get processed....
    Regards,
    Abhishek.

  • Proxy connection error sending big files

    Hello experts,
    I am sending a simple proxy to PI in order to generate an XML.
    When the XML that I get is less than 100MB big, it works fine and the XML gets generated.
    On the other hand, when I try to generate a file anything bigger, I get the following error.
    - <SAP:Error
    SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SAP:Category>XIServer</SAP:Category>
    <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
    <SAP:P1>400</SAP:P1>
    <SAP:P2>Bad Request</SAP:P2>
    <SAP:P3>(See attachment HTMLError for details)</SAP:P3>
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:Stack>Error while sending by HTTP (error code: 400 , error text: Bad Request)
    (See attachment HTMLError for details)</SAP:Stack>
    <SAP:Retry>A</SAP:Retry>
    </SAP:Error>
    It seams a communication error, but the proxy is retried and we always get the same error.
    Any ideas?
    Thanks a lot!

    Hello Maria,
    In ICM configuration, please check the value of the parameter icm/HTTP/max_request_size_KB. By default, it is 102400 - meaning that ICM will process HTTP requests of size up to 100 MB and will prevent processing larger requests. You can increase value of this parameter to a higher value depending on the size of HTTP requests that you expect to be passed to ICM. In extreme case, this limitation can be even switched off by setting value of the mentioned parameter to -1, but please take into consideration that switching off the request size limitation is not recommended from security perspective - since potentially very large requests may be sent to ICM and cause performance degradation / Denial of Service for ICM when being processed.
    Regards,
    Vadim

  • PI Web Service Scenario

    Hi experts!!!!
    I try to learn PI Web Service Scenario, and for test, i developed a simple scenario.
    I created a Service Message Synchron Outbound Message with Request and Response Structure, and I created a Service Message Synchron Inbound with Request and Response web service message (previouse imported on External Definition).
    I developed 2 mappings, one for Requeste ( MyMessageReq ---> Web Service Request) and other one for Response  (Web Service Response --> MyMessageResponse). and add this on Operation Mapping.
    In Directory, i created 2 Business Components (WS_Sender and WS_Receiver).and add my objects.
    For Receiver Communication channel i user adapter type like WS. and configured this like help.sap.
    When i executed the interface, the communication channel returns the following error:
    <!--  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>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">WS_ADAPTER_SYS_ERROR</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Systemfehler beim Aufruf des Web-Service-Adapters: Error al acceder a WSDL: &quot;Error in WSDL access for task ID &quot;00000000000000000007&quot;; read the long text&quot;</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I don't know the reason of this error, and i don't found anything on forum...
    Please, could somebody help me? Could somebody have any idea? Thanks.
    Gemma.

    Thanks.
    Now I use a communication channel soap receiver, and when i try to execute the interface, the call adapter returns the following error:
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
      <SAP:P1>35</SAP:P1>
      <SAP:P2>HTTPIO_ERROR_CUSTOM_MYSAPSSO-Fehlermeldung beim Senden der Daten.</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Fehler beim Senden per HTTP (Fehlercode: 35, Fehlertext: HTTPIO_ERROR_CUSTOM_MYSAPSSO-Fehlermeldung beim Senden der Daten.)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Please, could somebody help me? Thanks.

  • UNCAUGHT_EXCEPTION in SOAP TO PROXY scenario dump in ECC system.

    Hi Experts,
    My scenario is saop to proxy .while performing testing the scenario using saopui.  iam getting client_send_failed error in sxmb_moni.
    but data processed to ecc system and updated the data in database level and giving dump in ecc system.
    i am getting dump like below.
    UNCAUGHT_EXCEPTION.
    we increased the size of  instance profile parameters also upto 500 mb .in rz10.
    still getting dump.
    Please give the solution for  above.
    Regards
    Ravinder.s

    Hi All,
    We resolved the issue using below notes and my system is newly upgraded  its not accepting asynchronous scenarios with quality of service as  BE in sender communication channel.
    1966422 - XI runtime: Dump: synchronous proxy calls asynchronous interface
    Thanks for all.

  • Error at Call Adapter stage

    Hi.
    We are experiencing an error at the 'Call Adapter' stage of the pipeline. It seems as if the message is unable to move from the integration engine to the adapter engine with this error -
    <?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>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
      <SAP:P1>500</SAP:P1>
      <SAP:P2>Internal Server Error</SAP:P2>
      <SAP:P3>(See attachment HTMLError for details)</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error while sending by HTTP (error code: 500, error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    The HTML dump says u2013
    java.lang.NullPointerException:
            at com.sap.engine.interfaces.messaging.spi.transport.TransportHeaders.setHeader(TransportHeaders.java:169)
            at com.sap.aii.adapter.xi.ms.XIMessage.prepareToReceive(XIMessage.java:1437)
            at com.sap.aii.adapter.xi.ms.XIMessage.prepareToReceive(XIMessage.java:1122)
            at com.sap.aii.adapter.xi.ms.XIEventHandler.onRequest(XIEventHandler.java:791)
            at com.sap.engine.messaging.impl.spi.ServerConnectionImpl.request(ServerConnectionImpl.java:237)
            at com.sap.engine.messaging.impl.core.transport.http.MessagingServlet.doPost(MessagingServlet.java:417)
            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)
    This occurred after an SLD update. Does anyone know how to fix this issue?
    Thanks
    Regards
    Riaz

    Hi guys
    1. Sender - Backend ERP (ECC) calling enterprise service, Receiver - SOAP Web service. Both are business systems internal to the network
    2. Both sender and receiver are Business systems which are registered in the SLD.
    3. This interface was previously working, until the LSD was updated, then it began.
    4. PI 7.10
    5. All the scenarios which use this type of communication (Proxy to SOAP) are failing at the same stage
    I have also logged an OSS call with SAP and they are currently looking at the issue.
    Regards
    Riaz

Maybe you are looking for

  • How to delete a record in the target?

    Hi all, In my source i'm having three tables which are joined.My source and target is oracle. I'm using IKM incremental update oracle.For SCD-1.If i delete a record in any of my source tables i cannot able to delete that particular record in the targ

  • Installing new HDD after Windows XP to Windows 7 upgrade on my T400

    A few weeks ago I did a clean install to upgrade my T400 laptop from Windows XP to Windows 7 Professional, using the upgrade version of Windows 7 (vs. the complete new installation version - saved about $100.00). Now I want to upgrade my HDD from 250

  • Aperture 3 import of old library

    After spending 3 hours on the import of the Aperture 2 library (you can't convert in the trial, and there was no upgrade download option online so I ordered the disc) I discovered that it had not imported any folders within projects. Is this normal?

  • No AppleScript in Numbers?

    Am I missing AppleScript support somewhere?

  • CS4 close to unusable

    Hello everyone, like others, I've already spent hours on the web looking for solutions, yet without success. PS CS4 has numerous issues on my machine: 1. Canvas doesnt refresh (unless I switch tools) The frequency varies, but it happens very, very of