cells: remove System time dependency in unit-test

The CellNameServiceRegistryTests class provides unit-tests for the
CellNameServiceReigstry.  One of these tests verifies that expired
well-known cells registration is removed successfully, leaving the
existing cells intact.

This patch refacts CellNameServiceRegistry slighly to allow a
subclass to adjust its concept of time.  This is used to provide a
reliable simulated flow of time in the unit-tests, removing the
need for a sleep statement.

cherry-picked from d7f67a79c52fae242d4d531ebe46bd57bdae6936
[maven-release-plugin] prepare release 2.7.19
[maven-release-plugin] prepare for next development iteration
unittests: increase timeouts and fix race in DiskSpaceAllocatorTest

Various unit tests have timeouts to allow the test to fail if it gets
stuck.  While such tests are short-lived and the existing timeouts work
fine for desktop environments, when testing under heavy load the thread
scheduling within the OS can lead to severe delays and the tests could
fail.  For this reason, the timeouts are bumped up to 1 minute.  Tests
should aim to complete easily within one second (number picked out of
the air), so one minute should allow at least 2 orders of magnitude
leeway.

This patch also removes two unnecessary assertions.  These assertions
add nothing against an existing, earlier test and introduce a race
condition for a possible failure mode.

The test in question has a race in attempting to ensure the testing
thread blocks.  This is hard to fix without rewriting the code being
tested and, since it doesn't affect the test result, the code is left
as-is.

Target: master
Patch: https://rb.dcache.org/r/7308/
Acked-by: Tigran Mkrtchyan
Requires-notes: no
Requires-book: no
Request: 2.10
Request: 2.9
Request: 2.8
Request: 2.7
Request: 2.6
configuration: adjust references to deprecated properties

Various places contain references to deprecated properties.  This is
wrong and they should reference the non-deprecated replacement
properties instead.

This patch fixes this.  It is a combination of two patches committed to
master: 9f26723122 and fed4abd3cc, but modified as some of the one-of
values in the property annotations are still needed.

Request: 2.10
Request: 2.9
Request: 2.8
Request: 2.7

Conflicts:
	skel/share/defaults/dcache.properties
	skel/share/defaults/nfs.properties
srm: Fix asynchroneous job storage leak

The asynchroneous job storage fails to preserve the force flag when
collapsing several save calls. In case srm.persistence.enable.history
is false (the default), this could lead to incomplete data in the
database. This in case could lead to incomplete cleanup of upload
directories after an SRM restart.

The patch also renames the boolean parameter to something that I find
less confusing.

Target: trunk
Request: 2.10
Request: 2.9
Request: 2.8
Request: 2.7
Require-notes: yes
Require-book: no
Acked-by: Paul Millar <paul.millar@desy.de>
Patch: https://rb.dcache.org/r/7307/
(cherry picked from commit 98f21155a8927aae68a2619c3738bb31f0110fa1)

Conflicts:
	modules/srm-server/src/main/java/org/dcache/srm/scheduler/FinalStateOnlyJobStorageDecorator.java
Merge pull request #842 from gbehrmann/fix/2.7/rb7307

srm: Fix asynchroneous job storage leak
chimera: fix NPE on '.(parent)()' for root inode

Acked-by: Albert Rossi
Acked-by: Dmitry Litvintsev
Target: master, 2.10, 2.9, 2.8, 2.7, 2.6
Require-book: no
Require-notes: no
(cherry picked from commit 82879878110e5254ae1314c759a5fc4f26aecf0c)
Signed-off-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
pool: Fix xrootd vector read limits

Fixes a bug that caused problems with ROOT 6: dCache provided
too large limits for the readv_ior_max and readv_iov_max
properties.

Target: trunk
Request: 2.10
Request: 2.9
Request: 2.8
Request: 2.7
Request: 2.6
Ticket: http://rt.dcache.org/Ticket/Display.html?id=8461
Require-notes: ues
Require-book: no
Acked-by: Paul Millar <paul.millar@desy.de>
Patch: https://rb.dcache.org/r/7313/
(cherry picked from commit 92b36682cf3dd4aab14dab64ded6bf40e5660f4d)
Merge pull request #854 from gbehrmann/fix/2.7/rb7313

pool: Fix xrootd vector read limits
Merge pull request #846 from kofemann/fix-chimera-npe-2.7

chimera: fix NPE on '.(parent)()' for root inode
The gPlazma cache used by NFS and SRM caches both positive and negative
replies. Unfortunately it also caches failures to communicate with gPlazma.
This means that a transient timeout would be cached too, thus increasing the
effect of the transient error.

This patch resolves this problem by not caching timeouts (which include failure
to communicate with gPlazma).

Other errors are still cached - the correctness of this is debatable when
gPlazma does not distinguish between transient and permanent errors.

Target: trunk
Request: 2.10
Request: 2.9
Request: 2.8
Request: 2.7
Request: 2.6
Require-notes: yes
Require-book: no
Committed: 43ecb8c5ffac90014cf339560ca8f4640584c4bd
Acked-by: Albert Rossi <arossi@fnal.gov>
Patch: https://rb.dcache.org/r/7332
(cherry picked from commit 6bfdfa83d5b51c8601bd30d5de262ae032b14da8)

Conflicts:
	modules/dcache/src/main/java/org/dcache/services/login/CachingLoginStrategy.java

(cherry picked from commit 6e224f4ffeebb7f7ed11404a0b052480cdbcc431)

Conflicts:
	modules/dcache/src/main/java/org/dcache/services/login/CachingLoginStrategy.java
xrootd: Upgrade to xrootd4j 1.3.5

Fixes problems with kXR_set requests.

Ticket: http://rt.dcache.org/Ticket/Display.html?id=8468
Ticket: http://rt.dcache.org/Ticket/Display.html?id=8429
Target: trunk
Request: 2.10
Request: 2.9
Request: 2.8
Request: 2.7
Request: 2.6
Require-notes: yes
Require-book: no
Acked-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Patch: https://rb.dcache.org/r/7344/
(cherry picked from commit 6651bb2e2a72b09239ffcc3d71924159172e617a)

Conflicts:
	pom.xml

(cherry picked from commit 9d1b4a8293ecbf5d49b46f5d2ff5f69b8d6ad301)

Conflicts:
	pom.xml

(cherry picked from commit b378eb91ae326f227fdbe0e4aaba26a6fbde3e8a)

Conflicts:
	pom.xml

(cherry picked from commit 25c1c0c2781417c6624e4669f87e160da89c2a7a)
dcap: fix interaction with Spacemanager

we have to set subject in message to pool as well, as
space manager processes PoolAcceptFileMessage as well.

Ticket: #8456
Acked-by: Dmitry Litvintsev
Target: master, 2.10
Require-book: no
Require-notes: no
(cherry picked from commit 22230c4e1b851891e6f874e00f526d8c2c9bf752)
Signed-off-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Merge pull request #874 from kofemann/fix-dcap-w-sm-2.7

dcap: fix interaction with Spacemanager
Merge pull request #861 from gbehrmann/fix/2.7/rb7332

The gPlazma cache used by NFS and SRM caches both positive and negative replies. Unfortunately it also caches failures to communicate with gPlazma. This means that a transient timeout would be cached too, thus increasing the effect of the transient error.
Merge pull request #870 from gbehrmann/fix/2.7/rb7344

xrootd: Upgrade to xrootd4j 1.3.5
[maven-release-plugin] prepare release 2.7.20
[maven-release-plugin] prepare for next development iteration
cell: Declassify eval failure as a bug

Currently, this is claimed to be a bug:

[Gerds-MacBook-Pro.local] (System) admin > eval sdsd
There is a bug here, please report to support@dcache.org: (3) Eval Result : sdsd

After applying this patch, we get:

[Gerds-MacBook-Pro.local] (System) admin > eval sds
(3) Eval Result : sds

Target: trunk
Request: 2.10
Request: 2.9
Request: 2.8
Request: 2.7
Request: 2.6
Require-notes: yes
Require-book: no
Acked-by: Paul Millar <paul.millar@desy.de>
Patch: https://rb.dcache.org/r/7353/
(cherry picked from commit a85817f89123d0b9ec18e805ef7ce6e9cd360631)

Conflicts:
	modules/dcache/src/main/java/org/dcache/services/ssh2/ConsoleReaderCommand.java

(cherry picked from commit 20efd5e4afcd7f1ba1cfcecbf8ff9109cf8c495f)