PM01997: WHEN USING SDK 64-BIT FIX PACK 5 AND 7, THE APPLICATION SERVER'SJVM MAY CRASH UPON STARTUP WHEN CONFIGURED TO RUN IN DEBUG MODE

Fixes are available

APAR status

Closed as program error.

Error description

Fix Pack 3 for the 64-bit Java SDK for AIX, Linux, and Windows
introduces a new file in the WAS_HOME/java directory.  The name
and location of the file depends on the operating system and
architecture:

Product Edition        Location
---------------        --------
AIX (64-bit)           java/jre/lib/ppc64/libvmi.so
Linux (x86_64)         java/jre/lib/amd64/libvmi.so
Linux (i/p series)     java/jre/lib/ppc64/libvmi.so
Linux (zSeries 64-bit) java/jre/lib/s390x/libvmi.so
Windows (64-bit)       java/jre/bin/vmi.dll

The file was removed from that location in newer versions of the
JVM (beyond Fix Pack 3).  However, installing SDK 64-bit Fix
Pack 5 or Fix Pack 7 does not properly remove that file.  (Note
that other copies of that file with the same name are present in
other subdirectories, but those files are meant to be intact in
those other locations.)  When this file is present and Fix Pack
5 or Fix Pack 7 is applied, the application server's JVM will
crash upon startup when it is configured to run in debug mode.

Local fix

This file will be present if Fix Pack 3 is installed.  So, if
you install WebSphere Application Server V7.0 64-bit, then
install SDK 64-bit Fix Pack 3, then SDK 64-bit Fix Pack 5, then
this file will be present.  (In that case, the file should be
removed.  See below.)  But, if you install WebSphere Application
Server V7.0 64-bit, then install SDK 64-bit Fix Pack 5, the file
will not be present.  (In that case, take no action.)

Also, if you uninstall all SDK Fix Packs above SDK Fix Pack 3,
then uninstall SDK Fix Pack 3 itself, the file will be removed.
You can then re-install higher fix packs, such as SDK Fix Pack
5, and the file will not be re-created.

The file can be manually removed if Fix Pack 5 or Fix Pack 7 has
been installed on top of Fix Pack 3.  See the list of product
editions and file locations above for the name and location of
the specific file which should be removed.  This manual
workaround is only necessary for Fix Pack 5 and Fix Pack 7 and
it will be automatically corrected in future fix packs.

If SDK Fix Pack 3 is the highest SDK fix pack currently
installed, then the file should not be removed.

Problem summary

****************************************************************
* USERS AFFECTED:  Customers applying a WebSphere Application  *
*                  Server 7.0.0.5 SDK FixPack and onwards on   *
*                  top of their existing SDK 7.0.0.3 level     *
*                  will experience this issue.                 *
****************************************************************
* PROBLEM DESCRIPTION: When a WebSphere Application Server     *
*                      SDK FixPack of version 7.0.0.5 or       *
*                      greater is applied on top of an         *
*                      existing 7.0.0.3 SDK FixPack, the       *
*                      customer will experience a server       *
*                      startup issue when running in debug     *
*                      mode.                                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A new file was introduced in the WebSphere Application Server
7.0.0.3 SDK FixPack and was then removed from 7.0.0.5 SDK
FixPack onwards. Due to limitations in the packaging code this
file is not removed when the 7.0.0.5 SDK FixPack is applied,
therefore, the file will still exist in the system.
This file causes start up failures when running in debug mode.
The packaging code has been reworked to generate future
SDK FixPacks that will remove this file when it is applied on
top of the 7.0.0.3 SDK FixPack.

Problem conclusion

The code will be integrated into FixPack 7.0.0.11.

Temporary fix

Comments

APAR Information

APAR number
PM01997
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-11-23
Closed date
2010-03-12
Last modified date
2010-03-12

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
WEBS APP SERV N
Fixed component ID
5724H8800

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:
25 October 2021

Tips

PM01997: WHEN USING SDK 64-BIT FIX PACK 5 AND 7, THE APPLICATION SERVER'SJVM MAY CRASH UPON STARTUP WHEN CONFIGURED TO RUN IN DEBUG MODE

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?