PQ90270: J2CA0122I is output on normal direct lookup of DataSource

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• APAR PQ83300 corrected a problem with lookup of a DataSource
  via a resource-ref.  A side-effect of that fix was that the
  J2CA0122I message appears in the SystemOut.log whenever a
  DataSource is found via direct lookup, whether or not the direct
  lookup was intentional.  This message should be suppressed
  unless debug is enabled so as not to cause undue concern.
  .
  Additional Symptoms:
  Customers who use full function MQ in BINDINGS mode may
  experience java.lang.OutOfMemoryError accompanied by high cpu
  utilization caused by excessive number of threads (TCBs that
  are not WebSphere worker threads) in the WebSphere servant. The
  TCBs have the following traceback:
  .
  CEEOPCT
  pthread_cond_timedwait
  condTimedWait
  sysMonitorWait
  xmThreadSleep
  JVM_Sleep
  java/lang/Thread.sleep
  com/ibm/ejs/j2c/poolmanager/TaskTimer.run
  com/ibm/ejs/j2c/poolmanager/TaskTimer.run
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere Application Server    *
  *                 V5.1.0 for z/OS                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Excessive J2CA0122I messages logged     *
  *                      when doing direct JNDI lookup of a      *
  *                      DataSource or ConnectionFactory.        *
  *                                                              *
  *                      An additional physical                  *
  *                      connection is created for each          *
  *                      DataSource, JCA Connection Factory or   *
  *                      JMS Connection Factory even though      *
  *                      connector configurations which support  *
  *                      smart handle support do not require the *
  *                      extra connection to be created.         *
  *                                                              *
  *                      WebSphere Application Server for z/OS   *
  *                      users accessing full function MQ may    *
  *                      notice an excessive number of Task      *
  *                      Timer threads created in servant. This  *
  *                      could cause the JVM heap to be leaked   *
  *                      resulting in java.langOutOfMemoryError  *
  *                      The problem, in connection management   *
  *                      code can cause an excessive amount of   *
  *                      the JVM heap to be consumed. A JVM heap *
  *                      analysis of the dump will show a large  *
  *                      number of com.ibm.ejs.j2c.* objects in  *
  *                      the heap, including a large number of   *
  *                      objects of type                         *
  *                      com.ibm.ejs.j2c.poolmanager.PoolManager *
  *                      Please note there may be a large number *
  *                      of these objects without memory leaks   *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Excessive J2CA0122I messages logged when doing direct JNDI
  lookup of a DataSource or ConnectionFactory (as opposed to
  using a resource reference mapped to a DataSource).
  
  An additional physical connection is created for
  each DataSource, JCA Connection Factory or JMS Connection
  Factory even though connector configurations which support
  smart handle support do not require the extra connection to be
  created.
  

Problem conclusion

• This message will be suppressed when doing direct JNDI lookup of
  a DataSource or ConnectionFactory unless 'debug' trace is
  enabled.
  
  Only create the extra physical connection if smart handles are
  not supported for this DataSource or ConnectionFactory instance.
  
  Memory leak was closed so that TaskTimer threads will expire
  and get cleaned up and so that the connection pooling objects
  will be released from the JVM heap.
  .
  APAR PQ90270 is associated with SERVICE LEVEL W510200 of
  WebSphere Application Server V5.1.0 for z/OS.
  

Temporary fix

Comments

APAR Information

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

  PQ90269

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

Modules/Macros

•    BBOUBINF
  

Fix information

• Fixed component name

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R510 PSY UQ92898

     UP04/10/13 P F410

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.