[
https://issues.apache.org/jira/browse/IGNITE-23541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julia Bakulina updated IGNITE-23541:
------------------------------------
Description:
It will be useful to add the info to the docs that the checks below are not
equivalent and for some cases the 2nd check should be chosen.
{code:java}
1) IgniteTxManager#checkEmptyTransactions(){code}
{code:java}
2) ctx.grid().transactions().tx() != null;{code}
The reason is that GridCacheMvccManager#pendingExplicit contains the mapping of
Thread ID to value using IgniteTxManager#checkEmptyTransactions.
was:
As GridCacheMvccManager#pendingExplicit contains the mapping of Thread ID to
value using IgniteTxManager#checkEmptyTransactions may lead to unexpected
behaviour of forbidding an operation.
It will be useful to add the info to the docs that the checks below are not
equivalent and for some cases the 2nd check should be chosen.
{code:java}
1) IgniteTxManager#checkEmptyTransactions(){code}
{code:java}
2) ctx.grid().transactions().tx() != null;{code}
> Extend description of IgniteTxManager#checkEmptyTransactions()
> --------------------------------------------------------------
>
> Key: IGNITE-23541
> URL: https://issues.apache.org/jira/browse/IGNITE-23541
> Project: Ignite
> Issue Type: Task
> Reporter: Julia Bakulina
> Assignee: Julia Bakulina
> Priority: Minor
> Labels: ise
>
> It will be useful to add the info to the docs that the checks below are not
> equivalent and for some cases the 2nd check should be chosen.
> {code:java}
> 1) IgniteTxManager#checkEmptyTransactions(){code}
> {code:java}
> 2) ctx.grid().transactions().tx() != null;{code}
> The reason is that GridCacheMvccManager#pendingExplicit contains the mapping
> of Thread ID to value using IgniteTxManager#checkEmptyTransactions.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
