PQ87592: NULLPOINTEREXCEPTION CAUSED WHEN DEPLOYEDAPPLICATIONS TAG EXISTSIN SERVERINDEX.XML FOR AN APPLICATION THAT WAS UNINSTALLED | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Sync fails when customer deploys an application. He sees the following errors: . In the nodeagent log: . ExtendedMessage: replaceObject; javax.management.RuntimeMBeanE .at com.ibm.ws.management.connector.soap.SOAPConnectorClient.han .at com.ibm.ws.management.connector.soap.SOAPConnectorClient.inv .at com.ibm.ws.management.connector.soap.SOAPConnectorClient.inv .at com.ibm.ws.management.connector.soap.SOAPConnectorClient.inv .at $Proxy1.invoke(Unknown Source) .at com.ibm.ws.management.AdminClientImpl.invoke(AdminClientImpl .at com.ibm.ws.management.sync.NodeSync.invokeGetModifiedFolders .at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask. .at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.jav .at java.lang.Thread.run(Thread.java:513) ---- Begin backtrace for nested exception java.lang.NullPointerException . Also in the DMGR control region log (around the time of the NullPointerException) we saw: . Trace: 2004/01/28 10:52:32.765 01 t=7CA730 c=UNK key=P2 (1300700 FunctionName: com.ibm.ws.management.repository.FileRepository SourceId: com.ibm.ws.management.repository.FileRepository Category: DEBUG ExtendedMessage: extract: invalid URI; cells/CENTER2/applicati Pricing.ear/deployments/Pricing/deployment.xml . We researched this back to find that the error was caused because the serverindex.xml file that resides in the DMGR's hfs contains a deployedApplications tag for the customer's application shown in the error message (Pricing.ear) which had previously been uninstalled. The problem was resolved by removing this deployedApplications tag for the uninstalled application. The customer feels that, in lieu of the NullPointerException and non-descriptive message, we should generate and write a more descriptive message to the log and adminconsole. The customer requests that a message be generated to notify the user that the sync is not possible, explain why it is not possible (for example, the tag exists for a non existent application), and the SAVE operation not be allowed to conclude, thus leaving the node in a non-SYNC'd condition.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: NullPointerException occured during a * * node sync operation. * **************************************************************** * RECOMMENDATION: * **************************************************************** NullPointer Exception was thrown during a node sync operation, however, sync operation was successful.Problem conclusion Rollup WebSphere Application Server for Distributed code which fixed the same problem in PQ87196. APAR PQ87592 is associated with SERVICE LEVEL W502011 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: PQ89472 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ87592.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 #: PQ87592
IBM Group: Software Group
Modified date: Jul 2, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.