ADT Payload Size Indicates Increasing Size in BPEL Logfile For Separate BPEL Instances Using Inbound AQ Adapter

(Doc ID 1313818.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle SOA Platform - Version: 10.1.3.5.0 and later   [Release: and later ]
Information in this document applies to any platform.

Symptoms

Dequeuing AQ messages using an AQ adapter from the same queue in separate BPEL instances results in the logfile showing an additive increase in message size of for each message being dequeued, though each message is the same size.

Since each message is discrete each logger message should show the same payload size and not an additive display of x bytes + x bytes for each subsequent message. This problem has been seen on 10.1.3.5 MLR #1 (<>).

The additive increase in the ADT payload size can be seen in the BPEL container lofile in $ORACLE_HOME/opmn/logs/<BPEL Container>.log:

<2011-02-16 19:11:11,999> <INFO> <default.collaxa.cube.activation> <AQ Adapter::Inbound> ADT Payload size = 8
<2011-02-16 19:11:12,112> <INFO> <default.collaxa.cube.activation> <AQ Adapter::Inbound> ADT Payload size = 16
<2011-02-16 19:11:13,041> <INFO> <default.collaxa.cube.activation> <AQ Adapter::Inbound> ADT Payload size = 24
<2011-02-16 19:11:13,324> <INFO> <default.collaxa.cube.activation> <AQ Adapter::Inbound> ADT Payload size = 32
<2011-02-16 19:11:13,638> <INFO> <default.collaxa.cube.activation> <AQ Adapter::Inbound> ADT Payload size = 40
<2011-02-16 19:11:13,671> <INFO> <default.collaxa.cube.activation> <AQ Adapter::Inbound> ADT Payload size = 48
<2011-02-16 19:11:13,715> <INFO> <default.collaxa.cube.activation> <AQ Adapter::Inbound> ADT Payload size = 56
<2011-02-16 19:11:13,741> <INFO> <default.collaxa.cube.activation> <AQ Adapter::Inbound> ADT Payload size = 64
<2011-02-16 19:11:13,776> <INFO> <default.collaxa.cube.activation> <AQ Adapter::Inbound> ADT Payload size = 72
<2011-02-16 19:11:13,993> <INFO> <default.collaxa.cube.activation> <AQ Adapter::Inbound> ADT Payload size = 80
<2011-02-16 19:11:14,067> <INFO> <default.collaxa.cube.activation> <AQ Adapter::Inbound> ADT Payload size = 88

In this case each message is 8 bytes in size, but each log message shows each message increasing in size by 8 bytes.

Cause

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