Data Queue Threads Disappear After A Brief Database Connection Problem

(Doc ID 1613595.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Transportation Management - Version 6.3.1 to 6.3.4 [Release 6.3]
Information in this document applies to any platform.


After the application server lost connection to the database server for a brief period, all threads in thread pool INTEGRATION IN disappeared. A thread dump using JRockit command "jrcmd print_threads" confirmed the observation. As a result, queue INTEGRATION IN was backed up. However, other parts of OTM survived the connection loss and continued to function correctly. The problem was eventually corrected by a server bounce.

Here is an excerpt from the error log showing how database connection errors caused a thread to terminate normally.

2013-11-15 04:55:17.436 0 Error Exception {call vpd.set_user_r(?,?,?,?)=null}; inParams=[DBA.ADMIN, DBA.AD
MIN, null, STATIC]
  java.sql.SQLRecoverableException: No more data to read from socket

java.sql.SQLRecoverableException: No more data to read from socket
  at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(
  at oracle.jdbc.driver.T4CTTIfun.receive(
  at oracle.jdbc.driver.T4CTTIfun.doRPC(
  at oracle.jdbc.driver.T4C8Oall.doOALL(
  at oracle.jdbc.driver.T4CCallableStatement.doOall8(
  at oracle.jdbc.driver.T4CCallableStatement.executeForRows(
  at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(
  at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(
  at oracle.jdbc.driver.OraclePreparedStatement.execute(
  at oracle.jdbc.driver.OracleCallableStatement.execute(
  at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(
  at glog.util.jdbc.SqlCall.execute(
  at glog.util.jdbc.SqlCall.executeOut(
  at glog.util.jdbc.SqlCall.execute(
  at glog.util.jdbc.noserver.T2ConnUser.setToDB(
  at glog.util.jdbc.noserver.T2SharedConnection.setDatabaseUser(
  at glog.util.jdbc.noserver.T2SharedConnection$ReferencedConnection.setupVpdUser(
  at glog.util.jdbc.noserver.T2SharedConnection$ReferencedConnection.addRef(
  at glog.util.jdbc.noserver.T2SharedConnection$ReferencedConnection.addRef(
  at glog.util.jdbc.CheckForSQLExceptions.loadCustomErrorMessage(
  at glog.util.jdbc.CheckForSQLExceptions.mapSQLException(
  at glog.util.exception.GLException.factory(
  at glog.util.exception.GLException.factory(
  at glog.util.exception.GLException.factory(
  at glog.util.exception.GLException.factory(
  at glog.util.datasource.GC3ConnectionEstablisher.connect(
  at glog.util.datasource.DataSource.reserve(
  at glog.util.datasource.DataSource.reserve(
  at glog.util.jdbc.noserver.T2SharedConnection$ReferencedConnection.reopenIfDropped(
  at glog.util.jdbc.noserver.T2SharedConnection.reopenIfDropped(
  at glog.server.dataqueue.DataQueue.checkForDroppedConnection(

2013-11-15 04:55:17.437 0 Error Exception java.sql.SQLRecoverableException: IO Error: Got minus one from a
read call

java.sql.SQLRecoverableException: IO Error: Got minus one from a read call
  at oracle.jdbc.driver.T4CConnection.logon(
  at oracle.jdbc.driver.PhysicalConnection.(
  at oracle.jdbc.driver.T4CConnection.(
  at oracle.jdbc.driver.T4CDriverExtension.getConnection(
  at oracle.jdbc.driver.OracleDriver.connect(

It appears that the system had been idle right before thread INTEGRAION IN - 4 disappeared. I don't have the regular log to confirm this since the files had been overwritten by the time the problem was noticed. The timestamp was early morning local time (4:55 am) and there had been not entries in the exception log for 3 hours.

However it does not matter whether there was an XML input what the content of the XML was. A data queue thread pols the queue at regular intervals. The error happened during the polling. In the log you can see the following stack traces showing the sql statement and the error. The poller was try to get a lock on the data queue before a poll.

2013-11-15 04:55:17.323 0 Error Exception select 1 from data_queue_def where data_queue_def_gid=? for update; [INTEGRATION IN] [INTEGRATION IN - 4]
2013-11-15 04:55:17.324 0 Error Exception {call vpd.set_user_r(?,?,?,?)=null}; inParams=[DBA.ADMIN, DBA.ADMIN, null, STATIC]
  java.sql.SQLRecoverableException: No more data to read from socket


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