脏数据导致分支事务回滚失败，全局事务状态是retrying。事务拦截器GlobalTransactionalInterceptor拦截到的状态是RollbackDone。无法调用failureHandler

• I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description

分支事务因为其他非全局事务的线程操作数据导致了脏数据，此时分支回滚的时候会失败。全局事务的状态是retrying。
GlobalTransactionalInterceptor拦截此拦截的状态是RollbackDone。此时没法调用failureHandler，进行相关的处理工作。导致相关资源一致被当前全局事务占用。

Ⅲ. Describe what you expected to happen

针对上述情况，我们改如何处理。官网的建议是根据日志手工处理，定义failureHandler做邮件通知。此时根本不会调用failureHandler。

Ⅳ. How to reproduce it (as minimally and precisely as possible)

Ⅴ. Anything else we need to know?

Ⅵ. Environment:

• JDK version :
• OS :
• Others:

Start with GlobalTransactionalInterceptor and trace how the RollbackDone status is handled relative to failureHandler. Use the reported dirty-data branch rollback scenario as the reproduction case; the issue provides no minimal reproduction or test path. Done means the failure path has a clear, verifiable handling outcome and the resource-occupation behavior is addressed.