Multiple admin users trying to create a transaction in parallel get the same transaction ID

We have observed the following behavior when implementing transactions with F5 GTM 11.5.3

 

• Using one GTM credential per thread, when we run multiple create transactions requests in parallel, all threads get the same Transaction ID.
• Out of these transactions, only one transaction is committed successfully. The other transactions fail with the error {"code":404,"message":"there is no command to commit in the transaction.","errorStack":[]}
• Using two threads, if we ‘wait’ for one thread to complete a transaction before the other thread creates its own (by sleeping the thread), we observed that both threads now get different transaction IDs.

In conclusion, our observation is that the GTM returns the same transaction ID to all users (each user running her own thread), till the transaction is complete. If a thread requests a transaction creation when no transaction is running, a new transaction with a new ID is created.

 

Our question is why do different users get the same transaction ID?

 

All help is greatly appreciated.

 

Thanks Pravin