[
https://issues.jboss.org/browse/JBJCA-1374?page=com.atlassian.jira.plugin...
]
Scott Marlow closed JBJCA-1374.
-------------------------------
Resolution: Rejected
never mind, just reading the IJ 1.2 doc and we should already have:
{quote}
"
4.1.2. Allow obtaining connections during MARKED_FOR_ROLLBACK
IronJacamar doesn't allow to obtain a new connection once a
transaction is in
MARKED_FOR_ROLLBACK mode. This allows the container to fail eagerly, since any work after
that point is wasted anyway.
However, certain applications depends on getting a connection to perform work.
IronJacamar has a system property called ironjacamar.allow_marked_for_rollback
which can be set to true to enable this scenario.
Note, that an existing enlisted connection is allowed to be obtained. This can be
disallowed by
setting the system property
ironjacamar.allow_marked_for_rollback_fast_fail to true
{quote}
add option for disabling transaction_marked_rollback_only_fail_fast
check that throws "javax.resource.ResourceException: IJ000459: Transaction is not
active" error
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBJCA-1374
URL:
https://issues.jboss.org/browse/JBJCA-1374
Project: IronJacamar
Issue Type: Enhancement
Components: Core
Reporter: Scott Marlow
In my internal testing with Hibernate, I hit a problem with IronJacamar throwing
"javax.resource.ResourceException: IJ000459: Transaction is not active" error
when called to get a database connection from pool from a thread that has an active
transaction marked for rollback only.
The Hibernate jira is [
https://hibernate.atlassian.net/browse/HHH-12472], which we are
talking about changing. As well as WildFly jira
[
https://issues.jboss.org/browse/WFLY-10229] for a related bug.
Independent of the HHH-12472 + WFLY-10229 issues, I think it would be useful if there was
a data source deployment option (in WildFly standalone*.xml) or system property, for
disabling the IJ000459 check for rollback only transactions, as the IJ000459 check is not
always expected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)