[
https://issues.apache.org/jira/browse/CAMEL-25731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18139462#comment-18139462
]
Claus Ibsen commented on CAMEL-25731:
-------------------------------------
Merged to main in https://github.com/apache/camel/pull/29294 (33accc67f274).
_Claude Code on behalf of davsclaus_
> camel-mongodb - tailable and change stream consumers log the stack trace only
> for the first of consecutive cursor failures
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-25731
> URL: https://issues.apache.org/jira/browse/CAMEL-25731
> Project: Camel
> Issue Type: Improvement
> Components: camel-mongodb
> Reporter: shashank
> Assignee: shashank
> Priority: Minor
> Fix For: 4.24.0
>
>
> Follow-up of CAMEL-25679 (agreed in the review of
> https://github.com/apache/camel/pull/27918).
> Since CAMEL-25679 the consumer thread of the tailable and change stream
> consumers ({{MongoAbstractConsumerThread}}) survives a failure to create a
> new cursor and tries again after {{cursorRegenerationDelay}}. While MongoDB
> is down, every attempt logs a WARN with the full stack trace, so a longer
> outage fills the log with identical stack traces.
> Proposed change: log the stack trace only for the first failure of a run of
> consecutive failures, and a one-line WARN (the exception) for the following
> ones, until a cursor is created again (then one INFO line). A test with a
> cursor factory that fails several times checks the number of stack traces
> logged.
> _Filed with Claude Code on behalf of allthingssecurity._
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
