PI96735: ACCESS LOG "MAXFILES" ATTRIBUTE NOT WORKING AS INTENDED WITH VALUE OF 0

Fixes are available

APAR status

Closed as program error.

Error description

When "maxFiles" is set to 0, the max number of log files
that
will be kept stays at 1 instead of increasing indefinitely.

Local fix

```
Set "maxFiles" to a large number.
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server using NCSA Logging                   *
****************************************************************
* PROBLEM DESCRIPTION: Access Log "maxFiles" attribute not     *
*                      working as intended with value of 0     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When configuring the HTTP Access Logging, setting a value of 0
in the "maxFiles" attribute is meant to represent there is no
limit to the maximum number of log files to be kept. However,
setting the value to 0 caused roll over to not occur, which left
just one current file of unlimited size.

Problem conclusion

The HTTP Access Logging code was modified to correctly handle
setting "maxFiles" to a value of 0.

The fix for this APAR is currently targeted for inclusion in fix
pack 8.5.5.14, 9.0.0.9. This was fixed in Open Liberty by issue
#3103 (https://github.com/OpenLiberty/open-liberty/issues/3103),
which is included in WebSphere Liberty fix pack 18.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
PI96735
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-04-13
Closed date
2018-05-16
Last modified date
2018-05-16

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

RCD0 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":"CD0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
03 May 2022

Tips

PI96735: ACCESS LOG "MAXFILES" ATTRIBUTE NOT WORKING AS INTENDED WITH VALUE OF 0

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?