PI59220: DISCONNECTED JTDS SQL SERVER LINK NOT RECONNECTED (E.G. AT STARTOF STUB INVOCATION)

Rational Performance Test Server 9.2
Rational Test Virtualization Server 9.2
Rational Integration Tester 9.2

APAR status

• Closed as program error.

Error description

• When a long running stub has a jTDS connection to a SQL Server
  (and test actions which make use of that connection) then if the
  connection reaches a disconnected state then the stub will
  subsequently fail to respond.  Restarting the stub is
  insufficient (presumably because the connection remains broken)
  and to fix the problem the Agent needs to be restarted.  (If the
  same happens in RIT the connection could be manually
  disconnected.)  It is likely that this is true of all database
  connections.
  
  Since the connection is a pooled connection the disconnection
  should be identified and fixed before use, e.g. after the start
  of the database action, or the invocation of the stub at the
  time of the pooled resource allocation; and at those times for
  pooled resource items which remain allocated to the current
  process.
  

Local fix

• There is no known preventative measure which can be taken.
  
  When this occurs on RIT-Agent restart the Agent.
  
  In IBM Rational Integration Tester (RIT) use Architecture School
  and right click the connection and select "disconnect", then
  restart the stub.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of Rational Integration Tester accessing a database    *
  * with a driver that does not support all of the JDBC 4.0      *
  * methods.                                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When checking connectivity to a database, the application    *
  * uses methods present within the JDBC 4.0 specification to    *
  * check the validity of the connection, in some older drivers  *
  * these are not available and prevent re-connection from being *
  * possible.                                                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• In Rational Integration Tester 9.2 a fallback mechanism is used
  to determine database connection validity allowing older drivers
  to be used.
  

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

  RATL INTEGRA TE

• Fixed component ID

  5725G79IT

Applicable component levels

• R800 PSN

     UP

• R801 PSN

     UP

• R850 PSN

     UP

• R851 PSN

     UP

• R860 PSN

     UP

• R870 PSN

     UP

• R871 PSN

     UP

• R900 PSN

     UP

• R901 PSN

     UP

• R910 PSN

     UP

• R911 PSN

     UP

• R920 PSY

     UP