-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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.
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
[BUG] Jackson-Dependency upgrade causes EventHub communication to fail without any visible reason #18876
Comments
Hey, Thanks for reporting this issue. If you execute Since you explicitly referenced 2.12.0, maven picks it up first as part of its dependency resolution. If you use 2.11.3, it should work.
|
Thanks for the hint, we had figured out that already. Will you try to improve the runtime logs? It was a pretty hard and long time until found that one. |
@quandor Do you have an example of how we could improve the runtime logs? What were the errors you saw? |
After we recognized that eventhub communication did no longer work, we turned on debug logging. A sample out follows. To us this looks like there is trouble accessing the blob storage. But no indication what the cause may be. We just guessed after checking the dependencies that those conflicts might be a problem. After a couple of hours we finally found the problematic dependency. |
I can confirm the issue. Forcing Jackson to 2.11 may work as a short term workaround, but it is rather risky for us. We get Jackson 2.12.1 managed via Quarkus BoM and we'd prefer using the version they test with to avoid any surprises in the Quarkus stack. |
I can serve with a reproducer:
Expected: the test should pass with Jackson 2.12.1 too
Note that this impacts all users of Azure Java clients on Quarkus 1.12.0.Final that was released on Feb. 23 2021. Also note that without enabling the logging on the client via |
Any chance to check this, please? Staying with Jackson 2.11 is not tenable in the long term. |
Reminding friendly that this issue exists and that end users on Quarkus 2.12 and 2.13 are facing it. |
I would like to ask if there are any chances of fixing this issue? In my company, we are developing a project based on the Quarkus. We would like to choose Azure Event Hub for the messaging. This issue prevents us from using the Event Hub in our project. The workaround of staying on the old Jackson library is too risky for us. |
@JonathanGiles @conniey is it possible to soft dependency on Jackson so users can more easily transition to a later version, or is it because there is a hard dependency on 2.11.2, where 2.12+ breaks compatibility? |
@alzimmermsft may be able to provide more information on this because he's working on Jackson. |
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 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. |
Thanks @brunoborges and @alzimmermsft, I can confirm that upgrading to azure-bom 1.0.3 solves the issue for us in Camel Quarkus apache/camel-quarkus#2758 |
Hi @quandor. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “ |
Describe 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 **
The text was updated successfully, but these errors were encountered: