APAR status
Closed as program error.
Error description
[5/15/23 9:07:28:515 CEST] FFDC Exception:javax.naming.NamingException SourceId:com.ibm.ws.naming.util.Helpers.logJndiContextException ProbeId:1636 Reporter:java.lang.Class@aaac2bca javax.naming.NamingException: NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow: Context implementation: com.ibm.ws.naming.jndicos.CNContextImpl Context method: lookupExt Context name: npa9a/clusters/npaa_cluster Target name: jdbc/NPA_DS_NPAA Other data: Exception stack trace: com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is java.lang.NullPointerException] at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLo okupExt(Helpers.java:1235) at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLo okup(Helpers.java:928) From \websphere\npa9a2\config\cells\npa9a\clusters\npaa_cluster \resources.xml,can find: <factories xmi:type="resources.jdbc:DataSource" xmi:id="DataSource_1373025906303" name="NPA_DS_NPAA" jndiName="jdbc/NPA_DS_NPAA" ... <connectionPool xmi:id="ConnectionPool_1373025906305" connectionTimeout="180" maxConnections="100" minConnections="1" reapTime="180" unusedTimeout="1800" agedTimeout="0" purgePolicy="EntirePool" numberOfSharedPoolPartitions="0" numberOfUnsharedPoolPartitions="0" numberOfFreePoolPartitions="0" freePoolDistributionTableSize="0" surgeThreshold="-1" surgeCreationInterval="0" testConnection="false" testConnectionInterval="0" stuckTimerTime="0" stuckTime="0" stuckThreshold="0"/> Search and check code, sounds like relate to this line of code: if ((gConfigProps.getStuckQueryTime() > 0 && gConfigProps.getStuckQueryInterval() > 0)) { //158708.3 // PH48686 But from configuration, gConfigProps should not be Null.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server using datasource stuck connection * * function. * **************************************************************** * PROBLEM DESCRIPTION: During serialized processing of a * * datasource, * * stuck * * connection properties are null, * * resulting in a null pointer exception. * **************************************************************** * RECOMMENDATION: * **************************************************************** The follow error may occur during serialized processing of a datasource connection pool object. com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is java.lang.NullPointerException] at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLo okupExt(Helpers.java:1235) at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLo okup(Helpers.java:928)
Problem conclusion
The properties that are null from the serialized processing of a datasource are now being initialized correctly. The fix for this APAR is targeted for inclusion in fix pack 9.0.5.17. For more information, see 'Recommended Updates for WebSphere Application Server': https://www.ibm.com/support/pages/node/715553
Temporary fix
Comments
APAR Information
APAR number
PH54595
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-05-18
Closed date
2023-07-21
Last modified date
2023-07-21
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
22 July 2023