PQ90269: J2CA0122I is output on normal direct lookup of DataSource | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() 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.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: Incorrect Connection Management * * settings are used when doing a direct * * JNDI lookup of a DataSource or * * ConnectionFactory from an application * * with a resource reference with the * * same JNDI name. * * * * Excessive J2CA0122I messages logged * * when doing direct JNDI lookup of a * * DataSource or ConnectionFactory. * * * * Appearance of J2CA0112E messages * * when PMI is enabled and when using * * JMS. * * * * 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: * **************************************************************** The wrong Connection Management settings may be used in cases in which an application does a direct lookup of a JNDI name while using a resource reference with an identical name, except for the "java:comp/env" portion of the name. For example, if an application with a resource reference of "java:comp/env/jdbc/myds1" (mapped to some DataSource) does a direct JNDI lookup of "jdbc/myds1, the DataSource returned may be set up by WAS Connection Management with unexpected authentication (res-auth), sharing (res-sharing), and Isolation level settings. This can result in an application failure to get a connection, (with a J2CA0020 message), among other possible problems. 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). Appearance of J2CA0112E messages in log, such as: J2CA0112E : Factory or provider name for JMS$myQCF$JMSManagedConnection@NNNNNNNNNN was null. This can occur when PMI is enabled with applications running with WebSphere MQ JMS.Problem conclusion Use correct Connection Management settings for direct JNDI DataSource or ConnectionFactory lookup. This message will be suppressed when doing direct JNDI lookup of a DataSource or ConnectionFactory unless 'debug' trace is enabled. Unintended J2CA0112E messages with PMI enabled when using WebSphere MQ JMS are suppressed. 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 PQ90269 is associated with SERVICE LEVEL W502013 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: PQ87278 APAR is sysrouted TO one or more of the following: PQ90270 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ90269.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ90269
IBM Group: Software Group
Modified date: Aug 21, 2007
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.