Hi Miroslav
Thanks for trying out Shoal and letting us know.
The support for virtual multicast uri list was added and left as an
experimental feature in 1.1 as we did not get to test sufficiently given
that we had to meet many other requirements for GlassFish 2.1.1
clustering and Sailfin v2 clustering for telco apps.
As such we have never supported this feature - but we are currently
working on having this feature supported in Shoal over the Grizzly based
transport implementation in the next version of Shoal 1.5.x.
The issue you are seeing seems surely suggests that some messages are
not able to be sent to a receiver.
Have you seen this warning when messages per second are lower?
Thanks
Shreedhar
On 7/22/11 3:01 AM, smiki975_at_gmail.com wrote:
> Hi,
>
> I have three nodes in the cluster which are running on Amazon EC2. They
> communicate among themselves using shoal and traffic speed is about 300
> messages in second.
> I am using shoal 1.1 which use jxta 1.3.
> Also i cannot use multicast on this system, so on each server i am
> using VIRTUAL_MULTICAST_URI_LIST and IS_BOOTSTRAPPING_NODE parameters.
>
> In the servers log i got a lot of the following warning:
>
> Jul 22, 2011 11:35:00 AM com.sun.enterprise.jxtamgmt.ClusterManager
> send
> WARNING: ClusterManager.send: message
> net.jxta.endpoint.Message_at_2012082307(2){62264483} not sent to
> urn:jxta:uuid-59616261646162614A787461503250336E141A0272904E4286AA9AEAB
> AE8BC9B03 OutputPipe.send attempted resend 4 and they all returned
> false.
>
> What this warning means?
> Does this means that some messages are not send to receiver? Any
> advice how to get rid of this warning?
>
> Best regards
> Miroslav