PQ63409: UNABLE TO PROPAGATE A JVM SYS PROPERTY FROM A SERVER GROUP | |||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
APAR status Closed as documentation error. Error description On a cluster of 2 Sun Solaris boxes, running WebSphere Application Server 4.0.2, a customer is 4.0.2, customer is unable to propagate a JVM system property from the server group to the clones. Issuing "apply" and "ripple" from the Application Server admin console does not work. The UI indicates that the new system property is added to the server group definition, but the clones do not have it.Local fix The "System Properties" has been changed to a Clone-Only attributes on WebSphere Application Server 4.02. The "System Properties" will not be propagated to the clones, but the user caqn add/modify the properties in the clone attributes. The reason for the change of the design on WebSphere Application Server 4.02 is because on 4.01, one can add the "System Properties" to the clones only through the Server Group and the system properties field on the clones is "uneditable". The "System Properties" for a server group are copied into all clones which would cause the critical error on starting the server group in many situations. For example, if the server group contains application servers (clones) in different system platforms. We add a system properties with some path specified for a server group to enable security. The server group contains 20 application servers, 10 are on AIX node and the others are on Windows NT node. "was.home=c:/WebSphere/AppServer enable.Java2Security=true java.security.policy=c:/WebSphere/AppServer/properties/java.poli cy" If we propagate the system properties to all clones (application servers), it would fail to start the application servers on AIX node since the Application Server install path on AIX is different from the NT. The user has to change the properties for the clones on AIX node to their local directory (was.home=/usr/WebSphere/AppServer...). However, the System Properties field on the clones is "uneditable" on 4.0.1. It is clearly incorrect behavior, thus we change the "System Properties" to be a Clone-Only Attribute on WebSphere Application Server 4.02 release.Problem summary **************************************************************** * USERS AFFECTED: On a cluster of 2 Sun Solaris boxes, * * running WebSphere Application Server * * Version 4.0.2, user is unable to * * propagate a JVM system property from the * * server group to the clones. * **************************************************************** * PROBLEM DESCRIPTION: Issuing "apply" and "ripple" from the * * WebSphere Application Server * * administrative console does not work. * * * * The user interface indicates that the * * new system property is added to the * * server group definition but the clones * * do not have it. * **************************************************************** * RECOMMENDATION: * **************************************************************** For FixPak 4.0.2 and later FixPaks, the system properties has changed to a clone-only attributes. The system properties will not be propagated to the clones, but you can add or modify the properties in the clone attributes.Problem conclusion Close this APAR as a documentation change. (4.0.4 Release Notes)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 > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ63409
IBM Group: Software Group
Modified date: Apr 30, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.