CQ HA

Hi, Having the following scenario: C++ Client is registered to server via CQ mechanism, there are 2 servers (primary and backup) Once the primary is failed it takes 15 seconds for the backup to take over. Once it takes over new data is sent to the client, however the records accumulated in these

RE: ACE version for C++ client (not grant)

: ACE version for C++ client (not grant) There was no previous release of Geode Native. In fact there have not been any releases of Geode Native. On Mon, Mar 6, 2017 at 8:07 AM Avital Amity wrote: > This is on the grant, I have the previous version, there in this file > I can see

RE: ACE version for C++ client (not grant)

oduce the Geode dynamic library. -Jake On Mon, Mar 6, 2017 at 6:50 AM Avital Amity wrote: > Yes, it is 6.3.3 - but is the product (ACE dll) part of the GEODE? > How can I know its compilation flags? > > -Original Message- > From: Jacob Barrett [mailto:jbarr...@pivota

RE: ACE version for C++ client (not grant)

) The version used in Geode is compiled using the dependency CMake files. See src/dependencies/ACE. On Mon, Mar 6, 2017 at 5:22 AM Avital Amity wrote: > Hi, > > We are currently using GEODE C++ client (not grant version) I see it > was compiled with ACE 6.3.3 - anyone knows if the

ACE version for C++ client (not grant)

Hi, We are currently using GEODE C++ client (not grant version) I see it was compiled with ACE 6.3.3 - anyone knows if the specific ACE that was used is part of the GEODE sources How can I get the specific lib it was compiled with (for Windows) Thanks Avital This message and the informatio

RE: [ANNOUNCE] Apache Geode release 1.1.0

Does the new version also include new C++ client? Thanks Avital -Original Message- From: Jun Aoki [mailto:ja...@pivotal.io] Sent: Friday, February 17, 2017 5:46 PM To: dev@geode.apache.org Cc: u...@geode.apache.org Subject: Re: [ANNOUNCE] Apache Geode release 1.1.0 Congrats! On Thu, Fe

RE: C++ client change history

en the two. > > -Jake > > On Mon, Feb 13, 2017 at 10:51 PM Avital Amity > > wrote: > > > Hi Jacob, > > > > Does the deprecated long in GEODE server 1.0 still exist in GF server? > > In what version was it removed from the server > > > > T

RE: C++ client change history

fs between the two. -Jake On Mon, Feb 13, 2017 at 10:51 PM Avital Amity wrote: > Hi Jacob, > > Does the deprecated long in GEODE server 1.0 still exist in GF server? > In what version was it removed from the server > > Thanks > Avital > > -Original Messag

RE: C++ client change history

on falls > through to default: but I'm unsure that I've pieced the output from > git diff together properly so that may not be a change that happened in > TcrMessage::handleByteArrayResponse. > > Sarge > > > On 12 Feb, 2017, at 09:25, Avital Amity wrote

C++ client change history

Hi, I'm trying to track the history of TcrMessage.cpp but I can find it only in the new client release where it moved under cppcache/src In particular I'm searching for the change where in function TcrMessage::handleByteArrayResponse Where the case of PING message was merged with the case of the

libSqLiteImpl.so

Hi, Can anyone advise what is the use of libSqLiteImpl.so which is part of the C++ client GEODE libraries? Thanks Avital 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_

ACE version

Hi, Anyone knows what is the ACE version used by GEODE C++ client? Thanks Avital 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

HA when using CQ query

Hi, When using subscription (subscription-enabled="true") and would like to have HA of the data Is the regular configuration in server side for the relevant region enough (redundant-copies="1") or any configuration also needed on client side (subscription-redundancy="1") What is the differenc

RE: messages repeating when using CQ Query mechanism

hould be set to 0, not sure why it keeps getting set back). [Avital Amity] I see this message usually prior to the expiry message: (again only in GEODE) invoking listeners: [org.apache.geode.internal.cache.ha.HARegionQueue$1@63668e3a] The second message is logged obviously when the cq is closed.

messages repeating when using CQ Query mechanism

Hi, When using CQQuery mechanism, when moving from GEMFIRE to GEODE we see differences in server log files including many of the following messages: [info ...] Entry expiry tasks disabled because the queue became primary. Old messageTimeToLive was: 180 [fine ...] Started closing CQ CqName: ...