RE: Question about closing of all connections towards an endpoint in C++ native client

: Wednesday, February 24, 2021 7:38 AM To: dev@geode.apache.org Subject: Re: Question about closing of all connections towards an endpoint in C++ native client Oh good! 1.14 is on its way, so problem solved! ;) > On Feb 24, 2021, at 7:31 AM, Alberto Gomez wrote: > > Thanks Jake. I tota

Re: Question about closing of all connections towards an endpoint in C++ native client

d. > > -Jake > >> On Feb 24, 2021, at 4:36 AM, Alberto Gomez wrote: >> >> Hi, >> >> Running some tests with the C++ native client and looking at the code, I >> have observed that when an error in a connection towards an endpoint >> (timeout, IO

Re: Question about closing of all connections towards an endpoint in C++ native client

: Jacob Barrett Sent: Wednesday, February 24, 2021 4:24 PM To: dev@geode.apache.org Subject: Re: Question about closing of all connections towards an endpoint in C++ native client The Java client does the same thing under certain conditions. Neither of the clients should do this though. I think

Re: Question about closing of all connections towards an endpoint in C++ native client

er connections towards that endpoint. > > Are my observations correct? > > If so, shouldn't the C++ native client be aligned with the Java client? > > Thanks, > > Alberto G.

Question about closing of all connections towards an endpoint in C++ native client

Hi, Running some tests with the C++ native client and looking at the code, I have observed that when an error in a connection towards an endpoint (timeout, IO error) is detected, not only the faulty connection is closed but the endpoint is set to "not connected" status which

Re: Review for "C++ native client Function.execute() with onServers does not throw exception if one of the servers goes down while executing the function."

Hi Alberto, I’m back from a week’s vacation this morning, and will have a look. Thanks, Blake From: Alberto Gomez Date: Monday, November 16, 2020 at 7:11 AM To: dev@geode.apache.org Subject: Review for "C++ native client Function.execute() with onServers does not throw exception if o

Review for "C++ native client Function.execute() with onServers does not throw exception if one of the servers goes down while executing the function."

Hi, Could somebody review PR https://github.com/apache/geode-native/pull/690 (https://issues.apache.org/jira/browse/GEODE-8693?filter=-2). Thanks, /Alberto G.

Re: Reviewers for GEODE-8231: C++ native client keeps trying to connect to down cache server hosting a partitioned region

On it now. Mike From: Alberto Gomez Sent: Monday, June 22, 2020 9:04 AM To: dev@geode.apache.org Subject: Re: Reviewers for GEODE-8231: C++ native client keeps trying to connect to down cache server hosting a partitioned region Hi, I have no complete reviews

Re: Reviewers for GEODE-8231: C++ native client keeps trying to connect to down cache server hosting a partitioned region

Hi, I have no complete reviews yet. Any volunteers? Thanks, Alberto From: Alberto Gomez Sent: Monday, June 15, 2020 1:31 PM To: dev@geode.apache.org Subject: Reviewers for GEODE-8231: C++ native client keeps trying to connect to down cache server hosting a

Reviewers for GEODE-8231: C++ native client keeps trying to connect to down cache server hosting a partitioned region

Hi, Can someone please review my PR about https://issues.apache.org/jira/browse/GEODE-8231 (C++ native client keeps trying to connect to down cache server hosting a partitioned region)? Here is the link to the PR: https://github.com/apache/geode-native/pull/615 Thanks, /Alberto G.

Re: Issues with TransactionIds managed by CacheTransactionManager in C++ native client

Hi Blake, Are you sure that the TransactionId is always set to -1? We have used the C++ native client transactions and they apparently worked. /Alberto G. From: Blake Bender Sent: Friday, December 13, 2019 6:17 PM To: dev@geode.apache.org Subject: Re: Issues

Re: Issues with TransactionIds managed by CacheTransactionManager in C++ native client

related to > TransactionIds managed by CacheTransactionManager in the C++ native client. > > https://issues.apache.org/jira/browse/GEODE-7573 > > In it, I also propose some solutions to the issues found. > > I'd appreciate if someone could review the analysis to see if I am in the

Issues with TransactionIds managed by CacheTransactionManager in C++ native client

Hi, I have created a ticket with some issues I have found related to TransactionIds managed by CacheTransactionManager in the C++ native client. https://issues.apache.org/jira/browse/GEODE-7573 In it, I also propose some solutions to the issues found. I'd appreciate if someone could r

Re: C# native client problem

Right, that is why I’m curious what SHA because the sources on develop for the last few months allow multiple caches in a process or app domain. > On Feb 6, 2018, at 6:38 AM, Michael Stolz wrote: > > Also could be that he's hitting the Cache singleton. Hard to tell from what > he wrote, but I

Re: C# native client problem

Also could be that he's hitting the Cache singleton. Hard to tell from what he wrote, but I think he's attempting to new multiple Caches in the same process. -- Mike Stolz Principal Engineer - Gemfire Product Manager Mobile: 631-835-4771 On Feb 6, 2018 9:35 AM, "Jacob Barrett" wrote: > Since th

Re: C# native client problem

Since there is no official release of the Geode Native C# client can you please tell us what SHA you have compiled? Quickly I can say you can’t create two regions with the same name in the same cache. -Jake > On Feb 6, 2018, at 1:30 AM, Rupert St John Webster > wrote: > > Dear All, > > P

C# native client problem

Dear All, Per https://stackoverflow.com/questions/48628342/ I have a C# class Geode.cs that sets up a native client local cache, pool and region and does some work. I want to reuse the class and have 2 or more local caches that do work (ultimately to have different callbacks

[jira] [Commented] (GEODE-2891) connect-timeout violation in C++ Native Client

the attachment and reopening the issue. > connect-timeout violation in C++ Native Client > -- > > Key: GEODE-2891 > URL: https://issues.apache.org/jira/browse/GEODE-2891 > Project: Geode >

[jira] [Reopened] (GEODE-2891) connect-timeout violation in C++ Native Client

[ https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Vortman reopened GEODE-2891: > connect-timeout violation in C++ Native Cli

[jira] [Updated] (GEODE-2891) connect-timeout violation in C++ Native Client

Reporter: Gregory Vortman > Attachments: GEODE-connect-timeout-violation.docx > > > 1.C++ native client doesn’t honour read-timeout-milli-sec in a consistent > way while connecting to a server > 2.The lock on the connection pool has a very high granularity. Even if

[jira] [Updated] (GEODE-2891) connect-timeout violation in C++ Native Client

in C++ Native Client > -- > > Key: GEODE-2891 > URL: https://issues.apache.org/jira/browse/GEODE-2891 > Project: Geode > Issue Type: Bug > Components: native client >

[jira] [Commented] (GEODE-2891) connect-timeout violation in C++ Native Client

timeout violation in C++ Native Client > -- > > Key: GEODE-2891 > URL: https://issues.apache.org/jira/browse/GEODE-2891 > Project: Geode > Issue Type: Bug > Components: native

[jira] [Updated] (GEODE-2891) connect-timeout violation in C++ Native Client

why the issue status is Resolved. Understood I have to correct the description and to remove any Gemfire instance from there. Will do it shortly. Please let me know how to proceed with the issues. Thanks > connect-timeout violation in C++ Native Cli

[jira] [Resolved] (GEODE-2891) connect-timeout violation in C++ Native Client

[ https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett resolved GEODE-2891. - Resolution: Invalid > connect-timeout violation in C++ Native Cli

[jira] [Commented] (GEODE-2891) connect-timeout violation in C++ Native Client

ment references issue with GemFire commercial product. Please remove and post issues that relate to the Geode project only. > connect-timeout violation in C++ Native Client > -- > > Key: GEODE-2891 > URL: https:

[jira] [Updated] (GEODE-2891) connect-timeout violation in C++ Native Client

[ https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett updated GEODE-2891: Fix Version/s: (was: 1.1.1) > connect-timeout violation in C++ Native Cli

[jira] [Commented] (GEODE-2891) connect-timeout violation in C++ Native Client

ease do not place commercial support information in the open source project. > connect-timeout violation in C++ Native Client > -- > > Key: GEODE-2891 > URL: https://issues.apache.org/jir

[jira] [Commented] (GEODE-2891) connect-timeout violation in C++ Native Client

.2.3 release is opened > connect-timeout violation in C++ Native Client > -- > > Key: GEODE-2891 > URL: https://issues.apache.org/jira/browse/GEODE-2891 > Project: Geode >

[jira] [Updated] (GEODE-2891) connect-timeout violation in C++ Native Client

[ https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Vortman updated GEODE-2891: --- Thanks for help > connect-timeout violation in C++ Native Cli

[jira] [Commented] (GEODE-2891) connect-timeout violation in C++ Native Client

thub repo and submit a pull request. You might want to assign the JIRA ticket to someone on your team if you are going to do this. Here is the process for submitting a pull request: https://cwiki.apache.org/confluence/display/GEODE/Code+contributions > connect-timeout violation in C++ Native

[jira] [Updated] (GEODE-2891) connect-timeout violation in C++ Native Client

out violation in C++ Native Client > -- > > Key: GEODE-2891 > URL: https://issues.apache.org/jira/browse/GEODE-2891 > Project: Geode > Issue Type: Bug > Components: native clie

[jira] [Updated] (GEODE-2891) connect-timeout violation in C++ Native Client

leges can be assigned? Thanks > connect-timeout violation in C++ Native Client > -- > > Key: GEODE-2891 > URL: https://issues.apache.org/jira/browse/GEODE-2891 > Project: Geode >

[jira] [Commented] (GEODE-2891) connect-timeout violation in C++ Native Client

the component should be "native client", not "client server" > connect-timeout violation in C++ Native Client > -- > > Key: GEODE-2891 > URL: https://issues.apache.org/jira/browse/

RE: [jira] [Updated] (GEODE-2891) connect-timeout violation in C++ Native Client

-2891) connect-timeout violation in C++ Native Client [ https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Vortman updated GEODE-2891: --- Attachment: gemfire-connect-timeout

[jira] [Updated] (GEODE-2891) connect-timeout violation in C++ Native Client

Reporter: Gregory Vortman > Fix For: 1.1.1 > > Attachments: gemfire-connect-timeout-violation.docx > > > 1.C++ native client doesn’t honour read-timeout-milli-sec in a consistent > way while connecting to a server > 2.The lock on the connection pool

[jira] [Created] (GEODE-2891) connect-timeout violation in C++ Native Client

Gregory Vortman created GEODE-2891: -- Summary: connect-timeout violation in C++ Native Client Key: GEODE-2891 URL: https://issues.apache.org/jira/browse/GEODE-2891 Project: Geode Issue Type

Re: C++ native client compilation in Visual Studio

..@pivotal.io] > Sent: Thursday, January 26, 2017 17:24 > To: dev@geode.apache.org > Subject: Re: C++ native client compilation in Visual Studio > > Native client is targeted for 64 bit only but that said you should have > success on 32 bit, though your milage may vary. > > Yo

RE: C++ native client compilation in Visual Studio

Oh I was looking on an older version of BUILDING.md.. Thanks, I will try with your instructions. Gal -Original Message- From: Jacob Barrett [mailto:jbarr...@pivotal.io] Sent: Thursday, January 26, 2017 17:24 To: dev@geode.apache.org Subject: Re: C++ native client compilation in Visual

Re: C++ native client compilation in Visual Studio

lid integer constant expression" Thanks, Gal -Original Message- From: Jacob Barrett [mailto:jbarr...@pivotal.io] Sent: Thursday, January 26, 2017 16:16 To: dev@geode.apache.org Subject: Re: C++ native client compilation in Visual Studio Can you share the steps you took? Did you follow the

RE: C++ native client compilation in Visual Studio

Re: C++ native client compilation in Visual Studio Can you share the steps you took? Did you follow the BUILDING.md file? On Thu, Jan 26, 2017 at 6:09 AM Gal Palmery wrote: > Hi All, > > Did anyone successfully compile the c++ native client on Windows in > Visual Studio and can shar

Re: C++ native client compilation in Visual Studio

Can you share the steps you took? Did you follow the BUILDING.md file? On Thu, Jan 26, 2017 at 6:09 AM Gal Palmery wrote: > Hi All, > > Did anyone successfully compile the c++ native client on Windows in Visual > Studio and can share some instructions ? > I'm struggling wit

C++ native client compilation in Visual Studio

Hi All, Did anyone successfully compile the c++ native client on Windows in Visual Studio and can share some instructions ? I'm struggling with it.. :\ Thanks, Gal This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,

c++ native client

Hi, Is there a plan to make the c++ native client suitable for the new release? I see that it's not compatible now after the packages name changes (the changes from gemfire to geode).. Thanks, Gal This message and the information contained herein is proprietary and confidential and subje