You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2021/10/21 13:46:00 UTC
[jira] [Commented] (IGNITE-15732) Thin client: Tx can fail if there
are concurrent tx rollbacks by timeout
[ https://issues.apache.org/jira/browse/IGNITE-15732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432485#comment-17432485 ]
Ignite TC Bot commented on IGNITE-15732:
----------------------------------------
{panel:title=Branch: [pull/9504/head] Base: [master] : Possible Blockers (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Windows){color} [[tests 0 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=6233029]]
{panel}
{panel:title=Branch: [pull/9504/head] Base: [master] : New Tests (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Thin Client: Java{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=6231880]]
* {color:#013220}ClientTestSuite: FunctionalTest.testTxResumeAfterTxTimeout - PASSED{color}
{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=6231957&buildTypeId=IgniteTests24Java8_RunAll]
> Thin client: Tx can fail if there are concurrent tx rollbacks by timeout
> ------------------------------------------------------------------------
>
> Key: IGNITE-15732
> URL: https://issues.apache.org/jira/browse/IGNITE-15732
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Due to race between timeout worker and client-connector workers there can be situations when some transaction is processed by client-connector worker and concurrently rolled back by timeout worker. In this case, {{threadMap}} can still contain the reference to this transaction but the transaction state is already set to "ROLLED_BACK", for such a state client-connector worker does not suspend the transaction and can proceed to the next request, which uses another transaction. When resuming this second transaction there is an exception thrown, since {{IgniteTxManager#threadMap}} is not cleared yet for the current worker thread:
> {noformat}
> org.apache.ignite.client.ClientException: Ignite failed to process request [103]: Thread already has started a transaction. (server status code [1]){noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)