Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Future consideration
Workspace WebSphere Liberty
Created by Guest
Created on Feb 23, 2024

Extend the scope of the maxFiles parameter in logging configuration

As per case TS015417399 when configuring <accessLogging> with maxFiles in WebSphere Liberty the server only deletes old logs of more that maxFiles logs have been created by the currently running process.


The current behavior makes the maxFiles settings of limited use only of the server is periodically restarted as the logs for the previous run are not cleaned up. Therefore the filesystem fills up and we need another mechanism (for example cronjob) to cleanup the old logs.

The idea is to improve the log cleanup function in a way so that the running server checks all logs matching the configured pattern in the log output directory and deletes older files not matter if they were created by another process or not if the number of logs found exceeds maxFiles .

Idea priority Medium