geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Jiang <genspr...@gmail.com>
Subject Re: failover demo in sandbox
Date Tue, 23 Feb 2010 09:53:34 GMT
I've implemented a WADIdiscoveryAgent.  This agent can be either multicast
or unicast based on geronimo WADI clustering setting.   The underlying
transportation mechanism are transparent to the agent user.

The WADIdiscoveryAgent based Farming plugin is working well now.   I'm
trying to test the stateless ejb.  current failover example client are still
based on multicast agent.

p[Context.INITIAL_CONTEXT_FACTORY] =
"org.apache.openejb.client.RemoteInitialContextFactory"
p[Context.PROVIDER_URL] = "*multicast*://239.255.3.2:6142?group=cluster1";
InitialContext(p)

I'm wondering if there's a way like following to specify a static unicast
node address in OpenEJB client code ?

p[Context.INITIAL_CONTEXT_FACTORY] =
"org.apache.openejb.client.RemoteInitialContextFactory"
p[Context.PROVIDER_URL] = "*ejbd://192.168.1.2:4221*?group=cluster1 , *
ejbd://10.2.1.2:4221*?group=cluster1, *ejbd://192.168.1.2:4221*
?group=cluster1";
InitialContext(p)


On Wed, Feb 3, 2010 at 6:23 PM, David Blevins <david.blevins@visi.com>wrote:

>
> On Feb 3, 2010, at 9:57 AM, Shawn Jiang wrote:
>
>  There are some discussions before that we should use WADI instead of
>> discoveryAgent to track cluster nodes.
>>
>>
>> http://old.nabble.com/Re%3A-Pulling-Geronimo-Configuration-td21962048s134.html
>>
>> I would like to give it a try instead of implementing another discovery
>> agent.
>>
>
> A WADI implementation of the DiscoveryAgent interface might work.  If it is
> able to keep a server list and notify people when items are added and
> removed, then it would work fine.
>
> If you mean to remove the DiscoveryAgent abstraction and rewrite the
> related Geronimo and OpenEJB code that uses it, then that is something we'd
> probably want to avoid.  Would probably be better to "fix" the abstraction
> if there was something wrong with it.  It is pretty simple though.  Whoever
> maintains the big list of all services simply needs to call the
> DiscoveryListener's "add" or "remove" methods so that parts of the system
> who are interested can act accordingly.
>
>
> -David
>
>


-- 
Shawn

Mime
View raw message