Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
When WebSphere Application Server is configured in "DEBUG" mode for Performance Monitoring Infrastructure (PMI) Request Metrics and using ARM agents causes a slow memory leak occurs. Heapdump may show the following as leak suspect when using Tivoli ITCAM Transaction Tracking, this is is due to WebSphere starting an Application Response Measurement (ARM) transaction but not ending properly. 455,392,408 (43%) [32] 20 class com/ibm/tivoli/tt/jdbc/JdbcStatementHook 0x34f714c0 455,376,064 (43%) [32] 23 class com/ibm/tivoli/tt/ArmTransaction 0x34f69650 455,367,680 (43%) [24] 3 com/ibm/tivoli/tt/MultiThreadTransactionStack 0x6dfd7a58 455,367,640 (43%) [192] 44 array of com/ibm/tivoli/tt/utilities/TransactionStack 0x6dfea258 454,878,816 (43%) [24] 2 com/ibm/tivoli/tt/utilities/TransactionStack 0x70085da8 43,840 (0%) [24] 2 com/ibm/tivoli/tt/utilities/TransactionStack 0x7482a818 27,360 (0%) [24] 3 com/ibm/tivoli/tt/utilities/TransactionStack 0x73d5b5e0 24,840 (0%) [24] 2 com/ibm/tivoli/tt/utilities/TransactionStack 0x73960e40 24,424 (0%) [24] 3 com/ibm/tivoli/tt/utilities/TransactionStack 0x7441e5a0 24,072 (0%) [24] 2 com/ibm/tivoli/tt/utilities/TransactionStack
Local fix
use PERFORMANCE-DEBUG mode instead DEBUG mode
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V6.1 and V7.0 * **************************************************************** * PROBLEM DESCRIPTION: Slow memory leak occurs when using * * PMI request metrics configured in * * "debug" mode. * **************************************************************** * RECOMMENDATION: * **************************************************************** Whenever request metrics are enabled with an external ARM agent it is observed that some ARM transactions are started but not stopped. This causes live objects to be left over on the heap. This creates a problem especially when the number of transactions is high causing a lot of ARM Transaction objects to be created but not discarded causing a memory leak. Note: In order to check if your request metrics is configured in Debug mode or not please follow the following steps Procedure 1)Open the administrative console. 2)Click Monitoring and Tuning > Request Metrics in the administrative console navigation tree. 3)Find Trace level in the configuration tab. 4)Check the trace level a)If it is set to perf_debug then your RM trace level is performance_debug. b)If it is set to Debug then your RM trace level is Debug level. c)If it is HOPS then you are RM trace level is set to HOPS level. Please refer to the following link for more information on RequestMetrics data collection http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com. ibm.websphere.nd.doc/info/ae/ae/uprf_settrace.html
Problem conclusion
The code has been modified such that ARM transaction objects which are created are discarded properly, avoiding the possibility of any memory leaks. The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.39 and 7.0.0.19. 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
PM34413
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-03-09
Closed date
2011-03-31
Last modified date
2011-12-05
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
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
Document Information
Modified date:
27 October 2021