Nexus Repository Manager 3.3.1 Release Notes

This is not the latest version.
Please download and use the latest version of Nexus Repository Manager 3.

Nexus Repository Manager 3.3.1 Release Notes

These notes are a compilation of new features and significant bug fixes for Nexus Repository Manager 3.3.1.

See the complete release notes for all resolved issues.

New and Noteworthy

This is a targeted release to address some key issues with blob store operations.

Refetch Proxy Repository Content When a Blob is Missing

Prior to this release, if the blob (binary content) for proxy repository asset was marked as soft-deleted, an error would be logged return 500 status returned to the calling client. Now, the content will be re-fetched from the remote and if still not available, an appropriate 404 status will be returned. [ NEXUS-12388].

We have also made two internal improvements to blob write operations under concurrent load in order to increase resiliency. [ NEXUS-13030, NEXUS-13032 ]

Record Blob Soft-Deletion Reason

Soft-deleted binary content intentionally remains on disk until the blob store is compacted. In rare cases some blobs were being referenced as soft-deleted unexpectedly. To help diagnose such a situation, the reason a blob is soft-deleted will be recorded in its accompanying .properties file. [ NEXUS-13035]

Upgrading from 2.x

If you’re upgrading from Nexus Repository 2, you must first upgrade your installation to 2.14.4 .

General Improvements


  • [ NEXUS-13030] Improvement automatically retry blob creation when a UUID collision is detected
  • [ NEXUS-13035] Improvement add a diagnostic reason for soft-deleting a blob to the blob properties file


  • [ NEXUS-9872] Improvement misconfigured docker proxy URL should log more details about critical failures at default log levels
  • [ NEXUS-12793] Bug if java.lang.Error is thrown during request processing it may not be logged at default log levels

Proxy Repository

  • [ NEXUS-13032] Improvement eliminate soft-deleted blobs and reduce transaction retries for identical proxy repository asset requests performance
  • [ NEXUS-12388] Improvement attempt to refetch proxy repository content from remote when a referenced local blob is missing
Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk