Hi Viola! On Jun 2, 2010, at 12:31 AM, viola.lu wrote:
> > Thanks. > > I know failover:sticky:ejbd://9.123.237.141:4201,ejbd://9.186.10.68:4201 can > work, but > in multicast , client can access with: > > p.setProperty(Context.PROVIDER_URL,"multicast:// > 239.255.3.2:6142?group=cluster1"); > > is there any thing like: > p.setProperty(Context.PROVIDER_URL,"multipoint://*****"); ? Nope. The multipoint stuff is entirely TCP based, so no real broadcast functionality to speak of. Communication of who is in the network is achieved by each server having a physical connection to each other server in the network. To join the network, you have to know the address of at least one server in the network and connect to it. When you do it will tell you the full list of all the other servers it knows about. The new server will then connect to each of those servers and they will in turn give their lists. The end result is that everyone has a connection to everyone 100% of the time, hence the made-up term "multipoint" to describe this situation of each server having multiple point-to-point connections which create a fully connected graph. On the client side things are similar. It needs to know the address of at least one server in the network and be able to connect to it. When it does it will get the full (and dynamically maintained) list of every server in the network. The client doesn't connect to each of those servers immediately, but rather consults the list in the event of a failover, using it to decide who to connect to next. So the initial list is essentially to help bootstrap that whole process and is required of every server and every client in the multipoint network. You really only need one valid server in the list and after the first valid contact with a running server, that bootstrap list becomes unused. Essentially the art of using a statically maintained list to bootstrap getting the more valuable dynamically maintained list. Hope this helps! -David > > > > On Wed, Jun 2, 2010 at 3:23 PM, David Blevins [via OpenEJB] < > [email protected]<ml-node%[email protected]> >> wrote: > >> >> On Jun 1, 2010, at 10:58 PM, viola.lu wrote: >> >>> >>> As we know, we can access ejb members with multicast URI: >>> multicast://239.255.3.2:6142?group=cluster1 >>> >>> Now i have serveral multipoint members: NODE1, NODE2, Node3, >>> if i want to acess ejb members with multipoint URI, this URI format is? >> >> Added that support just last week. Check out this JIRA: >> >> https://issues.apache.org/jira/browse/OPENEJB-1281 >> >> Still need to get it documented, but it's basically >> "failover:URL1,URL2,URL3" >> >> >> -David >> >> >> >> ------------------------------ >> View message @ >> http://openejb.979440.n4.nabble.com/Multipoint-URI-tp2239616p2239675.html >> To unsubscribe from Multipoint URI, click here< (link removed) ==>. >> >> >> > > > -- > viola > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Multipoint-URI-tp2239616p2239683.html > Sent from the OpenEJB Dev mailing list archive at Nabble.com.
