[
https://issues.apache.org/jira/browse/DERBY-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474490
]
Julius Stroffek commented on DERBY-2360:
----------------------------------------
This makes sense, but I was not able to find this behavior in any
specification. Is it mentioned somewhere in JTA spec, JDBC or Derby spec? I was
not able to find this there. This behavior is not mentioned in jdk1.5 javadoc
where I would expect it to be.
What is the reason to notify the transaction manager by throwing an exception
in a case when the transaction manager knows that the resource is read-only
(because it knows the flag it passed to the call)? I would expect this
exception to be thrown only later in a call to commit function or in a similar
case.
> The XAResource.end(xid, XAResource.TMFAIL) does not work
> --------------------------------------------------------
>
> Key: DERBY-2360
> URL: https://issues.apache.org/jira/browse/DERBY-2360
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.3.0.0
> Environment: Solaris Nevada build 56, sun jdk 1.6
> Reporter: Julius Stroffek
> Assigned To: Julius Stroffek
>
> If I execute this peace of code
> Xid xid = createXid(9,11);
> xaRes.start(xid, XAResource.TMNOFLAGS);
> Statement stm = conn.createStatement();
> stm.execute("create table NumberTable2 (i int)");
> stm.execute("insert into NumberTable2 values (1)");
> xaRes.end(xid, XAResource.TMFAIL);
> xaRes.rollback(xid);
> I get the following exception
> 1)
> testXAConnection(org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest)javax.transaction.xa.XAException
> at org.apache.derby.jdbc.EmbedXAResource.end(EmbedXAResource.java:208)
> at
> org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest.testXAConnection(XATransactionTest.java:94)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at
> org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:76)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> at junit.extensions.TestSetup.run(TestSetup.java:25)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> at junit.extensions.TestSetup.run(TestSetup.java:25)
>
> If I change TMFAIL to TMSUCCESS, everything works. The end with TMFAIL shoudl
> do the same as with TMSUCCESS except that I can only rollback the transaction.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
