-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Quarkus 3.3.3 - injecting UserTransaction generates Jandex warnings on startup #36050
Labels
kind/bug
Something isn't working
Milestone
Comments
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 21, 2023
geoand
added a commit
that referenced
this issue
Sep 21, 2023
Don't register subresource for reflection based on their use as a return type
michelle-purcell
pushed a commit
to michelle-purcell/quarkus
that referenced
this issue
Sep 21, 2023
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Oct 3, 2023
…urn type Fixes: quarkusio#36050 (cherry picked from commit 5c37b57)
aloubyansky
pushed a commit
to aloubyansky/quarkus
that referenced
this issue
Oct 31, 2023
…urn type Fixes: quarkusio#36050 (cherry picked from commit 5c37b57)
holly-cummins
pushed a commit
to holly-cummins/quarkus
that referenced
this issue
Feb 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I'm upgrading our app from Quarkus 2.7 to Quarkus 3.3.3.
The app starts up fine, but we get tons of warnings regarding classes in jakarta.jms similar to this:
I've narrowed the problem down to injecting UserTransaction for manual transaction management in a few places.
It only seems to manifest itself when we have a sub-resource that injects UserTransaction somewhere. If we inject into a root level resource, e.g. GreetingResource I'm not seeing the warnings.
Expected behavior
No warnings on startup
Actual behavior
How to Reproduce?
I've attached a simple project here that demonstrates the issue:
jandex-transaction-issue.zip
Basic steps to reproduce the whole project.
@Transactional
method does not use the UserTransaction. It only needs to be injected to cause issues.Note:
In our real world app, we are injecting UserTransaction in a pure-Java business layer (separate Jar) that we try to keep Quarkus/framework-agnostic. So we'd rather not replace with QuarkusTransaction if possible. But the same problem exists just injecting it into the resource class.
Output of
uname -a
orver
Darwin Kernel Version 22.3.0
Output of
java -version
openjdk version "17.0.2" 2022-01-18 LTS
GraalVM version (if different from Java)
No response
Quarkus version or git rev
3.3.3
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: