-
Enhancement
-
Resolution: Done
-
Critical
-
None
-
None
-
Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1, Sprint 9.3.0.Final
-
Documentation (Ref Guide, User Guide, etc.)
-
High
It might be useful to allow Hot Rod clients to start transactions within Hot Rod servers. The possibility of clients participating in the actual transaction, i.e. being an XAResource, should not be imposed since this might be less than trivial to achieve in non-Java environments. The alternative would be to allow clients to start Hot Rod server local transactions only.
This would require enhancing Hot Rod spec to have some begin/commit/rollback commands that return a tx id, and for clients to be able to send this id as part of each command that should participate in the transaction.
Pitfalls to avoid include avoiding a transaction to be propagated over several Hot Rod servers. IOW, to simplify things, if a tx is started in server A, all ops within that tx should be directed to tx. Load balancing could still happen but would need to be tx sticky.
- blocks
-
MODE-2059 Allow the use of Infinispan's RemoteCacheManager as the cache container
- Closed
-
ISPN-848 Enhance HotRod to allow explicit locking of keys
- Closed
- is blocked by
-
ISPN-171 Build a server module based on the HotRod protocol
- Closed
- is incorporated by
-
ISPN-7807 Hot Rod Lightweight Transaction (Synchronization)
- Closed
-
ISPN-9176 Hot Rod Lightweight Transaction (XaResource)
- Closed
-
ISPN-9261 Hot Rod Lightweight Transaction (recovery)
- Closed