PM88643: TRACE STRING OPTIMIZATION ISSUE.

Fixes are available

APAR status

Closed as program error.

Error description

*=info:ORBRas:=all:*=info:WAS.J2C=all trace string optimize
the trace string back to just *=info:WAS.J2C=all .

The traceSpec is read left to right, so what is furthest out
(right) in the traceSpec has final say.  By putting *=info at
the end, that sets everything back to info level and undoes
anything done before it (*=xxx where xxx is any level at the
end will overRide all items before it.  If this were something
like *=info:PMGR=all:com.ibm.ws.sm.*=info then Runtime=all
would still be in affect.  But since the final clause is an
unqualified regular expression catching everything, it
overrides all clauses before.
For example :
*=info:PMGR=all:*=info:com.ibm.ws.sm.*=all with revert it back
to
*=info:WAS.j2c=all

This is working as designed but we should provide a
warning message when this happens.


When the optimization happens we should have a warning message
in the SystemOut.log (after optimizing the trace string) and in
the trace.log file.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7                                   *
****************************************************************
* PROBLEM DESCRIPTION: When a trace is applied in the          *
*                      configuration tab the trace string is   *
*                      optimized but not conveyed to the       *
*                      user.                                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a trace is applied in the configuration tab and the server
is restarted the trace string is optimized but it is not
conveyed to the user and creates an impression that the trace
string is not optimized.

Problem conclusion

A suitable message is displayed in logs which conveys that the
trace string is optimized.

The fix for this APAR is currently targeted for inclusion in
fix pack 8.5.5.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
PM88643
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
2013-05-08
Closed date
2013-08-22
Last modified date
2013-11-25

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

[{"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:
28 April 2022

Tips

PM88643: TRACE STRING OPTIMIZATION ISSUE.

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

Document Information

Share your feedback

Need support?