JMS JDBC Store Corrupted, JMS Fails to Initialize
Last updated on AUGUST 16, 2016
Applies to:Oracle WebLogic Server - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
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.
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