IV83775: TEPS RANDOMLY CRASHES AFTER APPLYING 630 FIX PACK6.

Tivoli Monitoring 6.3.0-TIV-ITM-FP0006-IV83775
IBM Tivoli Monitoring 6.3.0 Fix Pack 7 (6.3.0-TIV-ITM-FP0007)

APAR status

• Closed as program error.

Error description

• APAR Type:            Field
  Approver Initials:    RP
  Severity:             1
  Reported Release:     630
  Compid:               5724C04PS Tivoli Enterprise Portal Server
  ABSTRACT:             TEPS randomly crashes after applying 630
  Fix Pack 6
  
  PROBLEM DESCRIPTION:
  ================
  TEPS randomly crashes after applying 630-FP6. The eWAS
  SystemOut.log will show one of the following errors:
  
  java.lang.NullPointerException at
  com.ibm.TEPS.CTSQLJDBC.JDBCDataSource.pullSequenceWithTimeout(JD
  BCDataSource.java:541)
  
  or:
  
  java.sql.SQLException: Closed Resultset at
  oracle.jdbc.driver.ScrollableResultSet.next(ScrollableResultSet.
  java:311) at
  com.ibm.TEPS.CTSQLJDBC.JDBCDataSource.pullSequenceWithTimeout(JD
  BCDataSource.java:538)
  
  The exception occurs when trying to run a query to a JDBC data
  source (such as an Oracle warehouse database). If the query
  takes a long time to run, and the user switches to a different
  workspace before the JDBC query finishes, the crash will occur.
  

Local fix

Problem summary

• Portal server randomly crashes after applying 6.3.0 FP6.  The
  eWAS SystemOut.log will show one of the following errors:
  
  java.lang.NullPointerException at
  com.ibm.TEPS.CTSQLJDBC.JDBCDataSource.pullSequenceWithTimeout(JD
  BCDataSource.java:541)
  
  or:
  
  java.sql.SQLException: Closed Resultset at
  oracle.jdbc.driver.ScrollableResultSet.next(ScrollableResultSet.
  java:311) at
  com.ibm.TEPS.CTSQLJDBC.JDBCDataSource.pullSequenceWithTimeout(JD
  BCDataSource.java:538)
  
  The exception occurs when trying to run a query to a JDBC data
  source (such as an Oracle warehouse database).  If the query
  takes a long time to run, and the user switches to a different
  workspace before the JDBC query finishes, the crash will occur.
  

Problem conclusion

• Modified code to prevent race condition when destroying JDBC
  request object.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.3.0-TIV-ITM-FP0007
  

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

  TEPS

• Fixed component ID

  5724C04PS

Applicable component levels