GlassFish Message Queue JDBC Transaction Table Count Increase With Load
Last updated on NOVEMBER 05, 2016
Applies to:Sun Java System Message Queue - Version: 4.4u2
Oracle GlassFish Server - Version: 2.1.1 and later [Release: 2.1 and later]
Information in this document applies to any platform.
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.
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