A fix is available
APAR status
Closed as program error.
Error description
Whitespaces in front of WebSphere variables in the generic jvm arguments section of the server.xml causes the Portal server to abend when upgrading from 7.0.0.4 to 7.0.0.5 For example, Portal sets the generic JVM argument in the server.xml with a leading whitespace: genericJvmArguments=" ${WPS_JVM_ARGUMENTS_EXT} -Dderby.system.home=${USER_INSTALL_ROOT}/PortalServer/derby -Dibm.stream.nio=true -Xgcpolicy:gencon" This will cause the ${WPS_JVM_ARGUMENTS_EXT} websphere variable to be resolved incorrectly and the subsequent *.jvm.options file will be generated with the ${WPS_JVM_ARGUMENTS_EXT} key instead of the actually value: ${WPS_JVM_ARGUMENTS_EXT} -Dderby.system.home=/WebSphere/V6R1/AppServer/profiles/default/P ortalServer/derby -Dibm.stream.nio=true -Xgcpolicy:gencon During server startup, the following error will be logged: JVMJ9VM007E Command-line option unrecognized: ${WPS_JVM_ARGUMENTS_EXT}
Local fix
Change the generic jvm argument from the admin console: 1) Servers -> Application Server -> <serverName> -> Server Infrastructure -> Java and Process Management -> Process Definition -> <processType> -> Java Virtual Machine -> Generic JVM arguments 2) Remove the whitespace infront of the websphere variable. 3) Apply -> Save to Master Repository -> Sync Node 4) Restart the application server.
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V7.0 * * * **************************************************************** * PROBLEM DESCRIPTION: Whitespaces in front of WebSphere * * variables in the GenericJVMArgs * * property of the server.xml causes the * * Portal server to abend when upgrading * * from 7.0.0.4 to 7.0.0.5 * * * **************************************************************** * RECOMMENDATION: * **************************************************************** Leading whitespace before a WebSphere variable in the GenericJVMArgs property of the server.xml causes the server to abend at 7.0.0.5 when it didn't at 7.0.0.4. Setting the generic JVM argument in the server.xml with a leading whitespace: genericJvmArguments=" ${WPS_JVM_ARGUMENTS_EXT} -Dderby.system.home=${USER_INSTALL_ROOT}/PortalServer/derby -Dibm.stream.nio=true -Xgcpolicy:gencon" This will cause the websphere variable to be un-resolved in the *.jvm.options file. During server startup, the following error will be logged: JVMJ9VM007E Command-line option unrecognised: ${WPS_JVM_ARGUMENTS_EXT}
Problem conclusion
The code has been modified to handle leading whitespace in the GenericJVMArgs property. APAR PK94036 is currently targeted for inclusion in Service Level (Fix Pack) 7.0.0.7 of WebSphere Application Server V7.0. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PK94036
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-17
Closed date
2009-10-21
Last modified date
2009-12-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
BBGUBINF BBOUBINF
Fix information
Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R700 PSY UK51554
UP09/11/10 P F911
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 February 2022