Examples of org.sonatype.nexus.proxy.maven.routing.internal.ManagerImpl

Default implementation.

Notes on synchronization. As of 2.4,

periodic autorouting metadata updates are performed without holding any locks on path prefix file (i.e. .meta/prefixes.txt). Instead, ConstrainedExecutor is used to avoid multiple concurrent execution of periodic autorouting metadata updates. If new periodic update is requested while the previous one is already running, which is theoretically possible if update takes longer than update check period (1 hour as of 2.4), ConstrainedExecutor will prevent second concurrent execution.
during period update existing metadata, if any, is kept available throughout update and is changed as one relatively short prefix file update performed while holding write, i.e. exclusive, lock on the prefix file.
contents of the prefix file is cached in memory on first request and the cache is refreshed on each change to the prefix file. reading of the prefix file into the memory cache is performed while holding read, i.e. shared, lock, which is necessary to prevent reading prefix file partially written by concurrently running prefix file update.
during repository deploy/delete operations, prefix file contents is first read while holding read lock, then, if the operation results in changes to the prefix file, the prefix file is read-updated-written while holding write long. This allows concurrent execution of multiple repository deploy/delete operations that do not require changes to the contents of the prefix file.

@author cstamas @since 2.4

Related Classes of org.sonatype.nexus.proxy.maven.routing.internal.ManagerImpl