[ https://issues.apache.org/jira/browse/GEODE-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Schuchardt resolved GEODE-4377. ------------------------------------- Resolution: Fixed Fix Version/s: 1.5.0 > Don't catch encoding exceptions in OperationHandlers > ---------------------------------------------------- > > Key: GEODE-4377 > URL: https://issues.apache.org/jira/browse/GEODE-4377 > Project: Geode > Issue Type: Improvement > Components: client/server > Reporter: Galen O'Sullivan > Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > In the protobuf protocol, we are currently catching EncodingException due to > values that we can't deserialize or result values that we can't serialize. > Encoding and decoding exceptions should be handled differently, so clients > can tell if a value was present but could not be serialized. > Encoding and decoding errors should be handled consistently across operation > handlers. > Probably we could throw Encoding or Decoding exceptions and handle them at a > higher level than the individual op handler. -- This message was sent by Atlassian JIRA (v7.6.3#76005)