[
https://issues.apache.org/jira/browse/IGNITE-28489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18072579#comment-18072579
]
Ignite TC Bot commented on IGNITE-28489:
----------------------------------------
{panel:title=Branch: [pull/12998/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/12998/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Thin Client: Java{color} [[tests
2|https://ci2.ignite.apache.org/viewLog.html?buildId=8992854]]
* {color:#013220}ClientTestSuite:
FunctionalTest.testTxResumeAfterTxTimeoutOnInitialize[useBinaryArrays = false]
- PASSED{color}
* {color:#013220}ClientTestSuite:
FunctionalTest.testTxResumeAfterTxTimeoutOnInitialize[useBinaryArrays = true] -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8992893&buildTypeId=IgniteTests24Java8_RunAll]
> GridNearTxLocal leaks thread state on transaction timeout during
> initialization
> -------------------------------------------------------------------------------
>
> Key: IGNITE-28489
> URL: https://issues.apache.org/jira/browse/IGNITE-28489
> Project: Ignite
> Issue Type: Task
> Reporter: Maksim Davydov
> Assignee: Maksim Davydov
> Priority: Major
> Labels: ise
> Time Spent: 40m
> Remaining Estimate: 0h
>
> A race condition or immediate timeout during transaction initialization can
> cause a _TransactionTimeoutException_. When this happens in
> _initTimeoutHandler_, the transaction is not properly cleared from the
> _threadMap_. Subsequent transaction attempts on the same thread may fail with
> the error: "Thread already has started a transaction."
> +Proposal+: Explicitly call cctx.tm().clearThreadMap(this); inside the
> timeout block in initTimeoutHandler to ensure the thread is cleaned up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
