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
[Mongodb] NPE getting reactive client #11765
Comments
/cc @loicmathieu, @evanchooly |
I think I spot the possible source of the error though, going to submit a PR for your evaluation |
* Removing the reactive suffix in order to get the existing client (instead of getting null) * Changing anonymous classes to lambdas * Fixed the suppress warning with unused Closes quarkusio#11765
* Removing the reactive suffix in order to get the existing client (instead of getting null) * Fixed the suppress warning with unused Closes quarkusio#11765
Hello, |
+1 for what @loicmathieu says |
* Adding a flag to create named qualifier as reactive client or not * Fixed the suppress warning with unused Closes quarkusio#11765
Adding a flag to create named qualifier as reactive client or not Fixes: quarkusio#11765
Adding a flag to create named qualifier as reactive client or not Fixes: quarkusio#11765 (cherry picked from commit e73106f)
Describe the bug
When creating a named "blocking" client connection in a camel application (using quarkus extensions), I am hitting a NPE.
Expected behavior
Should not receive the NPE
Actual behavior
During startup, the application fail with the following exception:
To Reproduce
Steps to reproduce the behavior:
@Inject @MongoClientName("mongoClient1") MongoClient mongoClient1;
)Configuration
# Add your application.properties here, if applicable.
Screenshots
(If applicable, add screenshots to help explain your problem.)
Environment (please complete the following information):
uname -a
orver
: 5.4.0-42-generic Add proper logging #46~18.04.1-Ubuntu x86_64 x86_64 x86_64 GNU/Linuxjava -version
: openjdk version "11.0.7" 2020-04-14mvnw --version
orgradlew --version
): mvn 3.6.3Additional context
(Add any other context about the problem here.)
The text was updated successfully, but these errors were encountered: