Oracle SOA B2B : Sending Signed Ack Through Oracle HTTP Server (OHS) Results In ORA-24816
Last updated on OCTOBER 10, 2016
Applies to:Oracle B2B (Business to Business) - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : 184.108.40.206.0 version, Core B2B Platform
Oracle SOA B2B : Sending signed Ack through OHS results in ORA-24816
Sending signed Ack through OHS results in ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column with an 856 payload that generates a long error message.
You have an EDI payload that contains control-M characters. Initially this was giving a document protocol error, but have set the B2B parameter edi.enablePreprocess to True. This has resolved the document protocol error but now finding ORA-24816 errors in the log and the message is not showing in B2BConsole. (This fails on insert in wire message table due to the ORA-24816 error, and does not show in b2bconsole)
When configuring the AS2 channel to send a signed Ack, you get an ORA-24816 error. This is only going through OHS, and when Ack mode is set to Sync.
If you use the same configuration and same document, and go directly to Weblogic, the message processes as expected.
If you going through (vanilla) OHS, and set Ack mode to Async, message processes as expected. However, synch mode and OHS are required.
You also found that if you unchecked Ack Signed, this also works through OHS.
Steps to reproduce
The issue can be reproduced at will with the following steps:
- Configure Partner Agreement with Synchronous Acknowledgement
- Enable OHS
- Notice error when synch Ack and OHS are enabled
The issue has the following business impact: EDI document exchanges must be possible with OHS and synch Ack enabled.
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