"resetStateOnExceptionChange" has no effect, because the cause of "ListenerExecutionFailedException" is always a "TimestampedException"

[sebastianloefflath]

In what version(s) of Spring for Apache Kafka are you seeing this issue?

spring-kafka 3.0.5

Describe the bug

same bug as in #1653.

spring-kafka does not recognize an exception change from RetryException to FatalException, because it is wrapped multiple times. (ListenerExecutionFailedException -> TimestampedException -> ListenerExecutionFailedException -> FatalException)

The FailedRecordTracker unwraps only one layer (that was the fix for #1653)so it seems like the Exception does not change and is always TimestampedException

So this happens from a records view:
A record gets retried (blocking) -> the blocking error resolves -> fatal exception occurs on the same record -> record is being retried until configured number of blocking retry attempts.

To Reproduce

https://github.com/sebastianloefflath/spring-retry-bug
Run the tests of this repo to see the bug.

Expected behavior

Put the record to the DeadLetterTopic as soon as the FatalException occurs

Sample

https://github.com/sebastianloefflath/spring-retry-bug

[garyrussell]

Thanks for the reproducer; it is much appreciated; I wish more folks would take the time to do that.

[sebastianloefflath]

OMG. you guys are awesome! thank you very much for your fast fix!