You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Nick Reich (JIRA)" <ji...@apache.org> on 2018/03/09 19:21:00 UTC
[jira] [Assigned] (GEODE-4798) JdbcConnectorException can not be
deserialized
[ https://issues.apache.org/jira/browse/GEODE-4798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Reich reassigned GEODE-4798:
---------------------------------
Assignee: Nick Reich
> JdbcConnectorException can not be deserialized
> ----------------------------------------------
>
> Key: GEODE-4798
> URL: https://issues.apache.org/jira/browse/GEODE-4798
> Project: Geode
> Issue Type: Bug
> Components: regions
> Affects Versions: 1.5.0
> Reporter: Darrel Schneider
> Assignee: Nick Reich
> Priority: Major
>
> The JdbcConnectorException cannot be deserialized because it is not a "trusted" class. Also the SQLException it usually wraps will also fail deserialization so it might be better to not create JdbcConnectorException instances whose cause is a SQLException. Instead do some type of conversion of the SQLException.
> The following is some information about how to get JdbcConnectorException to be trusted by the serialization code:
> Create a new DistributionService like this lucene one:
> LuceneDistributedSystemService
> geode-lucene/src/main/resources/META-INF/services/org.apache.geode.distributed.internal.DistributedSystemService
> It returns a text file with a whitelist.
> Add a test likeĀ
> org.apache.geode.codeAnalysis.AnalyzeLuceneSerializablesJUnitTest
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)