We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Investigate why Sonarqube 9.9 won't start up unless agent is run in lite_mode (further discussion on Sonarqube site here
Agent is able to properly run with Sonarqube 9.9 and above.
N/A
Support case and it looks like SonarQube isn't starting up (causes the app to crash)
The text was updated successfully, but these errors were encountered:
https://issues.newrelic.com/browse/NEWRELIC-9461
Sorry, something went wrong.
Verified that SQ Server 9.7 runs with the agent and SQ Server 9.9 breaks.
This was fixed by adding the following classes to excludes:
excludes
java/util/AbstractList$RandomAccessSpliterator java/util/stream/MatchOps$MatchOp java/util/stream/MatchOps$BooleanTerminalSink javax/security/auth/Subject$SecureSet$1
Update: The classes above were added to the default excludes file for the agent, so they will be excluded by default on the next release.
Until the next release, customers can manually exclude the classes in their newrelic.yml file:
newrelic.yml
class_transformer: excludes: ^java/util/AbstractList\$RandomAccessSpliterator, ^java/util/stream/MatchOps\$MatchOp, ^java/util/stream/MatchOps\$BooleanTerminalSink, ^javax/security/auth/Subject\$SecureSet\$1
kanderson250
Successfully merging a pull request may close this issue.
Description
Investigate why Sonarqube 9.9 won't start up unless agent is run in lite_mode (further discussion on Sonarqube site here
Acceptance Criteria
Agent is able to properly run with Sonarqube 9.9 and above.
Design Consideration/Limitations
N/A
Dependencies
N/A
Additional context
Support case and it looks like SonarQube isn't starting up (causes the app to crash)
The text was updated successfully, but these errors were encountered: