-
-
Notifications
You must be signed in to change notification settings - Fork 806
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
IllegalAccessError for net.bytebuddy.dynamic.Nexus.NO_QUEUE #1179
Comments
Did you build the agent with the latest BB? This field is removed, the latest version should no longer expect it. |
I think the agent does not shade Byte Buddy into a different package, and there might be an older version of Byte Buddy already on the class path. The Nexus is not used in the agent, but I think this could explain the crash. |
@raphw Thanks for the reply, I am honestly not sure on your question so I cross-referenced this issue on their repo to maybe get some more expertise looking at this. Maybe them shading bytebuddy would be the best path forward here. If you have any other suggestions please let me know! |
Do you have BB on your class path? Try using the same version there as in the agent, as a backup. |
@raphw That is something else I'm not sure on. We tried to add this agent at a global level to our platform and a small % of applications failed, so my guess is that subset of apps probably do have an older version of BB on the classpath. I took a swing at updating the javagent to shade bytebuddy to avoid this conflict (since updating each of the individual apps would probably be a bummer). I'm not sure if you have any experience in this area, but if you'd be able to take a look that would be sweet: nccgroup/log4j-jndi-be-gone#7 (comment) |
Looks good but I'd choose a package in the same hierarchy: trust.nccgroup.jndibegone |
That's a good idea, I'll update 👍 |
@raphw just wanted to follow-up and let you know that shadowing worked. I appreciate all your help! |
This is maybe a duplicate of #616, but that was a couple years ago and the library we are using is a minimum version of 1.12.0.
We are using log4j-jndi-be-gone to help with some log4j mitigation. They are pointing to a minimum version of 1.12.0 https://github.com/nccgroup/log4j-jndi-be-gone/blob/main/build.gradle#L18
When running our application with the following
JAVA_OPTS
:We get the following in some of our applications:
Any help would be appreciated!
The text was updated successfully, but these errors were encountered: