My issue seems to be related to the WebSphere configuration. Although,
explicitly set java.net.preferIPv4Stack=true. After that it works as
On Sep 3, 9:56 am, Adrian Madrid <
aemad...@gmail.com> wrote:
> I've had problems sometimes when I launched two nodes simultaneously.
> Have you tried to deploy one and wait maybe 30 seconds before
> deploying the other?
>
> Adrian Madrid
>
>
>
> On Thu, Sep 2, 2010 at 16:53, anatoleus <
anatol...@gmail.com> wrote:
> > I am wondering if anyone has come across a similar issue:
>
> > I have two AIX boxes with WebSphere6.1 running on them. I would like
> > the application deployed to WebSpheres to be clustered via Hazelcast
> > 1.8.5. Both boxes can "see" each other via ping. The multicast is
> > enabled on both and even a simple Hazelcast tester works perfectly
> > when kicked off as a standalone java app on each box. The cluster is
> > being formed. However, when deployed within WebSphere it starts two
> > separate clusters, one on each box. Same code/EAR/Hazelcast/WebSphere
> > on two different Win boxes, again form a perfect cluster.
>
> > So it seems neither the code nor the network/sys configuration are
> > responsible for the problem. I gotta be missing something obvious
> > here...
>
> > any recommendations would be appreciated.
> > Thanks!
>
> > --
> > You received this message because you are subscribed to the Google Groups "Hazelcast" group.
> > To post to this group, send email to
haze...@googlegroups.com.
> > To unsubscribe from this group, send email to
hazelcast+...@googlegroups.com.