Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "getdtablesize"
See original GitHub issueHi there
My client run task with android target fails with the below link error:
E/AndroidRuntime(19668): java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "getdtablesize" referenced by "/data/app/hello.hellodesktop-XiRilnh49ahx5XXKtJJqtg==/lib/arm64/libsubstrate.so"...
This specifically occurs when launching our enterprise jar with Assisted Configuration of Native Image Builds. I’m unfortunately unable to replicate the issue in a simple project
Env:
GraalVM CE 20.3.0-dev-20200814_0227 and it’s bundled Java 11
Ubuntu 16.04
Maven client plugin version 0.1.31
Any assistance would be greatly appreciated
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ok, looks like it could be added via JMX. Your log shows
org.apache.log4j.jmxandorg.apache.logging.log4j.core.jmx. Is there a way you can easily remove these dependencies and test again?I took the following steps to resolve the issue:
I disabled log4j JMX with a system property as per log4j documentation
We were using async loggers in our project. I made sure to disable them by removing the async logging system property and the Disruptor dependency as per log4j documentation
client:build was now failing with a ClassNotFound error. I explicitly added back the now unused Disruptor dependency as per this issue