[BUG] Jackson-Dependency upgrade causes EventHub communication to fail without any visible reason
See original GitHub issueDescribe the bug
After adding dependency com.fasterxml.jackson.dataformat:jackson-dataformat-xml:2.12.0
to our project we are no longer able to successfully register a EventHubProcessorClient.
Turning on tracing logs did not give any insight about the cause of the problem.
To Reproduce https://github.com/quandor/azure-dependency-problems contains code and instructions
Expected behavior Clear message in logs about error condition.
** Setup information **
- OS: Linux (5.10.11-arch1-1)
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Troubleshoot connectivity issues - Azure Event Hubs
There are various reasons for client applications not able to connect to an event hub. The connectivity issues that you experience may be ......
Read more >Event Hubs Dead Letter Queue with Spring Cloud Stream
A dead letter queue can help us avoid data loss while still being able to ... Consider message M causes an error while...
Read more >Event Hub Throttling with the error: request was terminated ...
The request was terminated because the entity is being throttled. Error code : 50002. Sub error : 102. Can someone let me know...
Read more >Azure Event Hubs Are Not Queues - Tinkerer
Messages Block The Queue · Checkpointing Makes Error Handling Hard(er) · Event Hubs Require An Extra Storage Account · Local Development · Reasons...
Read more >Error to connecting event hub Azure cloud - Forums - IBM
I'm trying to fix an issue with the IBM connector for Azure Event Hub. Take a look about my configuration: I have no...
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
Thanks @brunoborges and @alzimmermsft, I can confirm that upgrading to azure-bom 1.0.3 solves the issue for us in Camel Quarkus https://github.com/apache/camel-quarkus/pull/2758
Hi @brunoborges, yes, there was an issue before where Jackson 2.11 and 2.12 had implicit serialization/deserialization differences which resulted in regressions for some SDKs. These issues have since been resolved and the Azure SDKs using
azure-core 1.14.1
or later should be able to use either Jackson 2.11 or 2.12.Looking forward, we are investigating new patterns and version shimming to support a wider breadth of Jackson versions to prevent future scenarios such as this.