You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dan Smith (JIRA)" <ji...@apache.org> on 2018/04/10 19:38:00 UTC
[jira] [Created] (GEODE-5044) Protobuf server does not log full
stacktrace of failures
Dan Smith created GEODE-5044:
--------------------------------
Summary: Protobuf server does not log full stacktrace of failures
Key: GEODE-5044
URL: https://issues.apache.org/jira/browse/GEODE-5044
Project: Geode
Issue Type: Bug
Components: client/server
Reporter: Dan Smith
While doing some testing, we noticed that the protobuf server was not logging the stacktrace of some failures, which makes debugging difficult.
Looking at the code, it looks like we were trying to log the exception as a separate log line. But in this case the exception just gets turned into a string
{code:java}
logger.error("Invalid execution context found for operation {}", requestType);
logger.error(exception); //This just prints the toString of the exception
{code}
Instead, we should be logging the exception and message as a single line
{code:java}
logger.error("Invalid execution context found for operation {}", requestType, exception);
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)