commons-pool is bumped down to 1.4.0 from 1.5.1 google-collection is bumped up to 1.0.rc2
ant conditions just check if the property isset or not. there is no easy way to unset a property in general added an additional check for empty strings in $BUILD_NUMBER to set the snapshot name for ant snapshot target.
ant release: builds Voldemort release version (voldemort-0.52.jar) ant snapshot: builds release snapshot with Hudson build number (voldemort-0.52-snapshot-55.jar)
Uses Hudson propagated BUILD_NUMBER property to add additional build identification tag with each snapshot name.
…g down the routed store, but if server-side routing is disabled it does not happen.
…fluent type interfaces. Should be useful for initializing the client from a properties file as well.
…rapper around an in-memory store that exposes a JMX pause and unpause function.
…izes the entire makeObject() call. This means that only one connection to ANY server can be connecting at a time. This problems shows up quite severely when you have a host that is hard down on the network, and hence the connection will timeout. Exacerbating this it turns out that java.net.Socket does not use the soTimeout when establishing the connection, so we were getting a near infinite timeout which blocked all other connections from being established. Fix is to use soTimeout when establishing a connection, and also upgrade to new version of commons pool which seems to have fixed (or mostly fixed) this problem.
… is shutting down. Apparently calling interrupt() on blocking IO does not have any effect for sockets. To fix, added a Map of active sessions. Each session removes adds itself to the map when it begins and removes itself when it is done. This allows the addition of a killSessions() method in SocketServer that will forcefully close all the open sockets and thereby terminate the client connections.
…te admin port, as this is now just another supported protocol.