e*Gate Migrated ETD does not throw unmarshall failure at runtime when running in SOA Server. (Doc ID 1631938.1)

Last updated on MARCH 04, 2014

Applies to:

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

Goal

On : 11.1.1.7.0 version, SOA Suite Migration Tool

ACTUAL BEHAVIOR
---------------
Migrated ETD does not throw exception on unmarshall failure

In eGate 4.5.3, if an ETD encounters an unmarshall failure, an exception is thrown and the message is rolled back to the queue and retried.

However when a eGate 4.5.3 ETD is migrated over to SOA Suite, if a bad message is sent, the ETD fails to unmarshall correctly, but doesn't throw an exception and the message disappears.

EXPECTED BEHAVIOR
-----------------------
Expectation is for the ETD in SOA Suite to behave the same way it did in eGate versions, and throw an exception when unmarshall fails.

Is there any Patch or Fix for this issue.
 

Solution

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