Fixes are available
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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
In a WAS Liberty server, setting com.ibm.ws.logging.console.log.level=OFF should mean that no messages are written to the console (stdout). However, this is not the case as the following message is written: Launching defaultServer (CICS 5.2.0, WebSphere Application Server 8.5.5.1, WAS FOR Z/OS 8.5.5.1/wlp-1.0.4.cl50120140115-1704) on IBM J9 VM, version pmz6470sr6-20131015_01 (SR6) (en_US)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile * **************************************************************** * PROBLEM DESCRIPTION: Setting * * com.ibm.ws.logging.console.log.level * * =off still results in one line of * * output. * **************************************************************** * RECOMMENDATION: * **************************************************************** When setting com.ibm.ws.logging.console.log.level=off, Liberty still prints the product version into the console.log file.
Problem conclusion
When starting the Liberty profile server the printing of the product version in the console.log is now only output when the property has a value other than off. It should however be noted that the console.log is a redirect of the command shell's stdout and stderr when the server start command is issued. The com.ibm.ws.logging.console.log.level property only controls the Liberty profile's output, it does not prevent or alter the logging of the underlying JVM to stdout or stderr. As an example, if a jvm.options file was in use, specifying: -Xtrace:methods={com/ibm/ws/kernel/boot*,com/ibm/ws/config*},pr int=mt The JVM trace output would still be located in the console.log file even if com.ibm.ws.logging.console.log.level=off is set. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.3. 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
PI12546
Reported component name
LIBERTY - Z/OS
Reported component ID
5655W6514
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-02-26
Closed date
2014-05-13
Last modified date
2014-05-13
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
LIBERTY - Z/OS
Fixed component ID
5655W6514
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
28 April 2022