Service Holding Values In Otd

(Doc ID 1359428.1)

Last updated on JANUARY 26, 2018

Applies to:

Oracle Java CAPS Enterprise Service Bus - Version: R6 U1 and later   [Release: 6.0 and later ]
Information in this document applies to any platform.
Checked for relevance on 20-SEP-2011


The inbound OTD field retains the old value during the unmarshal of next input message, after unmarshaling the first round of input message. This particular field doesn't contain any value in the second and subsequent incoming messages, but it still retains the old value from the first input message and unmarshals it into the outbound otd field.


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