PQ94972: APPLICATION UPDATE FAILS WITH THE NULLPOINTEREXCEPTION | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description PQ93178 added the ability to retain metadata information (in deployment.xml file) during app updates. With this fix in place, if there is an unnamed config at module level, app update fails with a NullPointerException. The SystemErr.log has the following stack: java.lang.NullPointerException at com.ibm.ws.management.application.AppAssociation. getOrCreateConfig(AppAssociation.java:1126) at com.ibm.ws.management.application.AppAssociation. populateDeployTargets(AppAssociation.java:840) at com.ibm.ws.management.application.task.ConfigureTask. createModuleDeployment(ConfigureTask.java:361) at com.ibm.ws.management.application.task.ConfigureTask. createDeployment(ConfigureTask.java:283) at com.ibm.ws.management.application.task.ConfigureTask. performTask(ConfigureTask.java:119) at com.ibm.ws.management.application.SchedulerImpl. run(SchedulerImpl.java:215) at java.lang.Thread.run(Thread.java:479) This is because the app update logic expects the configs always to be named, but either wsadmin or console has taken this into consideration to prevent unnamed config from being created. The app update logic needs improvement to handle unnamed config so such NullPointerException won't occur.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server v5.x users who * * create server configurations for deployed * * applications. * **************************************************************** * PROBLEM DESCRIPTION: A NullPointerException occurs when * * updating an application which has an * * unnamed server configuration. * **************************************************************** * RECOMMENDATION: * **************************************************************** The application management code assumed a server configuration is always named, which is not true. The code needed to be modified to handle unnamed server configurations. Server configurations contain information about the server target for the application either at application level or module level. One example of a server configuration is session management.Problem conclusion Updated the application management code to handle unnamed server configurations during application update.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ94972
IBM Group: Software Group
Modified date: Nov 9, 2004
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.