My Oracle Support Banner

GlassFish Message Queue JDBC Transaction Table Count Increase With Load (Doc ID 1368063.1)

Last updated on JULY 06, 2020

Applies to:

Sun Java System Message Queue - Version 4.4u2 and later
Oracle GlassFish Server - Version 2.1.1 and later
Information in this document applies to any platform.

Symptoms

NOTE: Names; eg MQ41Txn, MQ41TXN etc other used represent fictitious names are made up as examples.
Any similarity to actual code, is purely coincidental and not intended in any other manner.

=============

On GlassFish Message Queue (MQ) (versions MQ4.4u2P4/MQ4.5.1 or earlier), when using JDBC persistence storage for the message store,  the row count of the MQ's Transaction table (MQ41Txn<tablename>) in the database grows over time as long as there is continuous JMS transaction created and there is no period of inactivity. The Java heap histogram also shows the TransactionState objects pertaining to the GlassFish Message Queue to be high and it increases continuously.

If there is continuous non-stop load, it is possible that the MQ may run out of memory or the MQ41TXN table may grow to a large size; taking up space that may cause the broker to be slow to start later.This issue can only be seen when checking the MQ41TXN<brokername> table size.

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.