Trying again.
|
|
| jboss:service=Naming
| jboss:service=TransactionManager
| JotmTxMgrLookup
| REPEATABLE_READ
| REPL_SYNC
| false
| 0
| 0
| TestCluster
| true
|
|
|
Here's the cache config file. Note that JotmTxMgrLookup is a custom
TransactionManagerLookup implementation that creates a Jotm instance and
returns a reference to its TransactionManager.
jboss:service=Naming
jboss:service=TransactionManager
I have code that (within a single transaction) removes a node and then puts a
new value into the cache that is a child of the removed node. After the
transaction completes, the cache contains the new value AND the child nodes
that should have been removed when the parent node was removed. If I
I'm running pojocache 2.0.0 CR3 in a standalone two node active/hot-standby
cluster and I'm running into problems when brining up the second node (the
hot-standby). I'm using the replySync-service.xml configuration from the
example code (using TCP instead of multicast UDP). The active node is up
