RP/TUX Abnormal Increase Of Message Size Used In Tuxedo /Q Queues (Doc ID 1960053.1)

Last updated on MAY 01, 2017

Applies to:

Oracle Tuxedo - Version 12.1.1 to 12.1.1 [Release 12c]
Information in this document applies to any platform.

Symptoms

 When forwarding the message from Tuxedo queue space on disk to another Tuxedo queue space, the message size is different.

And when sending this message to another service(for example using Weblogic Tuxedo Connector, also known as WTC) This causes strange behavior such as TPETIME and lost WTC connection.

Reproducing scenario:

1. Original queue in original queue space (4GB) with 3 messages as reported by qlist in qmadmin:

Msgid BUduRZAAAAAVAAAAAAAAAAAAAAAAAV=, priority 50, retrycnt 0, msglen 567816
 Delivery qos: persistent,      Reply qos: default
Msgid BUduRZAAAAAWAAAAAAAAAAAAAAAAAW=, priority 50, retrycnt 0, msglen 596084
 Delivery qos: persistent,      Reply qos: default
Msgid BUduRZAAAAAXAAAAAAAAAAAAAAAAAX=, priority 50, retrycnt 0, msglen 3403384
 Delivery qos: persistent,      Reply qos: default

2. Forwarding the messages to new tiny unused Tuxedo queue space (10MB) using own developed qforward .

3. New Tuxedo queue in the new Tuxedo queue space as reported by qlist command from the Tuxedo qmadmin utility:

Msgid BUdz15AAAAAEAAAAAAAAAAAAAAAAAE=, priority 50, retrycnt 0, msglen 567816
Delivery qos: persistent,      Reply qos: default
Msgid BUdz15AAAAAFAAAAAAAAAAAAAAAAAF=, priority 50, retrycnt 0, msglen 596084
 Delivery qos: persistent,      Reply qos: default
Msgid BUdz15AAAAAGAAAAAAAAAAAAAAAAAG=, priority 50, retrycnt 0, msglen 3970484
 Delivery qos: persistent,      Reply qos: default

The third message size is different from original queue space. (3403384  versus 3970484)

Changes

 

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