Can you post the snippet of XML please. On Tue, Feb 28, 2017 at 8:36 AM Avital Amity <[email protected]> wrote:
> In the client cache xml we put the locator IP address, it is IPV4 > > > > *From:* Jacob Barrett [mailto:[email protected]] > *Sent:* Tuesday, February 28, 2017 5:45 PM > > > *To:* [email protected] > *Subject:* Re: Running GEODE on Windows machine > > > > How are you assigning the locator address to the client? By host name or > IP? > > On Tue, Feb 28, 2017 at 7:26 AM Avital Amity <[email protected]> > wrote: > > To my best knowledge we are using IPv4 address for the locator… how can I > make sure? What should I check? > > > > Thanks > > Avital > > > > *From:* Jacob Barrett [mailto:[email protected]] > *Sent:* Tuesday, February 28, 2017 5:24 PM > > > *To:* [email protected] > *Subject:* Re: Running GEODE on Windows machine > > > > Looks like the client doesn't support IPv6. If the host has IPv4 addresses > please try that for locator. > > On Tue, Feb 28, 2017 at 6:58 AM Avital Amity <[email protected]> > wrote: > > Hi Akihiro, > > > > Thanks for your response > > > > Log messages: > > > > From client log: > > > [fine 2017/02/28 12:06:15.747910 … ] Exception while querying locator: > gemfire::GemfireIOException: TcpConn::connect failed with errno: 10047: > address family not supported > > > > From the shell we are running the client: > > > > ACE_INET_Addr::get_ip_address: address is a IPv6 address not IPv4 > > > > Regarding locator configuration – we are already using the suggested > configuration > > > > Thanks > > Avital > > > > *From:* Akihiro Kitada [mailto:[email protected] <[email protected]>] > *Sent:* Tuesday, February 28, 2017 8:45 AM > > > *To:* [email protected] > *Subject:* Re: Running GEODE on Windows machine > > > > Hello Avital, > > > > >I have compiled the C++ client on the Win machine, and able to run both > client and server there. the current problem is that the C++ client does > not “find” the GEODE server…. It fails on our functions that approach the > server…. > > > > Do you see some error message in the client log or in stdout/stderr when > you run your C++ client application on Windows? > > > > I think you may use the default connection pool which intends to try to > connect to Geode server running on localhost with listening via port number > 40404 or something. > > > > If so, why don't you specify the locator host with using cache.xml like > the following? > > ---- > > <?xml version="1.0" encoding="UTF-8"?> > > <client-cache> > > <pool name="replicatedPool" read-timeout="1000" > subscription-enabled="true" > > > <locator host="10.211.55.2" port="55221"/> > > </pool> > > > > <region name="replicatedRegion"> > > <region-attributes pool-name="replicatedPool" > refid="CACHING_PROXY"> > > </region-attributes> > > </region> > > </client-cache> > > ---- > > > > You can refer this cache.xml when creating a cache in your client > application like the following. > > ---- > > CacheFactoryPtr cacheFactory = CacheFactory::createCacheFactory(); > > cacheFactory->set("cache-xml-file","/path/to/cache.xml"); > > cacheFactory->set("log-level","config"); > > > > CachePtr cachePtr = cacheFactory->create(); > > ---- > > > > > > Thanks. > > > > > > > > > > > > > > > -- > > Akihiro Kitada | Staff Customer Engineer | +81 80 3716 3736 > <+81%2080-3716-3736> > Support.Pivotal.io <http://support.pivotal.io/> | Mon-Fri 9:00am to > 5:30pm JST | 1-877-477-2269 <(877)%20477-2269> > <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > 2017-02-28 15:23 GMT+09:00 Avital Amity <*[email protected]*>: > <https://support.pivotal.io/> > > Thanks <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > I have compiled the C++ client on the Win machine, and able to run both > client and server there. the current problem is that the C++ client does > not “find” the GEODE server…. It fails on our functions that approach the > server…. <https://support.pivotal.io/> > > I thought maybe some special configuration is needed… or maybe some other > idea…. What could be the issue <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > Thanks <https://support.pivotal.io/> > > Avital <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > > > > *From: Akihiro Kitada [mailto:[email protected]] Sent: Tuesday, February > 28, 2017 5:09 AM To: [email protected] Subject: Re: Running GEODE on > Windows machine <https://support.pivotal.io/>* > > <https://support.pivotal.io/> > > Hello Avital, <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > If you want to connect to Geode servers from your C++ application as a > Geode client, you need Apache Geode Native components although you may have > already known it. <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > *https://github.com/apache/geode-native* <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > As far as I know, there are no binary distributions for Apache Geode > Native. So you need to build those modules by yourself according to the > following docs. <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > *https://github.com/apache/geode-native/blob/develop/BUILDING.md* > <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > I've never tried to build Windows version of Apache Geode Native but you > may be able to build it easily by getting source code via git tools. So > far, I've successfully built macOS version of Apache Geode Native and I > confirmed it connects to Apache Geode 1.0.0 running on macOS. I wrote the > following blog entry based on my experience on macOS. > <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > *http://quitada.hatenablog.jp/entry/2017/02/14/010259* > <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > Thanks. <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > -- <https://support.pivotal.io/> > > Akihiro Kitada | Staff Customer Engineer | *+81 80 3716 3736* > *Support.Pivotal.io* | Mon-Fri 9:00am to 5:30pm JST | 1-877-477-2269 > <https://support.pivotal.io/> > > > > <https://support.pivotal.io/> > > 2017-02-28 0:05 GMT+09:00 Avital Amity <*[email protected]*>: > <https://support.pivotal.io/> > > Small comment – we are using C++ client <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > Thanks <https://support.pivotal.io/> > > Avital <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > > > > *From: Avital Amity Sent: Monday, February 27, 2017 4:57 PM To: > [email protected] Subject: Running GEODE on Windows machine > <https://support.pivotal.io/>* > > <https://support.pivotal.io/> > > Hi, <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > Anyone run GEODE on a windows machine? Does it require any special > configuration from Server side? Client side? <https://support.pivotal.io/> > > <https://support.pivotal.io/> > > Thanks <https://support.pivotal.io/> > > Avital <https://support.pivotal.io/> > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > <https://support.pivotal.io/> > > you may review at *http://www.amdocs.com/email_disclaimer.asp* > <https://support.pivotal.io/> > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > <https://support.pivotal.io/> > > you may review at *http://www.amdocs.com/email_disclaimer.asp* > <https://support.pivotal.io/> > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > <https://support.pivotal.io/> > > you may review at *http://www.amdocs.com/email_disclaimer.asp* > <https://support.pivotal.io/> > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > <https://support.pivotal.io/> > > you may review at *http://www.amdocs.com/email_disclaimer.asp* > <https://support.pivotal.io/> > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > you may review at http://www.amdocs.com/email_disclaimer.asp >
