newrelic / newrelic/newrelic-java-agent
[Spike] Investigate options for WildFly with Caffeine 3
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 240
- Forks
- 170
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 21
Description
We've seen boot failures when using WildFly 26 with the Java Agent's Caffeine 3 updates.
Reference: https://new-relic.atlassian.net/browse/NR-593852
First option was to set -Dorg.wildfly.logging.skipLogManagerCheck=true, we believe this would work, but customers may be concerned about effects on WildFly's operations.
Solution, for now, was to set -Dnewrelic.config.collectionfactory.forcev2=true. This solution will not be an option once we have fully removed Caffeine v2.
We should investigate options other than skipLogManagerCheck to support removal of Caffeine 2.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the WildFly 26 boot failure with the Java Agent's Caffeine 3 updates and review the referenced NR-593852 investigation. Compare alternatives to -Dorg.wildfly.logging.skipLogManagerCheck=true, including the current forcev2 workaround and its operational effects. Done means documenting a viable option for removing Caffeine 2 without relying on skipLogManagerCheck.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100