You are viewing a plain text version of this content. The canonical link for it is here.

Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2022/02/18 08:20:00 UTC

[jira] [Created] (JAMES-3716) Improving Cassandra driver error logs

Benoit Tellier created JAMES-3716:
-------------------------------------

             Summary: Improving Cassandra driver error logs
                 Key: JAMES-3716
                 URL: https://issues.apache.org/jira/browse/JAMES-3716
             Project: James Server
          Issue Type: Improvement
          Components: cassandra
            Reporter: Benoit Tellier


If a cassandra query execution fails, because we use reactive code to schedule the query, the stack trace being returned only implies driver classes, and have no elements that can be linked to the applicative code.

Context tracking in asynchronous systems is a hard topic, with dedicated solutions yet in our case we could easily reuse the executed statement to provide the faiing statement in the logging information.

Sure, this do not replace an applicative stacktrace yet this provide valuable information for debugging / diagnostic.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org