Defining Fatal Error Codes for JCA/Database interactions in JBoss

Issue

• In Oracle 12c, there is an attribute in DB connection pool settings "Fatal error codes" . This optional attribute is used to define fatal error codes, that when specified as the exception code within a SQLException (retrieved bysqlException.getErrorCode()), indicate that a fatal error has occurred and the connection is no longer usable. By default, it include most common ORA errors:
  • 3113: "end-of-file on communication channel"
  • 3114: "not connected to ORACLE"
  • 1033: "ORACLE initialization or shutdown in progress"
  • 1034: "ORACLE not available"
  • 1089: "immediate shutdown in progress - no operations are permitted"
  • 1090: "shutdown in progress - connection is not permitted"
  • 17002: "I/O exception"
• ORA-16456: switchover to standby in progress or completed means the underlying database is going to switch to secondary, so we consider it's a fatal error.

Is there a similar feature in EAP6 where we can specify the fatal error code and when an exception is marked as fatal the connection from which it came is closed immediately?