[
https://issues.apache.org/jira/browse/JAMES-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3716.
---------------------------------
Resolution: Fixed
> 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
> Priority: Major
>
> 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.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
