Open jaridk opened 3 years ago
This issue has aged. The feature template should be updated when accepting this from the backlog.
Also, I believe the following has been addressed by subsequent changes to AppClassLoader to not throw ClassNotFoundException when searching for classes.
Removal of thrown ClassNotFoundExceptions (these generally are only useful if uncaught, and uncaught exceptions would typically already be logged)
Closing as superseded by https://github.com/OpenLiberty/open-liberty/issues/29690
Description of the high level feature, including any external spec links:
Liberty class loader trace is currently extremely verbose and thorough, but not always in ways that are amenable to efficiently debugging actual problems. It's not unusual for customer-submitted data sets to produce multiple gigabytes of logs, sometimes rolling over 100MB traces in a few seconds. Not only that, but the data that is produced is often difficult to use in the field due to some issues with how the data is presented, plus the fact that the verbosity leads to the data being spread over multiple log files (or lost altogether, if a customer doesn't have enough rollover logs configured).
This epic proposes a reworking of the Liberty class loader trace, including but not limited to the following changes:
Before proceeding to any items below (active development), this feature must be prioritized on the backlog, and have either the "Design Approved" or "No Design Approved" labels. Follow the Feature and UFO Approval Process.
When complete & mandatory, add links to the UFO (Upcoming Feature Overview) document, FTS (Feature Test Summary), and blogs post issues(s):
UFO:
FTS:
Beta Blog Post (if applicable):
Blog Post:
List of Steps to complete or get approvals / sign-offs for Onboarding to the Liberty release (GM date)
Instructions:
Design
Before Development Starts or 8 weeks before Onboarding
Beta
If your feature, or portions of it, are going to be included in a beta
Before Onboarding the beta
kind=beta
,ibm:beta
,ProductInfo.getBetaEdition()
)1 week before beta GA
Legal
3 weeks before Onboarding
Translation
3 weeks before Onboarding
Feature Complete
2 weeks before Onboarding
Focal Point Approvals
2 to 1 week before Onboarding
You MUST have the Design Approved or No Design Approved label before requesting focal point approvals.
All features (both "Design Approved" and "No Design Approved")
"Design Approved" features
Ready for GA
1 week before Onboarding
1 week before GA
Other deliverbles