Failed to load class from SLF4J on startup
See original GitHub issueEvery time that neow3j is used/loaded as a library, the user sees the following in the output:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
It would be good to hide that or fix that class loading.
- Write about neow3j’s usage of slf4j in the external docs.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:8 (8 by maintainers)
Top Results From Across the Web
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"
This warning message is reported when the org.slf4j.impl.StaticLoggerBinder class could not be loaded into memory. This happens when no ...
Read more >log4j2 - Failed to load class "org.slf4j.impl.StaticLoggerBinder"
The Java project is using log4j2, but look like some components are used SLF4J logging and caused the following error message:
Read more >Failed to load class "org.slf4j.impl.StaticLoggerBinder" when ...
SLF4J : Failed to load class "org.slf4j.impl.StaticLoggerBinder". This issue occurs when the port 1019 is used by some other process. The netstat ...
Read more >Failed to load class "org.slf4j.impl.StaticLoggerBinder"
In this post, we feature a comprehensive article about how to solve the error slf4j: Failed to load class “org.slf4j.impl.
Read more >[latest] Failed to load class "org.slf4j.impl.StaticLoggerBinder".
The application seems to still scrape CloudWatch, but I'm unable to debug properly due to the logging. Any way in which I can...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, true. We should document it in the extetnal docs. Let’s keep this issue open for that.
I added the dependency to logback to the neo3- and neo2-example projects. Thus, the error is not shown there anymore.