This issue was hot fixed already but it's worth documenting it in case it applies to your TM use case.
The problem was introduced in eb7ba2a0ca28ed2f4480ad079ca98c704edd3001 where we optimize abbreviated names in a Map<TransactionParticipant,String>. Problem this was a static Map and we should have mapped classes instead of instances, but even classes isn't a good idea as they may change when we use Q2's dynamic classloading.
The problem, already fixed in 2.1.9-SNAPSHOT (86950d6e2c2), only shows up when a participant uses a big amount of memory, and gets redeployed often.
This issue was hot fixed already but it's worth documenting it in case it applies to your TM use case.
The problem was introduced in eb7ba2a0ca28ed2f4480ad079ca98c704edd3001 where we optimize abbreviated names in a
Map<TransactionParticipant,String>. Problem this was a static Map and we should have mapped classes instead of instances, but even classes isn't a good idea as they may change when we use Q2's dynamic classloading.The problem, already fixed in 2.1.9-SNAPSHOT (86950d6e2c2), only shows up when a participant uses a big amount of memory, and gets redeployed often.