PK15035: Memory leak in InvocationCache (Replacement
for PK12027)
Downloadable files
Abstract
Memory leak in InvocationCache after applying WebSphere®
Application Server Fix Pack 5.02.12, 5.02.13, 5.02.14 OR 5.1.1.6
(Replacement for PK12027).
Download Description
PK15035 resolves the following problem:
ERROR DESCRIPTION:
AFTER installing PK12027, depending on which version of WebSphere
Application Server, you may receive the following:
WebSphere Application Server V5.0.2.12, V5.0.2.13 and V5.0.2.14:
Out Of Memory due to invocationCache
WebSphere Application Server 5.1.1.6:
5.1.1.6 if PK12027 has been applied than ... customer will see the
following exception:
[10/12/05 14:33:07:111 MEST] 110e0ec WebAppInvoker E Unexpected
internal engine error while processing request:
java.lang.NullPointerException
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:273)
at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handle
Invocation(CachedInvocation.java:71)
at
com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:120)
THIS PROBLEM IS ALREADY BEEN FIXED IN WAS V5.1.1.7
PROBLEM SUMMARY:
USERS AFFECTED:
WebSphere Application Server users of version 5.0.2.12, 5.0.2.13, 5.0.2.14
and 5.1.1.6.
PROBLEM DESCRIPTION:
After upgrading to WebSphere Application Server Fix Pack 5.1.1.6,
5.0.2.12, 5.0.2.13 or 5.0.2.14 and applying PK12027 interim fix, a memory
leak has been found in Invocation Cache which leads to an OutOfMemory
situation.
RECOMMENDATION:
PROBLEM CONCLUSION:
This interim fix resolves the OutOfMemory in InvocationCache for levels
5.0.2.12, 5.0.2.13, 5.0.2.14 & 5.1.1.6. This will also resolve the
NullPointerException caused due to the incomplete interim fix PK12027 for
version 5.1.1.6. Please Note this is a replacement APAR only for PK12027
interim fix. The Cumulative fix pack which includes PK12027 need not apply
this fix. This fix will not be made part of any cumulative fix pack.
Circumvention:
LOCAL FIX 1:
Temporary work around 1:
Setting invocation cache size to 0 will disable invocation cache
functionality and there will be no more caching of WebAppInvoker objects.
This can be set as follows:
(1) In the administrative console, click the application server.
(2) Click Process Definition under Additional Properties.
(3) Click the Java Virtual Machine under Additional Properties.
(4) Add the following argument in the Generic JVM arguments:
-DinvocationCacheSize=0
(5) Click Apply to ensure that the changes are saved.
(6) Stop and restart the application server.
LOCAL FIX 2:
If invocation cache size can not be set to 0, this issue can be avoided by
setting the minimum thread pool size the same as the maximum thread pool
size and setting growable to false. To make these changes, perform the
following:
(1) In the administrative console, click the application server.
(2) Click Web Container under Additional Properties.
(3) Click Thread pool under Additional Properties.
(4) Change Minimum size same as Maximum size.
(5) UnCheck IsGrowable.
(6) Click Apply to ensure that the changes are saved.
(7) Stop and restart the application server.
Prerequisites
Please download the UpdateInstaller below to install this fix.