PH38720: ABORTED CONNECTIONS WAS REPORTED AS CLOSED CONNECTION WHEN RELEASE THE CONNECTION.

APAR status

• Closed as program error.

Error description

• when transaction timeout and the transaction will invoke
  abortTransactionParticipants if Abort Any Transaction
  Participants if initial is true.
  The issues are:
  1. From JDK8 API, the java.sql.Connection.abort result the
  connection marked as closed and close the physical connection to
  the database, which trigger later release method reports "closed
  connection" issue to client which in fact client don't need to
  handle/track it and make confusion to client, trigger more cases
  open with IBM:
  [5/21/21 15:12:11:256 HKT] 00000069 TransactionIm <
  setTimeoutInfo Exit
  
  com.ibm.ws.tx.jta.TimeoutManager$TimeoutInfo@56724827
  [5/21/21 15:12:11:256 HKT] 00000069 TimeoutManage <  setTimeout
  Exit
  [5/21/21 15:12:11:256 HKT] 00000069 TransactionIm 3   Abort Any
  Transaction Participants if initial
                                   true
  [5/21/21 15:12:11:256 HKT] 00000069 TransactionIm >
  abortTransactionParticipants Entry
  ...
  [5/21/21 15:12:14:910 HKT] 00000069 WSJdbcPrepare W   DSRA8600W:
  Error closing
  oracle.jdbc.driver.OraclePreparedStatementWrapper@5bc2dbc6
  java.sql.SQLRecoverableException: Closed Connection
  
  2. If in same global transaction, multiple threads engage, the
  other thread who use the same shared connection which is aborted
  also reports closed connection to client which make confusion.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server using xa transations.                *
  ****************************************************************
  * PROBLEM DESCRIPTION: Closed connection error can occur       *
  *                      when aborting xa timed out              *
  *                      transactions or abort purging           *
  *                      connections.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Customer may encounter closed connection error due to xa
  transaction being aborted at the end of the transaction
  timeout or abort purging the connection.
  

Problem conclusion

• Messages DSRA0305E, DSRA0306E, DSRA0307E, J2CA0171E, J2CA0172E,
  J2CA0173E have been added to indicate that a transaction timout
  occurred or abort purge occurred for the closed connection
  error.  This will help to
  determine root cause of the closed connection.
  
  The fix for this APAR is targeted for inclusion in fix pack
  9.0.5.14. For more information, see 'Recommended Updates for
  WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels