From dev-return-71915-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Mon Feb 16 20:05:03 2009 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 39594 invoked from network); 16 Feb 2009 20:05:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Feb 2009 20:05:02 -0000 Received: (qmail 37901 invoked by uid 500); 16 Feb 2009 20:05:02 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 37424 invoked by uid 500); 16 Feb 2009 20:05:01 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 37415 invoked by uid 99); 16 Feb 2009 20:05:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Feb 2009 12:05:01 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [209.174.123.75] (HELO dubrium.sys.ma.cait.org) (209.174.123.75) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Feb 2009 20:04:51 +0000 Received: from vanadium.cait.org ([209.174.123.60] helo=zimbra.cait.org) by dubrium.sys.ma.cait.org with esmtp (Exim 4.68) (envelope-from ) id 1LZ9hb-0003GH-9Q for dev@geronimo.apache.org; Mon, 16 Feb 2009 14:04:28 -0600 Date: Mon, 16 Feb 2009 14:04:27 -0600 (CST) From: Chance Yeoman To: dev@geronimo.apache.org Message-ID: <8402969.32881234814667012.JavaMail.root@vanadium.sys.ma.cait.org> In-Reply-To: <13972899.32811234814332823.JavaMail.root@vanadium.sys.ma.cait.org> Subject: Re: Pulling Geronimo Configuration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [64.107.227.41] X-Mailer: Zimbra 5.0.11_GA_2696.RHEL4 (ZimbraWebClient - FF3.0 (Win)/5.0.11_GA_2696.RHEL4) X-Spam-Score-External: 0.0 (/) X-Virus-Checked: Checked by ClamAV on apache.org Hi Gianny, I'll take a shot at it. I am brand new to the WADI API, but at first glance it seems that it would be a very flexible approach. I'll look at the NetworkConnectorMonitor to get a better feel for how it should be used. Thanks, Chance ----- Original Message ----- From: "Gianny Damour" To: dev@geronimo.apache.org Sent: Thursday, February 12, 2009 4:02:51 AM GMT -06:00 US/Canada Central Subject: Re: Pulling Geronimo Configuration On 12/02/2009, at 9:46 AM, David Jencks wrote: > > I think it would be great to get node discovery based on WADI > working. Unfortunately I was in too much of a hurry when I > implemented the plugin based farming to look into how to do this. > > Where is your ejb client failover code? Hi David, The code is located in the project plugins/openejb/geronimo-openejb-clustering-wadi The interesting class is NetworkConnectorMonitor where the method registerListenerForMembershipUpdates provides to joining peers the list of OpenEJB deployments currently running along with the network connector URIs EJB clients can used to access the EJB server running these deployments. Reading the code once again, it actually uses the geronimo-clustering API to track joining/leaving SessionManagers. So, if a BasicWADISessionManager is installed on admin and farm nodes the same type of approach may be used. I can certainly work on swapping the current node discovery implementation with a WADI implementation. Chance, do you want to give it a shot? Thanks, Gianny > > thanks > david jencks >