JMS JDBC Store Corrupted, JMS Fails to Initialize (Doc ID 2108530.1)

Last updated on APRIL 25, 2023

Applies to:

Symptoms

Customer observing the following error in the logs. In their setup, JDBC persistent stores are configured. From database perspective everything looked fine, the table existed and it was accessible. Restarting the managed server without dropping the table did not resolve this issue. In order to resolve this issue, customer had to shut down the managed servers that the persistent store was targeted to and drop the table. Once the server started up, since the table no longer existed, it was automatically recreated and everything was working fine. However, dropping the table is not an acceptable workaround as the messages will be lost from the persistent store.

Environment : WLS 12.1.3

In customers environment, no two JDBC stores are using the same JDBC store.

Issue not reproducible all the time and is happening in Production intermittently.

Cause

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