Return-Path: X-Original-To: apmail-geode-issues-archive@minotaur.apache.org Delivered-To: apmail-geode-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E7406183E2 for ; Fri, 1 Apr 2016 19:19:27 +0000 (UTC) Received: (qmail 10604 invoked by uid 500); 1 Apr 2016 19:19:27 -0000 Delivered-To: apmail-geode-issues-archive@geode.apache.org Received: (qmail 10570 invoked by uid 500); 1 Apr 2016 19:19:27 -0000 Mailing-List: contact issues-help@geode.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.incubator.apache.org Delivered-To: mailing list issues@geode.incubator.apache.org Received: (qmail 10561 invoked by uid 99); 1 Apr 2016 19:19:27 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Apr 2016 19:19:27 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 7303A18054A for ; Fri, 1 Apr 2016 19:19:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.021 X-Spam-Level: X-Spam-Status: No, score=-4.021 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 1JzFUfB-QnZi for ; Fri, 1 Apr 2016 19:19:26 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with SMTP id 4A81E5F477 for ; Fri, 1 Apr 2016 19:19:26 +0000 (UTC) Received: (qmail 10219 invoked by uid 99); 1 Apr 2016 19:19:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Apr 2016 19:19:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 7AE142C1F5A for ; Fri, 1 Apr 2016 19:19:25 +0000 (UTC) Date: Fri, 1 Apr 2016 19:19:25 +0000 (UTC) From: "Bruce Schuchardt (JIRA)" To: issues@geode.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (GEODE-1160) TransactionWriter is unexpectedly triggered if updating data entries with using PDX serializer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Bruce Schuchardt created GEODE-1160: --------------------------------------- Summary: TransactionWriter is unexpectedly triggered if updating data entries with using PDX serializer Key: GEODE-1160 URL: https://issues.apache.org/jira/browse/GEODE-1160 Project: Geode Issue Type: Bug Components: serialization Reporter: Bruce Schuchardt It has been reported that TransactionWriters are being invoked for operations on the PDX type registry. The writer may see unexpected events containing internal PDX metadata. #Start a transaction #perform a put() on a Region with a PDX serializable object PDX Serialization will suspend the transaction and distributed metadata concerning the value object in its own transaction. When the PDX transaction commits any TransactionWriters (or TransactionListeners) will be invoked with the PDX TransactionEvents. Once the PDX transaction completes the original transaction is resumed and the put() is allowed to complete. Transaction listeners and writers shouldn't be invoked for the PDX events - just the original put() operation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)