Fixes are available
APAR status
Closed as program error.
Error description
If whitespace is included in the trace specification then the TRAS0018I message in messages.log will display a trace specification that does not match what was specified in server.xml or bootstrap.properties. If the trace specification is set to *=all=enabled then a StackOverflowError will be reported in console.log, and the server may fail to start.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile enabling trace * **************************************************************** * PROBLEM DESCRIPTION: If white space is present in a custom * * trace specification string, some * * specified elements will not be * * activated. Any logs requested by IBM * * support will be incomplete due to * * incorrect parsing of the element. * * Use of the *=all=enabled trace string * * in server.xml will cause a * * StackOverflowException, and may * * prevent the server from starting. * **************************************************************** * RECOMMENDATION: * **************************************************************** A customer might specify a trace string similar to the following: traceSpecification="*=info=enabled: woops=all=enabled" The resulting trace string shown in the TRAS0018I message will not match the specified order. All elements containing whitespace will be ignored, or applied incorrectly to prevent matching against a real trace element. Multiple nested calls to Tr.entry results in errors trying to trace the entry to the method creating the output stream. The StackOverflowException will be triggered by repeated calls to Tr.entry() and LauncherDelegateImpl$1.createOutputStream.
Problem conclusion
All elements of the trace specification are now trimmed as they are read. Methods for creating the log files were marked Trivial to prevent adding of entry/exit trace to avoid a repeated loop caused by tracing the creation of the log file that is triggered when all trace is enabled. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.0.1. 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
PM70303
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-08-06
Closed date
2012-09-14
Last modified date
2012-09-14
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 PROFILE
Fixed component ID
5724J0814
Applicable component levels
R850 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 October 2021