My Oracle Support Banner

WebLogic Server JDBC JMS Store Corruption when Hitting Database Tablespace Limit (Doc ID 878332.1)

Last updated on AUGUST 03, 2023

Applies to:

Oracle WebLogic Server - Version 9.2 to 10.3.1
Information in this document applies to any platform.


With JMS messages stored in a database persistent store, it was found that if the tablespace was fixed and ran out of space, the server went to failed state and could not be restarted until the table was truncated (even if the space was increased). This would cause the loss of the JMS messages.

This occurred when a MDB would listen on one queue and send messages to another queue (using an XAConnectionFactory and the MDB Transaction set to REQUIRED). (This is a pure WLS imitation of a common ALSB/OSB configuration of a Business Service with QOS of exactly once.)

Expected behavior is that the server should restart without truncating the table.

The following error occurred on restart attempt:




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

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