Skip to content
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.

Sign up for GitHub

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

Jump to bottom

JNI / classloader issues #7

Closed
jpountz opened this issue Jan 9, 2013 · 0 comments
Closed

JNI / classloader issues #7

jpountz opened this issue Jan 9, 2013 · 0 comments
Labels
bug

Comments

@jpountz
Copy link
Collaborator

jpountz commented Jan 9, 2013

A JNI library can only be loaded once per classloader, so if any classloader which is not a child of the classloader which loaded the JNI library tries to use the JNI version, it will fail. This can be a problem with servlet containers.

snappy-java has a hack to inject bytecode into the root classloader but I'm not sure this is the way to go...

If not fixable, I think we should either document this behavior or forbid loading the JNI lib from a non-root classloader?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jpountz