]
Brian Stansberry moved JBEAP-16080 to WFLY-11543:
-------------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-11543 (was: JBEAP-16080)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JPA / Hibernate
(was: Hibernate)
(was: JPA / Hibernate)
Affects Version/s: 15.0.0.Final
(was: 7.3.0.CD15)
(was: 7.2.0.GA.CR3)
EJB transactional method unable to commit when invoked from CDI bean
with MariaDB
---------------------------------------------------------------------------------
Key: WFLY-11543
URL:
https://issues.jboss.org/browse/WFLY-11543
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 15.0.0.Final
Environment: WildFly 15.0.0.Final
MariaDB 10.1.19
Reporter: Michal Jurc
Assignee: Scott Marlow
Priority: Blocker
Issue cloned from the [community
forum|https://developer.jboss.org/thread/279303] for
tracking.
{quote}Hello,
We are having issues after deploying our application in the latest Wildfly 15.0.0 Final
recently released with the following exception:
java.sql.SQLException: XAER_RMFAIL: The command cannot be executed when global
transaction is in the IDLE state
The error occurs when our code calls a transactional EJB method that itself calls a
couple more injected SessionBean that handles the database persistence through an
EntityManager
The issue only seems to affect the MariaDB port and not oracle.{quote}
{quote}I have hit the same problem, migrated from Wildfly 10.0.0. to 15.0.0, using MySQL,
same error, similar situation, cdi managed bean that invokes 2 EJBs that use different
persistent units. I dont seem to have the problem in 14.0.1 either.
Another error that has surfaced is this (apologies for the weird formatting but struggled
to define a simple type-up without cluttering)
"javax.persistence.TransactionRequiredException: no transaction is in
progress"
Managed bean with injected ejb (with datasource2) and injected entitymanager for
datasource1, code is nested as follows
Managed bean method save @Transactional(value = TxType.REQUIRED)
{
ejb save @TransactionAttribute(TransactionAttributeType.MANDATORY)
{
persist
flush
}
find with lock => LockModeType.PESSIMISTIC_WRITE at this point the
"no transaction is in progress" exception is fired
}
Did notice that error does not occur if the invocation is purely ejb rather that cdi
managed bean {quote}