[
https://issues.apache.org/jira/browse/IGNITE-4648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094311#comment-16094311
]
Ryabov Dmitrii commented on IGNITE-4648:
----------------------------------------
[~avinogradov], [~yzhdanov], [~ptupitsyn], I added boolean flag to
{{prepare()}} method.
[JTA|http://ci.ignite.apache.org/viewLog.html?buildId=733943&buildTypeId=Ignite20Tests_IgniteJta&tab=buildResultsDiv]
and
[.NET|http://ci.ignite.apache.org/viewLog.html?buildId=733942&tab=buildResultsDiv&buildTypeId=Ignite20Tests_RunAllNet]
tests are successfully completed.
> IgniteInternalTx.prepare() does not wait for async operations to complete
> -------------------------------------------------------------------------
>
> Key: IGNITE-4648
> URL: https://issues.apache.org/jira/browse/IGNITE-4648
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.7
> Reporter: Pavel Tupitsyn
> Assignee: Ryabov Dmitrii
> Priority: Minor
> Fix For: 2.2
>
>
> {{commit}} and {{rollback}} wait for async operations by calling
> {{tx.txState().awaitLastFut();}} (see {{GridCacheSharedContext}}).
> There is no such thing in {{IgniteInternalTx.prepare()}} implementations.
> Since {{prepare}} is an internal method, this is not an issue mostly, except
> for two things:
> * JTA. {{CacheJtaResource}} calls {{prepare()}} explicitly.
> * .NET {{TransactionScope}} API. Same thing as JTA, basically.
> {{PlatformTransactions}} call {{prepare()}} as well.
> As a result, if user starts an async operation within JTA transaction and
> then completes the tx, undefined behavior is possible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
