Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B4EB2200C0F for ; Thu, 2 Feb 2017 14:25:55 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id B3739160B61; Thu, 2 Feb 2017 13:25:55 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 09265160B54 for ; Thu, 2 Feb 2017 14:25:54 +0100 (CET) Received: (qmail 87801 invoked by uid 500); 2 Feb 2017 13:25:54 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 87786 invoked by uid 99); 2 Feb 2017 13:25:53 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2017 13:25:53 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 9DCC81A0272 for ; Thu, 2 Feb 2017 13:25:53 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id yDplEVr6SRGX for ; Thu, 2 Feb 2017 13:25:53 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id B97945F3A1 for ; Thu, 2 Feb 2017 13:25:52 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 22378E023B for ; Thu, 2 Feb 2017 13:25:52 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 7F03B2528A for ; Thu, 2 Feb 2017 13:25:51 +0000 (UTC) Date: Thu, 2 Feb 2017 13:25:51 +0000 (UTC) From: "Pavel Tupitsyn (JIRA)" To: dev@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-4648) TransactionProxyImpl.prepare() does not wait for async operations to complete MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 02 Feb 2017 13:25:55 -0000 Pavel Tupitsyn created IGNITE-4648: -------------------------------------- Summary: TransactionProxyImpl.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 Priority: Minor Fix For: 2.1 {{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.3.15#6346)