PM44407: Thread name field can be missing in Advanced Format

Fixes are available

APAR status

Closed as program error.

Error description

When using the WebSphere Application Server Advanced log file
format with java.util.Logger.log(java.util.LogRecord) method,
the thread name does not appear in the log files.  All other
forms of Logger.log(..) output the thread name.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: Components or applications that log     *
*                      with java.util.logging and use a        *
*                      java.util.logging.LogRecord as a        *
*                      parameter to the log calls will not     *
*                      see a thread name field when viewing    *
*                      the log entries in ADVANCED format.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Components or applications that log with java.util.logging and
use a java.util.logging.LogRecord as a parameter to the log
calls (see example) will not see a thread name field when
viewing the log entries in ADVANCED format.
Example:
Logger logger =
Logger.getLogger("com.xyz.foo");
logger.log(new LogRecord(Level.INFO,
"INFO message"));
In WebSphere Application Server v8.0, the thread name will
also be missing when viewing log and trace with the ADVANCED
-format option of HPEL LogViewer.
The thread name had only been made available to Log Records
that are created by the WebSphere Application Server runtime.

Problem conclusion

If the thread name is not available from the Log Record, the
thread name will default to the current thread's thread name
that the log event was created in.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.21 and 8.0.0.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
PM44407
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-07-25
Closed date
2011-10-26
Last modified date
2011-10-26

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021

Tips

PM44407: Thread name field can be missing in Advanced Format

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?