PQ78156: USING SHELL OR JACL SCRIPTS TO DEPLOY APPLICATIONS IN WEBSPHERE V5, THE 'NODESYNC' COMMAND IS ASYNCRONOUS | |||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||
APAR status Closed as fixed if next. Error description Customer is using shell scripts (and jacl scripts) to install / re-install applications in a Deployment Manager configuration of WebSphere for z/OS V5. The jacl script is starting the application, after doing a nodesync. The start of the application is failing with a java.lang.ClassNotFoundException: on a class which is part of the application, packaged in the application .war file. . The nodesync operation pushes the install out to the node agents and once it has been pushed to the node agents, control is returned to the jacl script. . The node agents then push the install out to the application servers, wihch will then 'un-zip' the .war file, into the hfs on the system where the application is installed. . The start application was being issued prior to the un-zip of the .war file being completed, thus the error: java.lang.ClassNotFoundException: . This apar is being taken to provide a mechanism for the nodesync to delay return to the jacl script, until the application is installed on the servers. .Local fix There are several local fixes, depending on the situation 1) If the application had been installed, and was active, then the install of the new/changed application is done with the -update option. The -update option will: a) Stop the application b) install the new level of the application c) Start the new level of the application . Therefore the jacl script does NOT have to issue the 'startApplication', it will be restarted automatically. . 2)If this is a 'new install' of an application, then a sleep timer of 20 seconds (or more depending on the responsiveness of the system) should b eplaced between the 'nodeSync' and the 'startApplication' . 3)If the application had been installed, but NOT active at the time of the re-install, then a 'sleep timer' should be added as in #2, to delay the 'startApplication'.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: On a Network Deployment install: * * After installation of an Application, * * that application's binaries must be * * sent to the various nodes that the * * application is installed in. * * An attempt to start the Application * * can subsequently fail, even though the * * binaries appear to have been * * distributed. * **************************************************************** * RECOMMENDATION: * **************************************************************** Due to the asynchronous nature of the config synchronication process,there was no realiable way to know that the Application is ready to be started. The synchronization function returns when the application binaries are transfered, but before the binaries are unwound on the HFS. Subsequently if an attempt is made to start the application too soon, errors will occur. This most commonly affects wsadmin scripting.Problem conclusion Temporary fix Comments This APAR is being closed FIN with concurrence from the submitting customer. A solution to this problem will be delivered in a WebSphere Application Server for z/OS release within the next 18 months.
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced
|
Document Information |
Current web document: swg1PQ78156.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 #: PQ78156
IBM Group: Software Group
Modified date: Dec 12, 2003
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.