[
https://jira.jboss.org/browse/ISPN-557?page=com.atlassian.jira.plugin.sys...
]
Galder Zamarreno commented on ISPN-557:
---------------------------------------
These type of scenarios should consider whether the two embedded Infinispan nodes are
deployed in the same jar or potentially in different, isolated jars. If the latter, there
might be classloading issues with calls between diff jars, particularly if these jars
belong to diff Infinispan versions. If Hot Rod is used to communicate between them,
you'll probably avoid these issues. This use case sounds like a niche one IMO.
support for same transaction touching multiple nodes (multiple VMs)
--------------------------------------------------------------------
Key: ISPN-557
URL:
https://jira.jboss.org/browse/ISPN-557
Project: Infinispan
Issue Type: Feature Request
Components: Transactions
Affects Versions: 4.1.0.Final
Reporter: Mircea Markus
Assignee: Manik Surtani
Fix For: 5.1.0.BETA1, 5.1.0.Final
E.g. if a distributed transaction managers touches two embedded Infinispan nodes within
the same transaction.
Could be implemented using the Hot Rod client approach - but in an embedded fashion!
EmbeddedClient <-- implements logic above
Except comms are in-VM for local entries
And via RpcDispatcher for remote entries
RemoteClient extends EmbeddedClient
Adds proper HotRod layer for comms
Including failover, smart routing, etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira