1 Reply Latest reply on Jan 5, 2018 2:32 PM by AnatoliAtanasov

    What could be the reasons for response structure change when we call an OSB proxy service that is down from SOA 12c

    Sravani Gajula

      Hi All,

      I would like to know why there will a response structure change when we call an OSB proxy service(which is down) from SOA 12c.

      What could be the reasons for the change in structure.

      Here are the two different response structures that are changing time to time: [one of below structures has SOAP structure]

      <remoteFault xmlns="http://schemas.oracle.com/bpel/extension">

      -<part name="summary">

      <summary>

      oracle.fabric.common.FabricException: oracle.fabric.common.FabricException: Error in getting XML input stream: http://...?wsdl: Response: '404: Not Found' for url: 'http://...?wsdl': Error in getting XML input stream: http://...?wsdl: Response: '404: Not Found' for url: 'http://...?wsdl'

      </summary>

      </part>

      -<part name="detail">

      <detail>

      Response: '404: Not Found' for url: 'http://.....?wsdl'

      </detail>

      </part>

      </remoteFault>

      --------------------------------------------------------------------------------------------------------------------------------------------------------------------------

      <remoteFault xmlns="http://schemas.oracle.com/bpel/extension">

      -<part name="summary">

      <summary>

      oracle.fabric.common.FabricInvocationException: Unable to invoke endpoint URI "http://..." successfully due to: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Bad response: 404 Not Found from url http://..

      ===== reqeust ========

      SOAPAction:"FetchParameterNum"

      Content-Type:text/xml; charset=UTF-8

      Content-Length:2112

      <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing"><env:Header>

      <wsa:To>http://..</wsa:To>

      <wsa:Action>FetchParameterNum</wsa:Action>

      <wsa:MessageID>urn:b47e63eb-e3e4-11e7-af73-005056937c77</wsa:MessageID>

      <wsa:RelatesTo>urn:b47e63eb-e3e4-11e7-af73-005056937c77</wsa:RelatesTo><wsa:ReplyTo><wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>

      <wsa:ReferenceParameters><instra:tracking.ecid xmlns:instra="http://xmlns.oracle.com/sca/tracking/1.0">e11a0fd6-0491-4689-831c-6f3a9c106290-00003923</instra:tracking.ecid><instra:tracking.conversationId xmlns:instra="http://xmlns.oracle.com/sca/tracking/1.0">urn:b47e63eb-e3e4-11e7-af73-005056937c77</instra:tracking.conversationId><instra:tracking.parentComponentInstanceId xmlns:instra="http://xmlns.oracle.com/sca/tracking/1.0">bpel:1502768</instra:tracking.parentComponentInstanceId><instra:tracking.parentReferenceId xmlns:instra="http://xmlns.oracle.com/sca/tracking/1.0">1502768-BpInv0-BpSeq3.6-2</instra:tracking.parentReferenceId><instra:tracking.FlowEventId xmlns:instra="http://xmlns.oracle.com/sca/tracking/1.0">4347477</instra:tracking.FlowEventId><instra:tracking.FlowId xmlns:instra="http://xmlns.oracle.com/sca/tracking/1.0">610159</instra:tracking.FlowId><instra:tracking.CorrelationFlowId xmlns:instra="http://xmlns.oracle.com/sca/tracking/1.0">0000M1dLQ6O2zGC5JFCCyf1Q7HRV00002r</instra:tracking.CorrelationFlowId><instra:tracking.quiescing.SCAEntityId xmlns:instra="http://xmlns.oracle.com/sca/tracking/1.0">380022</instra:tracking.quiescing.SCAEntityId></wsa:ReferenceParameters></wsa:ReplyTo><wsa:FaultTo><wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address></wsa:FaultTo></env:Header>

      <env:Body>

      <Request xmlns="http://..">

      <PRequest>

      <PI_N>N</PI_N>

      <PI_C></PI_C>

      <PI_F>B</PI_F>

      </PRequest>

      </Request>

      </env:Body>

      </env:Envelope>

      </summary>

      </part>

      -<part name="code">

      <code>404</code>

      </part>

      -<part name="detail">

      <detail>

      Unable to invoke endpoint URI "http://..." successfully due to: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Bad response: 404 Not Found from url http://..

      </part>

      </remoteFault>

      Thanks & Regards,

      Sravani.

        • 1. Re: What could be the reasons for response structure change when we call an OSB proxy service that is down from SOA 12c
          AnatoliAtanasov

          Hi Sravani,

           

          The faults you have pasted reflect two different scenarios:

          - In the first one the SOA infra is trying to download the WSDL for your reference binding component. Most probably ether in composite.xml or in some other WSDL you have URL pointing to the remove service's WSDL. This might be after you use configuration plan when you have deployed your composite. This should be the very first error when you invoke the composite service component.

          - The second one tries to post the SOAP payload to the remote server hosting your service. Posting to that URL causes the "javax.xml.soap.SOAPException: Bad response: 404 Not Found from url".

           

          If you still have the concrete WSDL in your project may SOA starts to use it instead of downloading it from the remote server due to the first error. That WSDL may hold a service endpoint pointing to the address in your second fault.

           

          Hope I made myself clear!

           

          Cheers,

          A.