Project: mule
Issue MULE-7589: VM transactions should support multithreading
VM transactions have as a known limitation around concurrency. Only the thread that started the transaction should be able to use it and/or close it. For highly concurrent use cases, it'd be great if scenarios like the following would be supported: Thread 1: Opens transaction A and polls one element from it Thread 2: Opens transaction B over the same queue and polls one element from it Thread 2: writes to the queue in the context of transaction A Thread 1: writes to the queue in the context of transaction B Thread 2: commits/rollbacks the transaction A Thread 1: commits/rollbacks the transaction B
Story points: 8