Skip to Main Content

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Reply with Failure in OSB 11.1.1.6 and 11.1.1.7

Prasanna GApr 17 2014 — edited Apr 21 2014

Hi,

We have recently migrated from weblogic 11.1.1.6 to 11.1.1.7 version and I do see some issues/changes in the way my code worked.

Scenario:

a. There is a BPEL composite - A, which invokes a synchronous OSB SOAP service B.

b. OSB service B in turn calls an external application and gives some response back.

c. If the external application is down or returned an error, we caught the error in error handler block of OSB, captured the error in a different xml(my output variable O1, not the fault variable F1), populated the body with this new xml and did a Reply with Failure.

The way it worked in 11.1.1.6:

a. Although a Reply with Failure was done from OSB, my BPEL received the error as a success response(not a partner link fault) with error message populated. The response had O1 message returned as success response with error populated.

The way it is working in 11.1.1.7:


a. A Reply with Failure done from OSB is erroring out my invoke(partner link error) in the calling BPEL. But the fault is not the actual fault returned by external application. It is the following one.

<detail>Unable to invoke endpoint URI "http://localhost:8080/test/status" successfully due to: Could not determine soap fault from message oracle.j2ee.ws.saaj.soap.soap11.Message11@1825a422</detail>

I modified the code in 11.1.1.7 to populate the body with Fault Variable F1, instead of output variable O1. Now my BPEL again gets partnerlink error, but the error message has the fault variable populated.


Why is there a difference in behavior in both 11.1.1.6 and 11.1.1.7? Is this a fix done in 11.1.1.7?

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on May 19 2014
Added on Apr 17 2014
2 comments
2,876 views