[ANNOUNCE] Apache Geode Kafka Connector 1.1.0

[Dan Smith]

The Apache Geode community is pleased to announce the availability of
Apache Geode Kafka Connector 1.1.0.

Apache Geode is a data management platform that provides a database-like
consistency model, reliable transaction processing and a shared-nothing
architecture to maintain very low latency performance with high concurrency
processing.

The Apache Geode Kafka connector can be used to move data from Apache
Kafka to Apache Geode and vice versa.

This version of the Kafka connector upgrades log4j to version 2.16.0.

The release artifacts can be downloaded from
https://geode.apache.org/releases/

We would like to thank all the contributors that made the release possible.

Regards,
Dan Smith on behalf of the Apache Geode team

Re: Query - bug fix - ServerConnection thread got stuck

[Anilkumar Gingade]

Yossi,

The issue GEM-1193 is fixed few years back on older version of Geode. It should 
be there in current versions.
Also, without much details (stack trace) here, it is hard to say if its 
GEM-1193 or something new. Can you please create a new GEODE ticket with the 
artifacts (logs, stack-trace, error message…)
Curious how are you seeing/comparing this issue to be GEM-1193.

-Anil.


From: Yossi Reginiano 
Reply-To: "u...@geode.apache.org" 
Date: Monday, January 17, 2022 at 8:05 AM
To: "'dev@geode.apache.org'" 
Cc: "'u...@geode.apache.org'" , Shadey Jabareen 
, Shivasharana Rao 
Subject: Query - bug fix - ServerConnection thread got stuck

Hi team,

We are running with geode 1.13.2 and we faced issue where ServerConnection 
thread got stuck.
In the log we saw ClosedChannelException and we suspect it is related to the 
issue reported in gemfire bug/fix GEM-1193.
How can we check if this fix exist in geode and in which versions?

Thanks,
Yossi Reginiano

This email and the information contained herein is proprietary and confidential 
and subject to the Amdocs Email Terms of Service, which you may review at 
https://www.amdocs.com/about/email-terms-of-service

PdxSerialization implementation can't deserialize new fields

[Mario Salazar de Torres]

Hi everyone,

Recently, we ran into this issue on the native client: 
https://issues.apache.org/jira/browse/GEODE-9968
Which, in a summarized way, causes PdxSerialization implementation to fail to 
deserialize new fields.
RCA led us to localToRemote mapping 
(https://github.com/apache/geode-native/blob/44abff89f65f9c1bc72f504f3d57800dd1e48cbc/cppcache/src/PdxRemoteReader.cpp#L48),
 which implementation is failing for new fields.
But after checking the Java code for the equivalent part 
(https://github.com/apache/geode/blob/109fdd88a41d21c53f8f3da3b1dff5677afab3d2/geode-core/src/main/java/org/apache/geode/pdx/internal/PdxReaderImpl.java#L119),
 we've seen that there is no mapping there and the fields are fetched by name 
instead.

So, my question is: Do you know what's the purpose of this localToRemote map 
(my guess is that it's an optimization)?
And why this localToRemote map does not exist on the Java implementation? Just 
misalignment? Or did you find any problematic issue with the approach?

Thanks!
/Mario