You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Mario Salazar de Torres (Jira)" <ji...@apache.org> on 2022/01/11 09:01:00 UTC

[jira] [Assigned] (GEODE-9941) Coredump during PdxSerializable object deserialization

     [ https://issues.apache.org/jira/browse/GEODE-9941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mario Salazar de Torres reassigned GEODE-9941:
----------------------------------------------

    Assignee: Mario Salazar de Torres

> Coredump during PdxSerializable object deserialization
> ------------------------------------------------------
>
>                 Key: GEODE-9941
>                 URL: https://issues.apache.org/jira/browse/GEODE-9941
>             Project: Geode
>          Issue Type: Bug
>          Components: native client
>            Reporter: Mario Salazar de Torres
>            Assignee: Mario Salazar de Torres
>            Priority: Major
>
> *GIVEN* a cluster with a single server and a single locator with a PdxSerializable like class implementation named Order
> *AND* a geode-native client with 1 PdxSerializable class implementation named Order, matching the implementation on the cluster
> *AND* also on-client-disconnect-clear-pdxType-Ids=true in client configuration
> *WHEN* an Order object is tried to be deserialized
> *WHILE* the cluster is being restarted
> *THEN* a coredump happens given that PdxType=nullptr
> —
> {*}Additional information{*}. As seen by early troubleshooting, the coredump happens because the pdx type is tried to be fetched from the PdxTypeRegistry by its class name, but the PdxTypeRegistry is cleaned up during serialization given that subscription redundancy was lost.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)