In the Doc ID given solution below:
To implement the solution, please execute the following steps:
2. Ensure that you have taken a backup of your system before applying the recommended patch.
3. Apply the patch in a test environment.
4. Retest the issue.
5. Migrate the solution as appropriate to other environments.
Could you please suggest the solution over here..
If your failure scenario is like below :
i)facing issue when invoking OSB service from BPEL which must act like one way but it does wait for response and behaves like sync call.
If that is the case , there is a bug which requires patches to be applied to env.
Error message which you are getting and the one mentioned in DocId seems to be similar kind of issue.
Analyse the DocId , go through the read me file and apply patches if necessary.
BPEL THROWS ENDPOINT PARSING EXCEPTION WHILE CALLING WEB SERVICE BASED OSB PROXY
Try invoking a web service based proxy service from BPEL and it fails with the following error:
Unable to invoke endpoint URI "..." 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.