PQ72990: TRYING TO CREATE NEW NAME PAIR UNDER A SYSTEM PROPERTIES JVM TAB IN THE WEB CONSOLE

 Fixes are available

4.0.6: WebSphere Application Server Version 4.0 Fix Pack 6
PQ72990; 4.0.1-4.0.5: NullPointerException trying to create a JVM property



APAR status
Closed as program error.

Error description
CUSTOMER IS RECIEVING A NULL POINTER EXCEPTION WHEN TRYING
TO CREATE NEW NAME PAIR UNDER A SYSTEM JVM TAB IN THE AEs WEB
CONSOLE
Local fix
NO WORK AROUND
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 4.0 Advanced    *
*                 Edition Single Server (AEs) users on all     *
*                 platforms.                                   *
****************************************************************
* PROBLEM DESCRIPTION: When using a configuration file that    *
*                      is not the default server-cfg.xml file  *
*                      users can not add JVM properties via    *
*                      the Thin Admin console.                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the server-cfg.xml file is removed or renamed from the
<WebSphere_home>/config directory and the user starts the
server by pointing to a different XML config file a
NullPointerException is thrown when trying to add a JVM property
in the Thin Admin.  The error arises when the user clicks on the
"New" button while adding a JVM system property.
The following error is thrown:
java.lang.NullPointerException at
com.ibm.ejs.sm.web.server.EditJVMSystemPropertyAction.perform
(EditJVMSystemPropertyAction.java:127) at
org.apache.struts.action.ActionServlet.processActionInstance
(ActionServlet.java:960)at
org.apache.struts.action.ActionServlet.processActionServlet.java
:869)at org.apache.struts.action.ActionServlet.doPost
(ActionServlet.java:361)
...
Problem conclusion
The cause of this problem was that there were some session
attributes that were not being set during the logon when the
server was pointed to a different XML configuration file during
startup.  These attributes are set during a normal startup when
there is a server-cfg.xml file in the <WebSphere_home>/config
directory.
The following session attributes were not being set during
logon:
resourcesFactory
applicationFactory
serverFactory
securityFactory
Temporary fix
This temporary fix will set the serverFactory session attribute
when the user is not using the default server-cfg.xml file.
Th
is is the reason for the NullPointerException.
Comments
APAR information
APAR number PQ72990
Reported component name WEBSPHERE AES L
Reported component ID 5630A2307
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-04-08
Closed date 2003-04-15
Last modified date 2003-04-15

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
THINADMN          

SRLS

Fix information

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ72990
IBM Group: Software Group
Modified date: Apr 15, 2003