Fixes are available
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
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
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
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
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
After a fresh server start, it looks like if customers has the Trace Output set to None in the Configuration tab, and switches to the Runtime tab, the Runtime tab will show Memory Buffer as the trace output type, which is incorrect, as it should be set to None, similar to the Configuration tab. Note: This issue only happens after a fresh server start, during the life cycle of the server, the runtime trace output can be explicitly set to other trace outputs (Memory Buffer or File), and it will get set correctly.
Local fix
Manually change the trace option.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server. * **************************************************************** * PROBLEM DESCRIPTION: The runtime trace output tab shows * * Memory * * Buffer, instead of None, if None is set * * in * * the configuration trace output tab in * * the * * Administrative Console. * **************************************************************** * RECOMMENDATION: * **************************************************************** When the server is started with the configuration trace output tab set to None, the runtime trace output will be always set to Memory Buffer in the Administrative Console. In the runtime trace output tab, if the Memory Buffer output is set from None, the specified Memory Buffer size does not get preserved.
Problem conclusion
Additional logic was added to the code to set the correct runtim trace output reflecting the configuration trace output tab, at t server start up. Also, the code was fixed to preserve the specif Memory Buffer size, when the runtime trace output is changed fro None to Memory Buffer. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.45, 8.0.0.15, 8.5.5.13, 9.0.0.6. Please refer to Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI87581
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-09-19
Closed date
2017-11-15
Last modified date
2017-11-15
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
R900 PSY
UP
Document Information
Modified date:
04 May 2022