When creating a sifting appender with a timeout of unbounded (Duration.buildUnbounded() or <timeout>9223372036854775807millis</timeout>) causes the appender to continually recreate logs.
The error is on line 220 of AbstractComponentTracker. It returns "(entry.timestamp + timeout) < now". The issue is that when timeout is sufficiently high the difference becomes negative and hence will always be less than now. I am not entirely sure how to solve this. When unbounded is used, shouldn't the appender treat the logger as never being stale?