Log aggregation of repeated application runtime exceptions

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 <charters@uk.ibm.com>.

Hi,

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.

Thanks,
Harry Thomas

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.