Fixes are available
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
When migrating from WebSphere Application Server 6.1, the PMI metrics logging option enableLog="false" is set to enableLog="true" if the traceLevel= option is not "NONE" Prior to migration , the primr.xmlfile for the 6.1 version and the version being migrated to show similar entry to: <pmirm:PMIRequestMetrics xmi:id="PMIRequestMetrics_1" dynamicEnable="true" enable="false" enableARM="false" traceLevel="HOPS" enableLog="false" armType="ARM40" armTransactionFactory="" armCallback=""> ... After migration, the post migration pmirm.xml contains: <pmirm:PMIRequestMetrics xmi:id="PMIRequestMetrics_1" dynamicEnable="true" enable="false" enableARM="false" traceLevel="HOPS" enableLog="true" armType="ARM40" armTransactionFactory="" armCallback="">
Local fix
Manually modify the entry in the PMIRM.xml file to enableLog="false"
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server using the migration tooling * * available. * **************************************************************** * PROBLEM DESCRIPTION: After running WASPostUpgrade * * Performance Monitoring Infrastructure * * (PMI) metrics logging becomes enabled * * when in the previous version it was * * not. * **************************************************************** * RECOMMENDATION: * **************************************************************** After running WASPostUpgrade, the enableLog attribute of the PMIRequestMetrics tag in pmirm.xml is set to true even though the same attribute in the previous release is set to false.
Problem conclusion
We now make sure that upon migration if a value is set for enableLog that it is honored and not replaced. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.31, 8.0.0.8, and 8.5.5.2. Please refer to the Recommended Updatespage for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Manually fix the enableLog value back to false if it was previously set to false in the pmirm.xml file in the new version of WebSphere Application Server.
Comments
APAR Information
APAR number
PM97904
Reported component name
WEBS LOAD BALAN
Reported component ID
5724H8811
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-09-26
Closed date
2013-10-11
Last modified date
2013-10-22
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
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
27 April 2022