[
https://issues.apache.org/jira/browse/GEODE-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701446#comment-16701446
]
John Blum commented on GEODE-6099:
----------------------------------
It is tempting to think that the error message is useful in the context of a
single interaction (transaction), since the error message does report the
{{Key}} along with the {{Region}} upon which the delta error occurred.
However, if I have a high volume of interactions/transactions on the same
Key/Value (Entry) in the same Region, is not apparent which Delta is in error,
therefore, it is useless, because I already know the {{Key}} and {{Region}} to
which the entry (i.e. the "delta") is being written.
What, I want to know is which "delta" (i.e. change) caused the error and why!
> Useless error message is logged when Geode fails to apply delta
> ---------------------------------------------------------------
>
> Key: GEODE-6099
> URL: https://issues.apache.org/jira/browse/GEODE-6099
> Project: Geode
> Issue Type: Bug
> Components: serialization
> Reporter: John Blum
> Priority: Major
>
> When serializing application domain objects using {{Deltas}} (i.e.
> application domain types implement {{org.apache.geode.Delta}}) between client
> and server, Apache Geode will log a completely *useless* error message to the
> log output (e.g. file) when Apache Geode encounters a problem applying the
> "delta"...
> {code}
> [info 2018/11/27 22:14:23.196 PST <ServerConnection on port 64301 Thread 1>
> tid=33] Error applying delta for key X of region /Example
> {code}
> Minimally, providing the underlying Exception's (i.e. {{cause}}) message
> would, perhaps, provide some relief and insight!
> This is with the {{log-level}} already set to {{config}}. I should not have
> to set the {{log-level}} to {{debug}} in order to ascertain the problem. At
> {{debug}}, or especially {{trace}}, I would expect to see a _Stack Track_
> even.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
