Exceptions From Inbound Transport Callout Are Not Sent To Exception Queue (Doc ID 1929734.1)

Last updated on NOVEMBER 03, 2016

Applies to:

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

Symptoms

On : 11.1.1.7.0 version, B2B Engine

ACTUAL BEHAVIOR
---------------
Exception messages generated by inbound callout's are not being send to the configured 'Exception Queue' in B2B.

 

The following exception is seen in the 'soa_server_diagnostic.log' for example ;

 

[2014-07-03T13:35:32.952+01:00] [AdminServer] [ERROR] [] 
[oracle.soa.b2b.engine] [tid: 
weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@15b832b] [userId: 
<anonymous>] [ecid: 0000KRwD8cW62VjpL0WBye1JhKnc000001,0] [APP: soa-infra] 
Error -:  B2B-50029:  B2B runtime error[[ 
at 
oracle.tip.b2b.callout.B2BCalloutHandler.invokeTransportCallout(B2BCalloutHand 
ler.java:816) 
at 
oracle.tip.b2b.callout.B2BCalloutHandler.handleTransportCallout(B2BCalloutHand 
ler.java:583) 
at oracle.tip.b2b.utility.Utility.processCallout(Utility.java:4920) 

All exceptions message should be routed to the exception queue if this is configured in the B2B console.

All other exception messages other then callout exceptions are making it to the queue in weblogic.



Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms