Hi Mike,
Sorry for not responding earlier. We are busy with getting some high
priority issues resolved. I will look into the test to see what the
problem is.
Will have more information on the other questions that you have
posted soon.
Thanks
Sheetal
On Jun 25, 2008, at 8:34 AM, Mike Wannamaker wrote:
> Any thoughts?
>
> Also has anyone run the tests lately? GroupLeaderTest fails,
> looks as though ClusterManager line 161
> è this.bindInterfaceAddress = (String)props.get
> (JxtaConfigConstants.BIND_INTERFACE_ADDRESS.toString());
> requires the BIND_INTERFACE_ADDRESS property to be given or throws
> null pointer?
>
> --ekiM
>
> From: Mike Wannamaker [mailto:mwannama_at_opentext.com]
> Sent: June 24, 2008 10:30 PM
> To: users_at_shoal.dev.java.net
> Subject: [Shoal-Users] Questions and Documentation?
>
> Hi I have a few questions
>
> Was wondering if there is any documentation on bootstrapping the
> JXTA in order to facilitate cross sub-net/firewall communications?
> Also any documents on writing your own SPI like JXTA SPI? For
> example app servers have their own communication layer, ie: JBoss/
> JGroups, I would like to see how to hook in an already running
> JGroups in JBoss into Shoal’s SPI layer.
>
> Does Shoal take into account the fact that a component could
> saturate the network with messages and in affect possibly take down
> the Shoal cluster? IE: If I pump shoal full of large messages,
> this could in effect stop shoal’s heartbeat responses? Does shoal
> try to do any kind of smart marshalling of messages to ensure that
> network saturation does not happen?
>
> I believe also I read somewhere that there are plans to support
> cluster splits or partitioning. IE: If a network glitch or a
> network splits, we would in effect have two sub-clusters.
> Eventually the network would come back and these clusters would
> come back together and join.
>
> TIA
> Mike
>