PM39875: FFDC EXCEPTION IN LOGS ARE NOT UPDATED IN SOME MULTI-THREADING.

Fixes are available

APAR status

Closed as program error.

Error description

FFDC exception in logs are not updated in some multi-threading
cases. The summary table won't be correctly reflected

When a runtime exception occurs in WPS 7.0.0.3, we sometimes see
that the ffdc-logs are created - but when the same error occurs
again, the exception.log is not updated with # occurrences. This
makes error analysis very difficult, as there will be just one
line in SystemOut.log without the stack trace - and no
indication that ffdc-logs for the error exists.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server using FFDC.                          *
****************************************************************
* PROBLEM DESCRIPTION: The FFDC summary file (ex:              *
*                      server1_exception.log) does not have    *
*                      the correct count for a given ffdc      *
*                      incident.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The FFDC summary is not always expected to be updated.  In this
particular case, however, it was discovered that there are
some cases (depending on the timing as it is a race
condition) where it is not possible for the count of a given
incident in the FFDC summary file to get updated at all
after the first incident, which is not the expected behavior.

Problem conclusion

The API (without breaking existing external implementations)
has been updated to allow for the summary check to be invoked
each time an incident is created or updated.  Please note that
there is still a criteria that needs to be met for the FFDC
summary file to be updated for a given incident.  The criteria
is:

1.  When there have been more than 10 incidents and at least a
minute has passed after the last time the summary table was
updated.

2.  It has been more than 5 minutes since the last time the
summary table was updated.


The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.19 and 8.0.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
PM39875
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-05-24
Closed date
2011-06-20
Last modified date
2011-06-20

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

PM39875: FFDC EXCEPTION IN LOGS ARE NOT UPDATED IN SOME MULTI-THREADING.

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?