Tuxedo FML32 Buffer Gets Cleared Or Corrupted If Service Call Fails
(Doc ID 2177927.1)
Last updated on NOVEMBER 08, 2018
Applies to:Oracle Tuxedo - Version 12.1.3 and later
Information in this document applies to any platform.
Oracle Tuxedo Version 18.104.22.168.0, 64-bit, Rolling Patch Level 056,(Issue is not happening in lower rolling patch levels of same release version)
The Tuxedo FML32 buffer sent gets cleared or corrupted if the service call failed with get error:LIBFML_CAT:4: ERROR: Field not present
ULOG's below error, with TMTRACE turned on, can be found when a non existing service is getting called after an existing service and then the filled FML32 buffer gets cleared.
The clearing of the FML32 buffer happens only after the call of the valid service, following by "invalid" service.
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