Location of the lock store is not configurable

During LockManager initialisation there is some code that instantiates an object store bean directly (using the new operator) but this bypasses the config properties. In particular the results in the creation of an object store relative to the current directory instead of the configured store location.