Alexey, Simplest way: wrap IgniteTransactions instance returned by ignite.transactions() with delegate using advanced logging capabilities for tx* methods, like current thread and stack trace.
There is no notion of transaction parameters. 2017-10-04 12:40 GMT+03:00 Alexey Inozemtsev <alexey.inozemt...@gmail.com>: > Igniters, > A team I'm working with uses Apache Ignite massively. > There are many application modules using the cluster. > We've faced a problem on how to identify the external app > modules which keep transactions open in the grid. > Right now we have to restart client nodes to get reed of them. > > Is there a parameter on Ignite transaction to (ala MODULE in Oracle) which > can be set on a client side? > Are there other ways to manage such a situation? > > Have a nice day, > Alexey > -- Best regards, Alexei Scherbakov
