PK74035: i5/OS: Application server will not stop if the profile was initially created to use Classic jvm and changed to use J9.

Fixes are available

APAR status

Closed as program error.

Error description

On i5/OS, when a product install of WebSphere Application
Server is configured to use the Classic jvm, profiles are
created with configuration files with values that are not
correct.  The application server will operate correctly when
using the Classic jvm, but when the enableJvm command is used
to convert a profile to use a J9 jvm, it will not be able to
correct the configuration file and the application server will
not stop when the stopServer command is issued.

Local fix

A workaround to ensure that the configuration files are correct
is to first issue the following command:
enableJvm -jvm classic -profile XX
 (where XX is the profile name)
Now the 'enableJvm -jvm std32 (or std64) -profile XX' command
will work correctly and the stopServer command will work.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V7.0                                        *
****************************************************************
* PROBLEM DESCRIPTION: Cannot stop an application server       *
*                      after using the enableJvm script to     *
*                      enable it to use either J9 java         *
*                      virtual machine.                        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a Websphere Application Server is installed to initially
use the Classic java virtual machine, the use of the enableJvm
script to enable a profile to use either of the J9 virtual
machines will fail to completely change the profile's
configuration.  Such a profile's application server will be
able to start and run, but the subsequent 'stopServer' command
will fail to stop the server.

Problem conclusion

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.1.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK74035
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-17
Closed date
2008-11-13
Last modified date
2008-11-13

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 October 2021

Tips

PK74035: i5/OS: Application server will not stop if the profile was initially created to use Classic jvm and changed to use J9.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?