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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Apr 5, 2018

Log aggregation of repeated application runtime exceptions

This request is for improvement in WebSphere logging and tracing. Log aggregation of repeated application run time exceptions so that logs are not filled and rolled over. This is similar to FFDC logs where repeated exception stacks are not printed, rather the count is mentioned. This will benefit us, wherein repeated application runtime exceptions are not written to the log every time and fill the log space and thereby avoiding faster log rotation.

Idea priority High
RFE ID 118476
RFE Product WebSphere Application Server
  • Admin
    Graham Charters
    Oct 27, 2021

    Thank you for the suggestion. The requirement does have merit, but looking at it with respect to our total backlog of requests we do not see sufficient interest in this enhancement to merit delivery any time in the foreseeable future. Given the unlikelihood that we would deliver this, we are declining the request rather than leaving it in an uncommitted state for an extended period of time. If you would like to discuss this decision further, please contact Graham Charters <>.

  • Guest
    Apr 16, 2018


    As mentioned in the original description, major concern is about logs rolling over very fast when there is some kind of error scenario in one of the applications. There are multiple applications deployed in one application server and we do not want continuous error messages from one application to fill all the logs and thereby we miss some error logs from other applications. Hope it is clear now. This is something similar to what we have with FFDC. I'm not familiar with liberty functionality you have mentioned about.

    Harry Thomas

  • Guest
    Apr 14, 2018

    I realize this is a request about WAS traditional -- but Liberty has a way to shrink stack traces to avoid printing internal (IBM) classes. Would doing that in WAS traditional be sufficient to address this need? I have some concern over making logs difficult to deal with if you have to cross-reference to see the actual exception contents. I also have some concern that scanning all messages with exceptions to see which match previously known exceptions could make logging/tracing slow.