From open-jpa-dev-return-1370-apmail-incubator-open-jpa-dev-archive=incubator.apache.org@incubator.apache.org Tue Dec 12 02:59:43 2006 Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 7971 invoked from network); 12 Dec 2006 02:59:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Dec 2006 02:59:42 -0000 Received: (qmail 88744 invoked by uid 500); 12 Dec 2006 02:59:49 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 88722 invoked by uid 500); 12 Dec 2006 02:59:49 -0000 Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: open-jpa-dev@incubator.apache.org Delivered-To: mailing list open-jpa-dev@incubator.apache.org Received: (qmail 88713 invoked by uid 99); 12 Dec 2006 02:59:49 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Dec 2006 18:59:49 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Dec 2006 18:59:41 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id F13C4714147 for ; Mon, 11 Dec 2006 18:59:20 -0800 (PST) Message-ID: <4393215.1165892360958.JavaMail.jira@brutus> Date: Mon, 11 Dec 2006 18:59:20 -0800 (PST) From: "Pinaki Poddar (JIRA)" To: open-jpa-dev@incubator.apache.org Subject: [jira] Created: (OPENJPA-88) Robustness of Distributed Cache Synchronization against transport outage MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Robustness of Distributed Cache Synchronization against transport outage -------------------------------------------------------------------------- Key: OPENJPA-88 URL: http://issues.apache.org/jira/browse/OPENJPA-88 Project: OpenJPA Issue Type: Improvement Components: datacache Reporter: Pinaki Poddar Assigned To: Pinaki Poddar OpenJPA provides pluggable mechanism to synchronize L2 caches of remote OpenJPA runtime. The commit events from one OpenJPA runtime can propagate to other remote OpenJPA runtime(s) on native providers that use TCP or JMS as transport or third-party distributed caching providers e.g. GemFire, Coherence etc. For native providers , specifically JMSRemoteCommitProvider, currently do not cope with transport outage. For example, consider the following scenario: 1. a JMS topic T on which OpenJPA is publishing its cache change events becomes unavailable 2. naturally, the cache changes are not transmitted to remote caches are not communicated to other caches during outage 3. JMS topic T becomes available again At this point, it is natural to expect that OpenJPA should restore connection to the JMS transport and continue transmitting commit changes. It is observed that OpenJPA does not restore connection and remains non-functional in the above scenario. The primary issue here is to extend current implementation with robustness against transport outage. A related issue is: how to handle the commit events that occur during outage? Two obvoius options are a) Remember every event that occurs during outage. Transmit these events when the connection is restored. b) Do not remember the events during outage. Transmit events that occur after the connection has been restored. At this point, the suggestions/views on these options are welcome. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira