PI64662: WHEN APPLICATION SERVER AND NODEAGENT RESTART, BUNDLE CACHE IS RE-EXPANDED

Fixes are available

APAR status

Closed as program error.

Error description

In a WAS Network Deployment environment, all the managed
application servers and the nodeagent are re-expanding the
OSGi bundle cache on startup.  This is unnecessary and occurs
regardless of whether the bundle needs to be re-expanded.

If the bundles in the OSGi bundle cache contain shared
libraries this can cause a segmentation fault on some platforms
and the JVM may terminate.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server users of OSGi  *
*                  applications                                *
****************************************************************
* PROBLEM DESCRIPTION: A managed application server fails      *
*                      due to a segmentation fault when        *
*                      another application server on the       *
*                      same node starts.                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In a WAS Network Deployment environment, all the managed
application servers and the nodeagent re-expand the OSGi
bundle cache on startup.  This is unnecessary and occurs
regardless of whether the bundle needs to be re-expanded.
When the bundle is re-expanded, it is first deleted from the
expandedBundles directory and then re-expanded. On some
platforms if the bundles in the OSGi bundle cache contain
shared libraries this can cause a segmentation fault in
processes that are currently using the deleted shared library
and those JVMs may terminate.

Problem conclusion

The OSGi component was modified so that managed application
servers in a Network Deployment environment do not perform the
OSGi bundle cache expansion process. In such an environment
this task is performed only by the nodeagent.

The fix for this APAR is currently targeted for inclusion in
fix packs 8.5.5.11 and 9.0.0.2.  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
PI64662
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-06-21
Closed date
2016-07-01
Last modified date
2016-07-01

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

R850 PSY
UP
R900 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI64662: WHEN APPLICATION SERVER AND NODEAGENT RESTART, BUNDLE CACHE IS RE-EXPANDED

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

R850 PSY

R900 PSY

Document Information

Share your feedback

Need support?