Bad Handling Of Indefinite Form Of Camel Field Length
Last updated on OCTOBER 10, 2016
Applies to:Oracle Communications Service Broker - Version 3.1.0 to 3.1.0 [Release 3.1.0]
Information in this document applies to any platform.
OCSB is not properly handing the case where the camel message includes an indefinite field length octet:
30  [SEQUENCE] InitialDPArg
The hexa 80 indicates the indefinite field length.
The following exceptions were generated in the PN node:
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