[JBoss JIRA] (JBTM-1920) Blacktie TestTransactions test failed: REST-AT stricter?
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1920?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-1920.
-------------------------------
> Blacktie TestTransactions test failed: REST-AT stricter?
> --------------------------------------------------------
>
> Key: JBTM-1920
> URL: https://issues.jboss.org/browse/JBTM-1920
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie, REST
> Reporter: Gytis Trikleris
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.0.0.M6
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI...
> {code}
> Test Results:
> [exec] Run: 14 Failures: 10 Errors: 0
> [exec]
> [exec]
> [exec] 1) test: TestTransactions::test_basic (F) line: 90 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTxAvoid.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 2) test: TestTransactions::test_transactions (F) line: 94 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 3) test: TestTransactions::test_protocol (F) line: 125 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 4) test: TestTransactions::test_info (F) line: 165 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 5) test: TestTransactions::test_timeout1 (F) line: 217 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 6) test: TestTransactions::test_timeout2 (F) line: 261 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 7) test: TestTransactions::test_rollback (F) line: 285 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 8) test: TestTransactions::test_hhazard (F) line: 317 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 9) test: TestTransactions::test_RM (F) line: 345 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 10) test: TestTransactions::test_recovery (F) line: 486 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBTM-1950) NullPointerException during after completion in REST-AT coordinator
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1950?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1950:
--------------------------------
Fix Version/s: 5.0.0.M5
(was: 5.0.0.Final)
> NullPointerException during after completion in REST-AT coordinator
> -------------------------------------------------------------------
>
> Key: JBTM-1950
> URL: https://issues.jboss.org/browse/JBTM-1950
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: REST
> Reporter: Gytis Trikleris
> Assignee: Michael Musgrove
> Priority: Critical
> Fix For: 5.0.0.M5
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/TESTS=MAIN,jdk=jd...
> {code}
> [0m[31m09:35:11,468 ERROR [io.undertow.request] (default task-9) Servlet request failed HttpServerExchange{ PUT /rest-at-coordinator/tx/transaction-manager/0_ffffac118324_2d1b88f2_524694b3_f/terminator}: org.jboss.resteasy.spi.UnhandledException: java.lang.NullPointerException
> at org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:76) [resteasy-jaxrs-3.0.4.Final.jar:]
> at org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:212) [resteasy-jaxrs-3.0.4.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:149) [resteasy-jaxrs-3.0.4.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:372) [resteasy-jaxrs-3.0.4.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.4.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.4.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.4.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.4.Final.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1]
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13]
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:59) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13]
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13]
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13]
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13]
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13]
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:209) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:196) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:69) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:130) [undertow-servlet-1.0.0.Beta13.jar:1.0.0.Beta13]
> at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:614) [undertow-core-1.0.0.Beta13.jar:1.0.0.Beta13]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> Caused by: java.lang.NullPointerException
> at org.jboss.jbossts.star.service.Coordinator.removeTxState(Coordinator.java:483) [restat-api-5.0.0.M5-SNAPSHOT.jar:]
> at org.jboss.jbossts.star.resource.Transaction.afterCompletion(Transaction.java:326) [restat-api-5.0.0.M5-SNAPSHOT.jar:]
> at org.jboss.jbossts.star.resource.Transaction.afterCompletion(Transaction.java:305) [restat-api-5.0.0.M5-SNAPSHOT.jar:]
> at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:118) [narayana-jts-jacorb-5.0.0.M5-SNAPSHOT.jar:5.0.0.M5-SNAPSHOT (revision: 1aeb9)]
> at com.arjuna.ats.arjuna.AtomicAction.abort(AtomicAction.java:186) [narayana-jts-jacorb-5.0.0.M5-SNAPSHOT.jar:5.0.0.M5-SNAPSHOT (revision: 1aeb9)]
> at org.jboss.jbossts.star.service.Coordinator.terminateTransaction(Coordinator.java:438) [restat-api-5.0.0.M5-SNAPSHOT.jar:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_17]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_17]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_17]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_17]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) [resteasy-jaxrs-3.0.4.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:280) [resteasy-jaxrs-3.0.4.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:234) [resteasy-jaxrs-3.0.4.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:221) [resteasy-jaxrs-3.0.4.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.4.Final.jar:]
> ... 24 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBTM-1920) Blacktie TestTransactions test failed: REST-AT stricter?
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1920?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1920:
--------------------------------
Fix Version/s: 5.0.0.M6
(was: 5.0.0.Final)
> Blacktie TestTransactions test failed: REST-AT stricter?
> --------------------------------------------------------
>
> Key: JBTM-1920
> URL: https://issues.jboss.org/browse/JBTM-1920
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie, REST
> Reporter: Gytis Trikleris
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.0.0.M6
>
>
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI...
> http://172.17.131.2/view/Narayana+BlackTie/job/narayana/255/TESTS=BLACKTI...
> {code}
> Test Results:
> [exec] Run: 14 Failures: 10 Errors: 0
> [exec]
> [exec]
> [exec] 1) test: TestTransactions::test_basic (F) line: 90 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTxAvoid.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 2) test: TestTransactions::test_transactions (F) line: 94 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 3) test: TestTransactions::test_protocol (F) line: 125 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 4) test: TestTransactions::test_info (F) line: 165 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 5) test: TestTransactions::test_timeout1 (F) line: 217 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 6) test: TestTransactions::test_timeout2 (F) line: 261 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 7) test: TestTransactions::test_rollback (F) line: 285 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 8) test: TestTransactions::test_hhazard (F) line: 317 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 9) test: TestTransactions::test_RM (F) line: 345 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> [exec]
> [exec]
> [exec] 10) test: TestTransactions::test_recovery (F) line: 486 /home/hudson/workspace/narayana/TESTS/BLACKTIE/jdk/jdk7.latest/label/linux64el6/blacktie/tx/src/test/cpp/TestTransactions.cxx
> [exec] equality assertion failed
> [exec] - Expected: 0
> [exec] - Actual : -6
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBTM-1082) Emma not working on JDK7
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1082?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1082:
--------------------------------
Fix Version/s: 4.16.7
> Emma not working on JDK7
> ------------------------
>
> Key: JBTM-1082
> URL: https://issues.jboss.org/browse/JBTM-1082
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System, Testing
> Reporter: Tom Jenkinson
> Assignee: Ondřej Chaloupka
> Fix For: 4.16.7
>
>
> -Demma.enabled=true does not work on JDK7
> Testcase: testNullInput took 0.006 sec
> Caused an ERROR
> Expecting a stackmap frame at branch target 11 in method com.arjuna.common.util.propertyservice.StringPropertyReplacer.<init>()V at offset 4
> java.lang.VerifyError: Expecting a stackmap frame at branch target 11 in method com.arjuna.common.util.propertyservice.StringPropertyReplacer.<init>()V at offset 4
> at com.arjuna.common.tests.propertyservice.StringPropertyReplacerUnitTestCase.testNullInput(StringPropertyReplacerUnitTestCase.java:86)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBTM-1566) Expose timed delivery feature of hornetq in btenqueue
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1566?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1566:
--------------------------------
Fix Version/s: 5.0.0.M4
(was: 5.0.0.Final)
> Expose timed delivery feature of hornetq in btenqueue
> -----------------------------------------------------
>
> Key: JBTM-1566
> URL: https://issues.jboss.org/browse/JBTM-1566
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Affects Versions: 5.0.0.M2
> Reporter: Crispin Boylan
> Assignee: Crispin Boylan
> Fix For: 5.0.0.M4
>
>
> It would be good to be able to specify a delivery time for the message (either relative or absolute) in the btenqueue.
> on #jbossts it was discussed and apparently HornetQ does support this so it just needs to be exposed to the blacktie interface.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBTM-1481) Transaction::commit on an transaction that the reaper has tried to rollback but has a wedged resource will not raise an exception
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1481?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-1481.
-------------------------------
> Transaction::commit on an transaction that the reaper has tried to rollback but has a wedged resource will not raise an exception
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1481
> URL: https://issues.jboss.org/browse/JBTM-1481
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTS, Transaction Core
> Affects Versions: 4.6.1.CP13
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Priority: Critical
> Fix For: 4.6.1.CP14, 4.16.7, 4.17.4, 5.0.0.M2
>
> Attachments: JBTM-1481.patch, WedgedResourceDemonstrator.java
>
>
> If you are getting a wedged resource. What then happens is that we interrupt the original reaper thread that is calling XAResource::rollback on the wedged resource which because you are using JacORB and have an in progress call will generate a null pointer exception when the thread is interrupted (you can see this in my attached log file, it prints a stack trace where the logging didn't do so before) which generates a org.omg.CORBA.TRANSACTION_ROLLEDBACK exception.
> The problem is that after the reaper tries to rollback the transaction but stalls on a wedged resource, it is then possible for the app thread to unwedged and to do a JTA::commit() and not get an exception. Debugging through the code, it doesn't pose data integrity issues on the transaction as what is happening is that internally we are checking the status of the transaction:
> ./ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/coordinator/ArjunaTransactionImple.java:340
> And because the transaction is not RUNNING or ABORT_ONLY, we are:
> ./ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/orbspecific/coordinator/ArjunaTransactionImple.java:398:
> throw new INVALID_TRANSACTION(0, CompletionStatus.COMPLETED_NO)
> Which is all good so far but then ends up in:
> ./ArjunaJTS/jtax/classes/com/arjuna/ats/internal/jta/transaction/jts/TransactionImple.java:1425
> catch (INVALID_TRANSACTION e6)
> {
> /*
> * In JTS/OTS we can indicate that something was terminated by another thread.
> * JTA doesn't really prevent this, but ...
> */
>
> //throw new IllegalStateException(
> // jtaLogger.loggerI18N.getString("com.arjuna.ats.internal.jta.transaction.jts.invalidtx2"));
> }
> Where it appears at some point we would have thrown an exception but decided to make the call that this was not valid anymore.
> As I say, it doesn't pose data integrity implications to the specific transaction, but if your app thread unwedges and you then make a decision on the outcome of the transaction (send email, acknowledge success) then it would break the business rules of that application.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months