[0.32.0] Getting Provider com.fasterxml.jackson.module.paranamer.ParanamerModule not found
See original GitHub issueWhen we upgraded from 031.2 to 032.0 we started getting this error:
Exception in thread "main" java.util.ServiceConfigurationError: com.fasterxml.jackson.databind.Module: Provider com.fasterxml.jackson.module.paranamer.ParanamerModule not found
at java.util.ServiceLoader.fail(ServiceLoader.java:239)
at java.util.ServiceLoader.access$300(ServiceLoader.java:185)
at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:372)
at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404)
at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
at com.fasterxml.jackson.databind.ObjectMapper.findModules(ObjectMapper.java:938)
at com.fasterxml.jackson.databind.ObjectMapper.findModules(ObjectMapper.java:921)
at com.fasterxml.jackson.databind.ObjectMapper.findAndRegisterModules(ObjectMapper.java:957)
at net.logstash.logback.composite.CompositeJsonFormatter.createJsonFactory(CompositeJsonFormatter.java:129)
at net.logstash.logback.composite.CompositeJsonFormatter.start(CompositeJsonFormatter.java:103)
at net.logstash.logback.encoder.CompositeJsonEncoder.start(CompositeJsonEncoder.java:211)
at ch.qos.logback.core.joran.action.NestedComplexPropertyIA.end(NestedComplexPropertyIA.java:161)
at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:309)
at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:193)
at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:179)
at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:62)
at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:165)
at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:152)
at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:110)
at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:53)
at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75)
at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150)
at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:84)
at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55)
at org.slf4j.LoggerFactory.bind(LoggerFactory.java:150)
at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:124)
at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:412)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:357)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:383)
We use logback-classic
(1.2.3) with logstash-logback-encoder
(6.1)
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
"Provider com.fasterxml.jackson.module.jaxb ... - Stack Overflow
I would look at your dependencies which might use xml as configuration. I am using Spring Boot 2.3.1 and did not need this...
Read more >ParanamerModule (Jackson-module-paranamer 2.7.0 API)
Convenience module that registers stand-alone ParanamerOnJacksonAnnotationIntrospector after existing introspectors, to add support for discovering names of ...
Read more >com.fasterxml.jackson : jackson-bom : 2.12.5 - Maven Central
Jackson BOM - Bill of Materials pom for getting full, complete set of compatible versions of Jackson components maintained by FasterXML.com.
Read more >com.fasterxml.jackson.module - Maven Repository
Add-on module for Jackson (https://github.com/FasterXML/jackson/) to support Kotlin ... and are not datatype, data format, or JAX-RS provider modules.
Read more >Maven build breaks 'Could not find artifact com.fasterxml ...
Digging into the matter I found that this pom https://maven.repository.redhat.com/ga/com/fasterxml/jackson/module/jackson-modules-java8/2.12 ...
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 Free
Top 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
Thank you for looking into this. We moved on with newer version of Jackson and have not had problems since.
Unfortunately, we haven’t reproduced the issue. The agent runs in its own classloader so there shouldn’t be contamination of the user classloader. The good news is that #1185 removes the Jackson dependency.