Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

We have not tested AWS clustering with old kernel. We moved to AWS clustering with new kernel. I thought it was due to new kernel version as I have heard AWS was working properly with products released with older kernel. Here I have started each node one after the other. And once a member was

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

And also I have tested the cluster with WKA membership scheme with old kernel previously and it worked fine. But with new kernel version we got some issues and that is why we had to move to AWS clustering mode. On Tue, Oct 27, 2015 at 12:55 PM, Maninda Edirisooriya wrote: >

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

On Tue, Oct 27, 2015 at 12:55 PM, Maninda Edirisooriya wrote: > > Here I have started each node one after the other. And once a member was > stopped also any message was not printed. > Then it might be a connection issue between nodes. On Tue, Oct 27, 2015 at 12:55 PM,

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

No. It is because the cluster was not properly set. I could access other nodes from these nodes. Even though the cluster was setup it seems nodes does not recognize other nodes as members. On Tue, Oct 27, 2015 at 2:02 PM, Imesh Gunaratne wrote: > On Tue, Oct 27, 2015 at 12:55

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

I setup two Carbon 4.4.2 servers in two EC2 nodes and added the above mentioned configurations in the axis2.xml and started (one after the other) and the same issue was observed. No message was logged once one server was shut down in the other node backend logs. Thanks. *Maninda Edirisooriya*

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

Member joined message may not come with AWS membership scheme if all the members were started at the same time. However the member left message should appear if a member is stopped afterwards. On Monday, October 26, 2015, Maninda Edirisooriya wrote: > I have setup the AWS

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

Are the same settings working with the old kernel? On Mon, Oct 26, 2015 at 10:21 PM, Maninda Edirisooriya wrote: > I have setup the AWS clustering according to [1] but it seems the > "AWSBasedMembershipScheme > Member joined" message is not displayed once a new member is

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

I have setup the AWS clustering according to [1] but it seems the "AWSBasedMembershipScheme Member joined" message is not displayed once a new member is joined and no message when it left. This seems to be an issue with new kernel version. aws 5701 xxx zzz sg-16f4b571 us-east-1

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

In EC2 with AWS mode, you should use ports 5701 to 5800 On Sun, Oct 25, 2015 at 5:52 PM, Niranda Perera wrote: > Hi Thusitha, > > 4000 is the local host port specified in the axis2.xml > > quote axis2.xml > " > > 10.100.5.109 > > > > >

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

Hi Anjana, I noticed following error line on the error stack that you posted. com.hazelcast.spi.exception.WrongTargetException: WrongTarget! > this:Address[172.18.1.227]:4000 Here it tries to connect using the port 4000. But AFAIK we usually use ports between 5701 to 5800. Did you set the port

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

Hi Thusitha, 4000 is the local host port specified in the axis2.xml quote axis2.xml " 10.100.5.109 4000" in DAS we are using wka as the membership scheme. cheers On Sun, Oct 25, 2015 at 4:47 PM, Thusitha Thilina Dayaratne <

Re: [Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

Hi, So I'd a chat with Azeez, and the first thing he mentioned was, we should be using the AWS mode in EC2 it seems, the docs can be found for this here [1]. And his comments are, these kind of issues can be seen sometimes there, but if it recovers eventually it would be okay, but if it continues

[Dev] Hazelcast Issues in EC2 (Kernel 4.4.2)

Hi everyone, When testing DAS in EC2, and also with the latest Kernel 4.4.2, QA has reported some Hazlecast issues, specifically [1] and [2]. Some of the errors as follows:- TID: [-1234] [] [2015-10-24 08:40:05,130] ERROR {org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler} -