Hi Christian,

At this time, we haven't seen enough community demand to work on providing a more complete solution to this than our current approach which is to utilize classloader isolation of the instances.

Please can you elaborate on your requirements and we can try to work with you on it?

Thanks,

Tom

You're assuming that there is one transaction manager for all transactions within Narayana. That is an incorrect assumption. Whilst we may talk about THE transaction manager, in reality every transaction is handled by a unique coordinator instance.

As Mark says above, each transaction has its own coordinator instance. So for example you can instantiate the following class and use it (or the BasicAction they derive from):

https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/TransactionImple.java

Here is an example of our unit tests doing that:

narayana/TransactionImpleUnitTest.java at master · jbosstm/narayana · GitHub

The issue I can foresee is that you may eventually want to have different configurations for each transaction concurrently (you talk about configuring each transaction to use a different disk). To do that you will need to use classloader isolation like I have here (and related classes):

narayana/SimpleIsolatedServers.java at master · jbosstm/narayana · GitHub

No problem - good luck with your testing!