Java crash in libocijdbc

Solution Verified - Updated

Environment

JBoss Enterprise Application Platform (EAP) all versions

Issue

Our JBoss process is crashing with a JVM cored dump. It generated an hs_err_ file with the following content at the top:

# JRE version: 6.0_31-b04
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.6-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libocijdbc11.so+0x810d]  Java_oracle_jdbc_driver_T2CConnection_t2cPingDatabase+0xb

Another example:

# JRE version: OpenJDK Runtime Environment (8.0_302-b08) (build 1.8.0_302-b08)
# Java VM: OpenJDK 64-Bit Server VM (25.302-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libocijdbc12.so+0x95d5]  Java_oracle_jdbc_driver_T2CConnection_t2cDescribeTable+0x65

Resolution

As the issue is happening in the Oracle JDBC driver, the next steps should be:

  1. Upgrade the Oracle JDBC driver and check if it solves the issue
  2. Upgrade the JVM and check if it solves the issue.

if neither helps,

  1. Contact Oracle support and log an issue for the crashing of the Oracle JDBC driver. Oracle support can verify if the database driver is compatible with the JDK and OS versions or if it is a known issue fixed in a later release.

Root Cause

[libocijdbc11.so+0x810d] Java_oracle_jdbc_driver_T2CConnection_t2cPingDatabase+0xb

clearly indicates the issue crash is happening in the Oracle JDBC driver.

SBR
Product(s)

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.