Hi Tammo,

Yes, I agree with you. So I will use hazelcast.xml to configure.

Thank you
Sudharma

On 19 May 2015 at 16:25, Tammo van Lessen <tvanles...@gmail.com> wrote:

> Hi Sudharma,
>
> is this your own configuration file schema? What about just using the
> standard hazelcast.xml for the configuration and loading it from
> WEB-INF/conf? This would enable uses to use all hazelcast features (e.g.
> EC2 auto discovery) and we don't need to replicate to configuration
> documentation for the cluster config. WDYT?
>
> Best,
>   Tammo
>
> On Tue, May 19, 2015 at 8:54 AM, sudharma subasinghe <
> suba...@cse.mrt.ac.lk> wrote:
>
>> This is the structure of cluster config file. It uses static configuration
>>
>> <clusterconfig enabled=true>
>>  <membershipScheme>wka</membershipScheme>
>>
>> <!-- The host name or IP address of this member -->
>> <localMemberHost>127.0.0.1</localMemberHost>
>>
>> <!-- The TCP port of this member -->
>> <localMemberPort>4000</localMemberPort>
>>
>> <!-- The list of static or well-known members -->
>> <members>
>>     <member>
>>          <hostName>127.0.0.1</hostName>
>>          <port>4000</port>
>>     </member>
>>     <member>
>>          <hostName>127.0.0.2</hostName>
>>          <port>4001</port>
>>     </member>
>>     <member>
>>          <hostName>127.0.0.3</hostName>
>>          <port>4002</port>
>>     </member>
>> </members>
>> </clusterconfig>
>>
>> Thank you
>>
>>
>> On 18 May 2015 at 22:17, Nandika Jayawardana <jayaw...@gmail.com> wrote:
>>
>>> In axis2, clustering implementation supports both WKA ( well known
>>> address
>>> based clustering ) and multicast. However, in most cases, its the well
>>> known address based method that is used in production setups. Hence, I
>>> think its better to implement well known address based method. Can you
>>> post
>>> your configuration file and the hazelcast based api design.
>>>
>>> Regards
>>> Nandika
>>>
>>> On Thu, May 14, 2015 at 3:16 PM, sudharma subasinghe <
>>> suba...@cse.mrt.ac.lk>
>>> wrote:
>>>
>>> > Hi,
>>> >
>>> > This is my plan on implementing ODE clustering using hazelcast. I
>>> thought
>>> > to use a static configuration. Each node has a config file which stores
>>> > hostName and port number of each node in the cluster. So each node is
>>> aware
>>> > of other nodes in the cluster and when a node start up it will join to
>>> the
>>> > cluster. Please give me ideas on this.
>>> >
>>> > Thanks,
>>> > Sudharma
>>> >
>>>
>>
>>
>
>
> --
> Tammo van Lessen - http://www.taval.de
>

Reply via email to