JMS JDBC Persistent Store Does Not Failover When Using oracle_blob.ddl

(Doc ID 1440155.1)

Last updated on MAY 24, 2017

Applies to:

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


A JDBC persistent store using oracle_blob.ddl to create the backing table and a multi data source with Oracle RAC nodes does not fail over properly. If the RAC node associated with the first data source in the multi data source list goes down, the below errors occur even if the second data source is available. The server is then marked as failed, and has to be restarted. This exact same configuration fails over properly if using the JDBC persistent store uses the default ddl to create the JDBC store backing table with a LONG RAW column.

The issue can be reproduced at will with the following steps:

  1. Create blob JDBC persistent store.
  2. Create JMS server using a queue.
  3. Deploy app that consumes messages.
  4. Send message to queue.
  5. Shutdown RAC node that WLS connected to to simulate RAC failure.
  6. Send message to queue.
  7. Observe error


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