GitHub user WangzJi added a comment to the discussion: bind xid: 172.17.0.15:8092:27681535134726645, while current xid: 172.17.0.15:8092:27681535134726611
This XID binding conflict can occur in several scenarios beyond connection pool reuse: **Additional scenarios to check:** 1. **Transaction propagation**: `REQUIRES_NEW`/`NOT_SUPPORTED` with suspend/resume 2. **Retry mechanisms**: Failed transactions being retried with new XIDs 3. **XA timeout handling**: XA branch timeouts causing context inconsistency 4. **Coroutine contexts**: If using Kotlin coroutines **Debug info needed:** - Transaction propagation settings - Any retry/timeout configurations - Complete stack trace showing the call path - Whether XA mode is used This issue likely involves the same connection being used across different transaction contexts without proper cleanup between them. GitHub link: https://github.com/apache/incubator-seata/discussions/7455#discussioncomment-13528358 ---- This is an automatically sent email for dev@seata.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@seata.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@seata.apache.org For additional commands, e-mail: dev-h...@seata.apache.org
