[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Is ECF Discovery Service necessary when using RemoteServices

Hi Bart,

If you can see:
ZooDiscovery> Discovery Service Activated.
then
ZooDiscovery> INFO - Attempting connection to server:
 in output,  then  the zooDiscovery is running but clients cannot connect to the to center.  There may be different reasons for that (firewall, antivirus,..) but most of time it happens because of the client port (default  is 2181) is not approachable.
So to strip out the client port possibily, please try the following:

1- Set another client port using this system property
-Dzoodiscovery.clientPort=some_available_ port  in the central machine (192.1.10.10 in the example)
2- append that port to the target IP addresses of participating zooDiscovery instances, that is, all instances get now: e.g,   "zoodiscovery.flavor.centralized=192.1.10.10:some_available_ port"

Hope this helps,

Ahmed,
remainsoftware.com

 

From: Bartosz CzerwiÅski <czerwin@xxxxxxxxxx>
To: "'Eclipse Communication Framework \(ECF\) developer mailing list.'" <ecf-dev@xxxxxxxxxxx>
Date: 10-02-2011 10:28
Subject: Re: [ecf-dev]        Is        ECF        Discovery        Service        necessary        when        using        RemoteServices





Hi Ahmed,
 
Iâm sorry for the late response.
 
> Are you configuring ALL the participating nodes (zooDiscovery instances) with the same IP address when
> using "zoodiscovery.flavor.centralized"? For instance "zoodiscovery.flavor.centralized=192.1.10.10" means > all nodes configured as such will connect to the zooDiscovery instance running on host with IP
> 192.1.10.10. That implies the very zooDiscovery instance running on 192.1.10.10 host is configured with
> "zoodiscovery.flavor.centralized=192.1.10.10" as well, in our example.
Precisely. Iâm doing it in the way you described it. The problem is that the main node (192.1.10.10 in your example) does not connect to itself (zooDiscovery is not starting).
 
--
BC
 
From: ecf-dev-bounces@xxxxxxxxxxx [mailto:ecf-dev-bounces@xxxxxxxxxxx] On Behalf Of ahmed.aadel@xxxxxxxxxxxxxxxxxx
Sent:
Monday, January 17, 2011 10:14 AM
To:
Eclipse Communication Framework (ECF) developer mailing list.
Subject:
Re: [ecf-dev] Is ECF Discovery Service necessary when using RemoteServices

 
Hi Bart,

>Maybe you can help with the zoodiscovery container. When using "zoodiscovery.flavor.centralized" flavour of zoodiscovery I encounter problems with the "root >node". According to the description located on the
http://wiki.eclipse.org/Zoodiscovery page there should be one node which is connecting to itself. Doing >this that way it causes that the node cannot connect and it's generating "Attempt connecting to ..." log entry all the time.

Are you configuring ALL the participating nodes (zooDiscovery instances) with the same IP address when using "zoodiscovery.flavor.centralized"? For instance "zoodiscovery.flavor.centralized=192.1.10.10" means all nodes configured as such will connect to the zooDiscovery instance running on host with IP 192.1.10.10. That implies the very zooDiscovery instance running on 192.1.10.10 host is configured with "zoodiscovery.flavor.centralized=192.1.10.10" as well, in our example.


Ahmed,

remainsoftware.com

From: Bartosz CzerwiÅski <czerwin@xxxxxxxxxx>
To: "'Eclipse Communication Framework \(ECF\) developer mailing list.'" <ecf-dev@xxxxxxxxxxx>
Date: 14-01-2011 14:57
Subject: Re: [ecf-dev] Is        ECF        Discovery        Service        necessary        when        using        RemoteServices

 






> From:
ecf-dev-bounces@xxxxxxxxxxx [mailto:ecf-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Markus Alexander Kuppe
> Sent: Friday, January 14, 2011 2:50 PM
>
> On 01/14/2011 02:38 PM, Bartosz CzerwiÅski wrote:
> > On the consumer side additionally I configure the container:
> > IContainer container =
> containerFactory.createContainer("ecf.generic.client");
> >                                   container.connect(
> >                                   IDFactory.getDefault().createID(
> >                                   container.getConnectNamespace(),
> > "ecftcp://192.168.206.1:10013/server"), null);
>
> Just connecting containers does not end with the remote service being
> automatically added to the local service registry.
This is the information I was looking for! Thank you for all replies!


>
> With this approach you would essentially have to retrieve all remote services
> from the remote container and add them manually to the local service
> registry. Pretty much what ECF remote services gives you for free anyway if
> used with ECF discovery.
Maybe you can help with the zoodiscovery container. When using "zoodiscovery.flavor.centralized" flavour of zoodiscovery I encounter problems with the "root node". According to the description located on the
http://wiki.eclipse.org/Zoodiscovery page there should be one node which is connecting to itself. Doing this that way it causes that the node cannot connect and it's generating "Attempt connecting to ..." log entry all the time.



>
> Markus
> _______________________________________________
> ecf-dev mailing list
>
ecf-dev@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/ecf-dev
[attachment "smime.p7s" deleted by Ahmed Aadel/Remain] _______________________________________________
ecf-dev mailing list

ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
[attachment "smime.p7s" deleted by Ahmed Aadel/Remain]
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev