PQ91787: For Sun JDK command line argument MaxPermSize cannot be set

 Fixes are available

5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux



APAR status
Closed as program error.

Error description
For Sun JDK command line argument MaxPermSize cannot be set in
adminconsole on WAS 5.0/5.1 on Solaris.WAS is not setting up
parameters properly for the Sun JVM. Users are unable to set or
alter MaxPermSize in the adminconsole as the argument is set in
the sun.system.properties file in the wasjmx.jar. Setting the
value in the adminconsole has no effect as the value is picked
up from the properties file.In order to alter MaxPermSize
unjarring wasjmx.jar and modification of the
sun.system.properties file would be required.Additionally,
MaxPermSize is listed twice with a ps -grep of the java process
when set in the in the adminconsole.
Local fix
In order to alter MaxPermSize unjarring wasjmx.jar and
modification of the sun.system.properties file would be
required.
Problem summary
****************************************************************
* USERS AFFECTED: Users of Websphere Application Server        *
*                 version 5.1.1                                *
****************************************************************
* PROBLEM DESCRIPTION: Sun JDK Command line MaxPermSize        *
*                      property of Generic JVM arguments       *
*                      getting overriden by Default JVM        *
*                      arguments                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
MaxPermSize Generic JVM arguments of an Application Server
value is getting overriden by the Default JVM arguments which
are picked from the sun.systemlaunch.properties
Problem conclusion
Prior to the fix there were two MaxPermSize properties in the
command line arguments one from the Default JVM & other from
the Generic JVM arguments for the application server. This fix
will override the Default JVM arguments if Generic JVM
arguments are set through the Admin console
Temporary fix
The problem is related to MaxPermSize setting in Sun system.laun
ch.properties.
The Default JVM arguments are overriding the Generic JVM argumen
ts specified through the admin console.
The commmand line arguments contains two -XXMaxPermSize entries
which causes the problem.
This fix will make sure that :
1. Always only one MaxPermSize entry is present in the
commandline args.
2. Generic JVM Arguments will override the default jvm arguments
.
Comments
APAR information
APAR number PQ91787
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 10S
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-07-21
Closed date 2004-09-30
Last modified date 2006-01-20

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
ADMINJMX          

Publications Referenced

Fix information

Applicable component levels
R00S PSY    UP
R10S PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 10S
Software edition:
Reference #: PQ91787
IBM Group: Software Group
Modified date: Jan 20, 2006