My Oracle Support Banner

Cannot catch the Fault thrown by Oracle Service Bus (OSB) 11g when using SOA-DIRECT Binding (Doc ID 1266475.1)

Last updated on AUGUST 30, 2019

Applies to:

Oracle SOA Suite - Version 11.1.1.3.0 and later
Information in this document applies to any platform.

Purpose

This document intends to explain some aspects of  the transactional behavior in interactions between SOA Suite components and Oracle Service Bus 11g when using direct binding (SOA_DIRECT Transport).

Scope

This document is addressed to service designers and developers, who are designing composite applications interacting with Oracle Service Bus 11g and they consider to leverage the transactional and security capabilities of direct binding.

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details
 Problem
 Resolution Information and scope
 (1)  What are the transaction boundaries in interactions between BPEL components and Oracle Service Bus Proxy services when direct binding is used?
 (2) How faults thrown by Oracle Service Bus direct binding are treated by the BPEL components?
 (3) What recovery mechanisms can be used?
 (4) Are there any properties, that can be used to influence that behavior?
 (5) Why 'java.lang.ClassCastException Exception is seen in the logs?
 (6) Are there any patches available?
 
 
 
 Summary
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.