What test(s) are you running? Version?
--Udo
On 2/25/21, 8:39 AM, "Ernie Burghardt" wrote:
Its not just you Bruce, I get this...
2021-02-24 13:38:10,891 main ERROR Error processing element GeodeConsole
([Appenders: null]): CLASS_NOT_FOUND
2021-02-24 13:38:10,898 main ERROR Error p
+1
Built source and examples, reviewed NOTICE and LICENSE and tgz distribution.
-Original Message-
From: Owen Nichols
Sent: Sunday, February 21, 2021 12:08 PM
To: dev@geode.apache.org
Subject: [VOTE] Apache Geode 1.12.1.RC4
Hello Geode Dev Community,
This is a release candidate for
Looks good to me.
Be aware that users can provide custom key/trust managers and that behavior
should be preserved without them being wrapped with this new file watching
manager.
-Jake
> On Feb 4, 2021, at 7:06 AM, Joris Melchior wrote:
>
> Hi Geode developers,
>
> I have published an RFC f
To be clear SDG Neumann/2.3.x builds with Apache Geode 1.12.1, correctly.
+1
From: John Blum
Sent: Wednesday, February 24, 2021 1:52 PM
To: dev@geode.apache.org
Subject: Re: [VOTE] Apache Geode 1.12.1.RC4
+1
Spring Data for Apache Geode builds with Apache Geode
+1
Spring Data for Apache Geode builds with Apache Geode 1.12.1 RC bits.
From: Dave Barnes
Sent: Wednesday, February 24, 2021 10:34 AM
To: dev@geode.apache.org
Subject: Re: [VOTE] Apache Geode 1.12.1.RC4
+1
Docs.
- Geode API docs header correctly updated to 1.12
Its not just you Bruce, I get this...
2021-02-24 13:38:10,891 main ERROR Error processing element GeodeConsole
([Appenders: null]): CLASS_NOT_FOUND
2021-02-24 13:38:10,898 main ERROR Error processing element GeodeLogWriter
([Appenders: null]): CLASS_NOT_FOUND
2021-02-24 13:38:10,898 main ERROR Er
This has started showing up in all of my test runs. Is anyone else seeing it?
Maybe something in my environment?
2021-02-24 11:19:44,765 main ERROR Error processing element GeodeConsole
([Appenders: null]): CLASS_NOT_FOUND
2021-02-24 11:19:44,778 main ERROR Error processing element GeodeLogWri
Just FWIW - we cut the 1.14 branch of native *prior to* merging the boost::asio
change, so we would have some mileage on the change before releasing. So, all
other things being equal, this will be in native 1.15, not 1.14.
Thanks,
Blake
-Original Message-
From: Jacob Barrett
Sent: W
+1
Docs.
- Geode API docs header correctly updated to 1.12.1
- User guide build scripts generated correct 1.12.1 manual
- Native client user guides built correctly
- Native client api docs not tested -- they're generated by the full
software build, so I assume they're OK. We publish only the latest
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 totally agree with you.
>
> Interestingly, that logic has been recently removed from the C++ client when
> we switched from ACE_SOCK to boost::asio so what I said in my pr
Thanks Jake. I totally agree with you.
Interestingly, that logic has been recently removed from the C++ client when we
switched from ACE_SOCK to boost::asio so what I said in my previous e-mail
pertained to the C++ client 1.13 version and older.
Alberto
From: Ja
The Java client does the same thing under certain conditions. Neither of the
clients should do this though. I think this model is way too overaggressive. I
think we should remove that logic entirely. If we think we want something that
proactively checks the other connections to that server we co
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 eventually provokes
13 matches
Mail list logo
