Hi,
Present we are migrating SOA 11.1.1.6.0 version to 12.2.1.2 version. One of the interface facing one issue i.e., on runtime while trying to invoke OSB proxy throwing below error:
*However we have not touch the Business Logic inside the code, only updating JMS Adapter to SOAP Adapter configuration i.e., where JMS Produce in a Queue happening in SCA and in same Queue Consuming in OSB updating to WSDL based.
SOAP Error:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header><tracking:faultId xmlns:tracking="http://oracle.soa.tracking.core.TrackingProperty">20004</tracking:faultId></env:Header>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode><faultstring>oracle.fabric.common.FabricInvocationException: Unable to invoke endpoint URI "http://localhost:7003/Helloworld/HelloWorld_OSB/ProxyService/HTTP_SOAP" successfully due to: javax.xml.soap.SOAPException: Error parsing envelope: most likely due to an invalid SOAP message.: Strange I/O stream, returned 0 bytes on read</faultstring>
<faultactor/>
<detail><exception>Unable to invoke endpoint URI "http://localhost:7003/Helloworld/HelloWorld_OSB/ProxyService/HTTP_SOAP" successfully due to: javax.xml.soap.SOAPException: Error parsing envelope: most likely due to an invalid SOAP message.: Strange I/O stream, returned 0 bytes on read</exception></detail>
</env:Fault>
</env:Body>
</env:Envelope>
After above error, tried to change OSB proxy ServiceType as 'Any Soap Service (SOAP 1.1)', got different error below:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header>
<tracking:faultId xmlns:tracking="http://oracle.soa.tracking.core.TrackingProperty">33251</tracking:faultId>
</env:Header>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>OSB-380001: Internal Server Error</faultstring>
<faultactor/>
<detail>
<exception>
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>OSB-380001</con:errorCode>
<con:reason>Internal Server Error</con:reason>
<con:location>
<con:node>RouteTo_HelloWorld</con:node>
<con:path>response-pipeline</con:path>
</con:location>
</con:fault></exception>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
Could any one help over here please. Facing this issue from 5 days. After tried different ways finally posted in Community. So, please help me.
-----
Thanks..