Nice!

On Sat, Jul 8, 2017 at 10:40 PM, Júnior <[email protected]> wrote:

> Hi,
>
> I was able to find the problem.
>
> It was in broker.xml, I was using the same thrift server ip for both.
>
> When I used each ip address on the file, it worked.
>
> Thanks!
>
> 2017-07-07 17:56 GMT-03:00 Júnior <[email protected]>:
>
>> Hello Hasitha,
>>
>> I have tried that, but I keep receiving this error message in the second
>> node:
>>
>>
>> oreImpl
>> TID: [-1234] [] [2017-07-07 20:51:13,838]  WARN
>> {org.wso2.andes.server.cluster.CoordinationConfigurableClusterAgent} -
>>  Node id was null for member Member [xxxx.xxx.X.X]:5711. Node id will be
>> read again after 2 seconds.
>>
>>
>> After 4 attempts it shutdown the node.
>>
>> Follow my axis2 configuration for clustering:
>>
>>
>>
>> <clustering class="org.wso2.carbon.core.clustering.hazelcast.HazelcastCl
>> usteringAgent" enable="true">
>>         <parameter name="AvoidInitiation">true</parameter>
>>         <parameter name="membershipScheme">aws</parameter>
>>         <parameter name="domain">localhost</parameter>
>>
>>         <parameter name="localMemberPort">5711</parameter>
>>         <parameter name="accessKey">accesskey</parameter>
>>         <parameter name="secretKey">secretkey</parameter>
>>         <parameter name="securityGroup">secrutiy-group</parameter>
>>         <parameter name="region">us-east-2</parameter>
>>         <parameter name="tagKey">ClusterName</parameter>
>>         <parameter name="tagValue">mb_int</parameter>
>>
>>         <parameter name="properties">
>>             <property name="backendServerURL" value="https://
>> ${hostName}:${httpsPort}/services/"/>
>>             <property name="mgtConsoleURL" value="https://${hostName}:${h
>> ttpsPort}/"/>
>>             <property name="subDomain" value="worker"/>
>>         </parameter>
>>
>>  </clustering>
>>
>>
>> When i start the second node, I can see in the logs that has joined the
>> cluster, but as it is not able to get the hazelcast node id of the first
>> node, it shutdowns the second one.
>>
>>
>> Any clue on this is very welcome.
>>
>> Thanks,
>>
>> 2017-07-05 14:20 GMT-03:00 Júnior <[email protected]>:
>>
>>> Thank you Hasitha.
>>>
>>> It thought leaving it as default, it would generate one.
>>>
>>> The ports are open, I can see in the logs it saying the new member has
>>> joined, but it keeps trying to get the node id of the other member, and
>>> when it is not able to do, it shutdown the node.
>>>
>>> I will try and let you know the results.
>>>
>>> Thanks,
>>>
>>> 2017-07-05 8:52 GMT-03:00 Hasitha Hiranya <[email protected]>:
>>>
>>>> Hi,
>>>>
>>>> <coordination>
>>>>         <!-- You can override the cluster node identifier of this MB
>>>> node using the nodeID.
>>>>         If it is left as "default", the default node ID will be
>>>> generated for it. (Using IP + UUID).
>>>>         The node ID of each member should ALWAYS be unique.-->
>>>>         <nodeID>default</nodeID>
>>>>
>>>> Set a node id in broker.xml file at [EI_HOME]/wso2/broker/conf
>>>>
>>>> BTW, are necessary ports open for Hazelcast to communicate?
>>>>
>>>> Thanks
>>>>
>>>> On Mon, Jul 3, 2017 at 6:51 PM, Júnior <[email protected]> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I am trying to setup a cluster for the Broker Profile on AWS.
>>>>>
>>>>> I am able to start the first node without problem, but when we start
>>>>> the second node, it doesn't start because it says it is not able to get 
>>>>> the
>>>>> node id of the other member:
>>>>>
>>>>> TID: [-1234] [] [2017-07-03 12:55:10,193] ERROR
>>>>> {org.wso2.andes.server.registry.ApplicationRegistry} -
>>>>>  org.wso2.andes.kernel.AndesException: Failed to read Node id of
>>>>> hazelcast member Member [X.X.X.X]:5711
>>>>>
>>>>> On the nodes I have leave the nodeId on broker.xml as default, so it
>>>>> will generate a random one.
>>>>>
>>>>> Do you have any clue on where should I set this node id?
>>>>>
>>>>> Thanks,
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Francisco Ribeiro
>>>>> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>>>>>
>>>>> _______________________________________________
>>>>> Dev mailing list
>>>>> [email protected]
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Hasitha Abeykoon*
>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>>>> *cell:* *+94 719363063*
>>>> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>
>>>>
>>>>
>>>
>>>
>>> --
>>> Francisco Ribeiro
>>> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>>>
>>
>>
>>
>> --
>> Francisco Ribeiro
>> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>>
>
>
>
> --
> Francisco Ribeiro
> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>



-- 
*Hasitha Abeykoon*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
*cell:* *+94 719363063*
*blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to