-
Notifications
You must be signed in to change notification settings - Fork 2
remove JDK v1.8.252 requirement #408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR removes the JDK version 1.8.252 minimum requirement that previously prevented the agent from initializing on older Java 8 patch versions. The agent now allows execution on any Java 8 or higher runtime, with profiling features conditionally disabled for versions below 1.8.252.
Key Changes:
- Removed JDK version check from agent initialization logic
- Added conditional profiling activation based on JDK version
- Updated warning messages to clarify profiling-specific version requirements
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| AutoConfigurationCustomizerProviderImpl.java | Removed version check that disabled entire agent; replaced with profiling-specific warning |
| DeclarativeLoader.java | Removed agent disablement logic; kept profiling version warning |
| SolarwindsTracerProviderCustomizer.java | Added conditional profiling span processor registration based on JDK version |
| CustomConfigCustomizerProvider.java | Added JDK version check before adding profiling processor |
| SolarwindsAgentListener.java | Added JDK version check before profiler initialization; removed system monitor code |
| AutoConfigurationCustomizerProviderImplTest.java | Added teardown to reset static agentEnabled field between tests |
| CustomConfigCustomizerProviderTest.java | Added tests verifying profiling processor conditional registration |
| SolarwindsTracerProviderCustomizerTest.java | New test file verifying profiling span processor conditional behavior |
...rwinds/opentelemetry/extensions/config/provider/AutoConfigurationCustomizerProviderImpl.java
Show resolved
Hide resolved
custom/src/main/java/com/solarwinds/opentelemetry/extensions/config/DeclarativeLoader.java
Show resolved
Hide resolved
cheempz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @cleverchuk esp. for the pre 252 patch adhoc test link!
| } | ||
| }.buildMonitors()); | ||
| logger.debug("Started System monitor"); | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Above is no longer needed AO-style metrics code, correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mainly tace.jvm.* metrics.
Context:
This PR removes the previous restriction that required users to run the SolarWinds APM Java agent on JDK version 1.8.252 or higher. Previously, the agent would fail to initialize on older Java 8 patch versions due to the
JavaRuntimeVersionCheckervalidation. This validation is removed and users can now run the agent on any Java 8 or higher runtime without encountering initialization failures due to patch version restrictions with the caveat thatProfilingis permanently disabled for versions before1.8.252Test Plan:
Regression plus additional test and manually on JDK
1.8.242Test services data