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
#505 is not fixed when TxType is REQUIRES_NEW #667
Milestone
Comments
Hi, thanks for raising that again, we'll take a look. |
This is reproducible but only when using a Datasource. When used with a JPA EntityManager the transaction is rolled back correctly. |
Thank you so much! |
Cousjava
added a commit
to Cousjava/Payara
that referenced
this issue
Aug 21, 2019
…#667) PAYARA-3822 Ensure AMX Bean is created for metrics after server start Approved-by: Jan Bernitt <jan.bernitt@payara.fish> Approved-by: Andrew Pielage <andrew.pielage@payara.fish>
arieki
pushed a commit
to arieki/Payara
that referenced
this issue
Nov 15, 2022
FISH-6603 : META-INF must not be always denied
Pandrex247
pushed a commit
that referenced
this issue
Feb 17, 2023
FISH-6603 : META-INF must not be always denied
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm very happy with Payara 4.1.1.161 released.
I wrote issue #505 .
I tried Payara 4.1.1.161, and I saw this bug is fixed when TxType is
REQUIRED
.But, it seems this bug is NOT fixed when TxType is
REQUIRES_NEW
.Could you try my test program again?
https://github.com/MasatoshiTada/TransactionalSample-Doma/blob/master/src/main/java/com/example/jdbc/JdbcCdiRequiresNewTestDao.java
The text was updated successfully, but these errors were encountered: