Return-Path: Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: (qmail 98091 invoked from network); 17 May 2010 21:09:51 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 17 May 2010 21:09:51 -0000 Received: (qmail 70541 invoked by uid 500); 17 May 2010 21:09:50 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 70495 invoked by uid 500); 17 May 2010 21:09:50 -0000 Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@openjpa.apache.org Delivered-To: mailing list users@openjpa.apache.org Received: (qmail 70486 invoked by uid 99); 17 May 2010 21:09:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 May 2010 21:09:50 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [76.13.13.42] (HELO smtp103.prem.mail.ac4.yahoo.com) (76.13.13.42) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 17 May 2010 21:09:42 +0000 Received: (qmail 18697 invoked from network); 17 May 2010 21:09:21 -0000 Received: from cpe-174-099-058-061.nc.res.rr.com (dwoods@174.99.58.61 with plain) by smtp103.prem.mail.ac4.yahoo.com with SMTP; 17 May 2010 14:09:20 -0700 PDT X-Yahoo-SMTP: sCI.ryiswBB7FW.DxjU523c87MI- X-YMail-OSG: VqyydVgVM1m_WscIgv8m0.fekSBrOMgic1Wi.1NW4uWrPGsB4B_xetNJWopvPAHTXko5gAwHuVjknHvTN561cggyuMGszMPgqZ.Qo0Xg3py9ahEprZ6D6uCYlZU6VrTdiChAfEb_gosxzDOolRKNu3h_2TPBp_m5h.vMJyepuCwiE0fpLPXEc1yM1GtzADjYRO53m98hc3gy2kTLpblmj99ckljaSFitcStnRfYM5WPsZA50TDiTCZitiTmYK7kY_jvZsFTcPZtwQ5QE_kPzf1b1ql7gQK9tYHWll2rpM8d.gK3HdJh3Vfp4zLlvbw-- X-Yahoo-Newman-Property: ymail-3 Message-ID: <4BF1B080.3080704@apache.org> Date: Mon, 17 May 2010 17:09:20 -0400 From: Donald Woods User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 MIME-Version: 1.0 To: users@openjpa.apache.org Subject: Re: configure RemoteCommitProvider for Amazon EC2 References: In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 5/17/10 5:20 AM, Oliver Krohne wrote: > Hi, > > we are going to deploy our app to Amazon EC2. > One issue is that the ip-adresses of an ec instance can change and new ec instances > can be started which makes the RemoteCommitProvider using TCP unuseable as all > TCP adresses where messages are sent to must be configured at the point the > instance is starting. New instances can't be added without reconfiguring the running ec instances. What about the Amazon Simple Queue Service (SQS)? > > Using JMS as transport would work but i don't want a another machine running and hence a new point of failure. > But I would be thankful for any experience using JMS (openjms or activemq?). I've only used ActiveMQ as a JMS provider in Apache Geronimo, but it does have robust discovery and fail-over mechanisms. http://activemq.apache.org/configuring-version-5-transports.html http://activemq.apache.org/networks-of-brokers.html http://activemq.apache.org/failover-transport-reference.html > > So am thinking of using jgroups were new instances can join a channel, but I did not found someone > who has implemented it, maybe in this mailinglist? > > The other solution would be using ehcache with jgroups replication and > just replicate "removes and updates". Does anyone have experience with this setup? To use ehcache, you'd need to create a EhcaheRemoteCommitProvider that can instantiate a CacheManager and Cache based on a XML configuration file. I've opened OPENJPA-1669 and started looking at creating one for trunk :-) -Donald > > > Thanks, > Oliver