PI80225: JUL Traces do not show up in logstash collector / bluemix log collector when binary logging is enabled

Fixes are available

APAR status

Closed as program error.

Error description

When binary logging is disabled, trace logs for custom
applications using the JUL(java.util.logging) package are
pushed to logstashcollector, but when binary logging is
enabled, they do not appear.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  Liberty - HPEL Tracing in combination with  *
*                  Liberty Log Collector features              *
****************************************************************
* PROBLEM DESCRIPTION: JUL Traces do not show up in logstash   *
*                      collector / bluemix log collector when  *
*                      binary logging is enabled for trace     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When binary logging is disabled, trace logs for custom
applications using the JUL(java.util.logging) package are pushed
to logstashCollector or bluemixLogCollector, but when binary
logging is enabled, they do not appear.

Problem conclusion

The code path for JUL traces was fixed to enable them to be sent
to the respective log collectors.

The fix for this APAR is currently targeted for inclusion in fix
pack 17.0.0.2.  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
PI80225
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-04-19
Closed date
2017-05-18
Last modified date
2017-05-18

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
WAS LIBERTY COR
Fixed component ID
5725L2900

Applicable component levels

RCD0 PSY
UP

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

Document Information

Modified date:
03 May 2022

Tips

PI80225: JUL Traces do not show up in logstash collector / bluemix log collector when binary logging is enabled

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

RCD0 PSY

Document Information

Share your feedback

Need support?