PQ68957: PROVIDE MECHANISM TO DISABLE AUTOMATIC RECYCLING OF SERVERS BY SYSTEMS MANAGEMENT DURING CONVERSATION ACTIVATION | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Provide a mechanism (environment variable) to disable the automatic recycling of application servers when an activate is done for a conversation in the SM EUI containing a server with a new/changed application or other change requiring the application server to be refreshed. The server would still need to be manually recycled to pick up the new/changed application. However by providing a mechanism to disable the automatic recycling, the customer can control when the recycle is initiated. When Systems Management initiates the recycling, one server instance is stopped and restarted. Upon initialization complete of that server instance, Systems Management begins the stop/restart of the next server instanace of that server. However, Naming Registration may not have been completed from the first server instance, resulting in an outage of the application since it had not yet reregistered. This mechanism will let the customer choose when to recycle the application servers following an application install/reinstall. The recycle can then be handled manually or through automation to help control quiescing network requests through a sysplex distributor.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: Support is needed which will provide a * * means to disable automatic recycling of * * application servers when a conversation * * is activated. * **************************************************************** * RECOMMENDATION: * **************************************************************** During automatic recycling, one server instance is stopped and restarted. Upon initialization complete of that server instance, the stop/restart of the next server instance for that server begins. However, Naming Registration may not have been completed from the first server instance, resulting in an outage of the application since it had not yet reregistered. This mechanism will let the customer choose when to recycle the application servers following an application install/reinstall. The recycle can then be handled manually or through automation to help control quiescing network requests through a sysplex distributor.Problem conclusion A new environment variable RECYCLE_J2EE_SERVERS is added. Setting RECYCLE_J2EE_SERVERS to "N" for the Systems Management server will produce the following behavior for modified J2EE servers which are running when the conversation is activated: - automatic recycling of modified J2EE servers will not occur during conversation activation. The servers must still be restarted (manually or with some customer-provided automation) to allow changes to the server to take effect. - files associated with deleted applications on these servers will not be deleted from the HFS because the application will still be running until the server is restarted. To prevent accumulation of obsolete files on the HFS, the customer should delete all files and directories associated with the deleted applications after restarting the servers. This includes: * /<CBCONFIG>/apps/<server_name>/A/A<uuid>/ (directory) * /<CBCONFIG>/apps/<server_name>/A/A<uuid>.* (files) * /<CBCONFIG>/apps/<server_name>/<j2ee_application_name>/ (directory) * /<CBCONFIG>/working/<server_name>/temp/<sysplex_name>/ <server_inst_name>/<app_name> (directory) RECYCLE_J2EE_SERVERS is only used by the Systems Management server. If specified on any other server, it is ignored. The default value,"Y", performs automatic server recycling as was done prior to the introduction of this new variable. APAR PQ68957 requires changes to documentation. To access the latest online documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/zos_os390/ Appendix A of WebSphere Application Server V4.0.1 for z/OS and OS/390 Installation and Customization (GA22-7834-06) and WebSphere Application Server V4.0.1 for z/OS and OS/390 Assembling J2EE Applications (SA22-7836-05) will be changed as follows: The table labelled "Where to use environment variables" will be updated to indicate that the new RECYCLE_J2EE_SERVERS environment variable applies to a OS/390 Systems Management server instance and is optional. The following description of the new enviroment variable will be added to the section "Environment variable descriptions:" RECYCLE_J2EE_SERVERS = Y|N Specifies whether or not the Systems Management server will automatically recycle a J2EE server instance when a modified conversation for the associated J2EE server is activated. If "Y" is specified, the Systems Management server will automatically recycle J2EE server instances whenever a modified conversation is activated. When "Y" is specified, the environment variable performs the same function that was implemented prior to the introduction of this new variable. If "N" is specified, the Systems Management server: - Will not automatically recycle J2EE server instances whenever a modified conversation for the associated J2EE server is activated. The servers must still be restarted (manually or with some customer-provided automation) to allow changes to the server instance to take effect. - Will not delete files associated with deleted applications on these server instances from the HFS because the application will still be running until the server instance is restarted. To prevent accumulation of obsolete files on the HFS, you should delete all files and directories associated with the deleted applications after restarting the server instances. This includes: * /<CBCONFIG>/apps/<server_name>/A/A<uuid>/ (directory) * /<CBCONFIG>/apps/<server_name>/A/A<uuid>.* (files) * /<CBCONFIG>/apps/<server_name>/<j2ee_application_name>/ (directory) * /<CBCONFIG>/working/<server_name>/temp/<sysplex_name>/ <server_inst_name>/<app_name>/ (directory) Note: RECYCLE_J2EE_SERVERS is only used by the Systems Management server. If specified on any other server, it is ignored. Default: Y Example: RECYCLE_J2EE_SERVERS=Y APAR PQ68957 is associated with SERVICE LEVEL W401408 of WebSphere Application Server V4.0.1 for z/OS and OS/390.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
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ68957
IBM Group: Software Group
Modified date: Feb 5, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.