…n or <expiration> element
* Fixed as well code issue that would lead to JDBC cache store preloading more data than it should.
This is done in order to support cache stores whose marshalling layer cannot be swapped, and therefore it requires stored elements to be Serializable as per standard Java rules.
…ache has finished starting up
This solves a compilation error and testsuite failures query module had
* A brand new externalizer was created to deal with CacheRpcCommand instances, allowing lookup of per-cache marshallers. * Extended RiverMarshaller and RiverUnmarshaller instances to allow cache marshaller to travel down the stack to externalizer impls.
…methods (If-Match, If-None-Match, If-Modified-Since, If-Unmodified-Since)
…logger lock even if the latch was open Sometimes the rehasher can acquire the write lock after a transaction thread has called latch.await() but before readLock.lock(). If that happens we need to retry the lock acquisition in the transaction thread.
…d the prepare command, since they could have already left the cluster. JGroups will wait for the response message until the timeout replication expires, while holding the locks for the modified keys. So other transactions could time out waiting for our locks.
…HandlerImpl if the entire cache manager is stopping
…ions or not
…o start properly This allowed an inbound command to start before the initial rehash even started.
…n configuration properties
…r of constructors in Lucene