]
Galder Zamarreño commented on ISPN-915:
---------------------------------------
Another important point is that while TransactionTable is waiting for on-going txs to
finish, no new operations should be allowed against the cache. The test needs to make sure
that this happens as well: so if status is STOPPING, then no new invocations are allowed.
Cache.stop() should wait for on-going txs to finish
---------------------------------------------------
Key: ISPN-915
URL:
https://issues.jboss.org/browse/ISPN-915
Project: Infinispan
Issue Type: Bug
Affects Versions: 4.2.0.Final, 4.2.1.CR1, 5.0.0.ALPHA2
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 4.2.1.Final, 5.0.0.ALPHA3
At first glance, this should be relatively easy to achieve by making sure
TransactionTable.stop() waits for local and remote transaction collections to be empty.
Clearly, waiting for txs to finish would be configurable with a timeout. This timeout
should not be bigger than the transaction timeout, otherwise you're wasting time cos
even if a transaction started just before Cache.stop() was called, it could only last as
long as the TM says.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: