My Oracle Support Banner

Unable to Reconnect JDBC Connection After Restart of Database Without Application Server Restart (Doc ID 1279187.1)

Last updated on AUGUST 14, 2020

Applies to:

Oracle Retail Central Office - Version 12.0.3IN and later
Oracle Retail Back Office - Version 12.0.3IN and later
Information in this document applies to any platform.


In Oracle Retail Back Office (ORBO) and Oracle Retail Central Office (ORCO), we find that no code is written to re-initialize lost JDBC connections.  Due to this, the connection is closed by the application server, but the JDBC driver still has the connection in an open state.   Whenever SQL is subsequently executed, the following exception is seen:

"The connection is closed"

Another symptom with the same cause as above:

In ORBO and ORCO, we find that incoming data import (DIMP) batches are reaching the archive folder on database connection issues.


Steps to Reproduce:

  1. Stop listener and Oracle Service, and copy the *.jar in the incoming directory of ORBO.
  2. *.jar is moved to the archive folder and the xml data is not inserted into the database.
  3. Ideally, if database service is down the import bundles should still remain in the incoming directory and should get processed to archive when DB service comes back up.


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.