Known Issues

Ruby gems connection leak to S3. Check for a non-closed stream that may cause a leak.

When running with Microsoft SQL database, after upgrading to version 6.13, deploying/deleting artifacts/directories and deleting existing repositories will fail with an error.
For example, "Could not check if Repo path 'generic-local:foo.bar' is related to a Release Bundle"

RTFACT-18664

Users associated with a group that is configured with admin privileges and additional non-admin group(s), do not have admin privileges.

After upgrading Artifactory to 6.6 and above, starting Artifactory can take long period due to index validation in the Oracle database

JFrog Artifactory 6.3.0 is not backwards compatible with previous versions for the purposes of distributing release bundles. Therefore, when distributing release bundles between Artifactory services with JFrog Distribution, you need to ensure that either both source and target services are version 6.3.0 and above, or they are both below version 6.3.0.

6.0.2

5.11.1

6.1.0

5.11.2

When upgrading from version below 5.7 to version 5.7 and above while the Artifactory password encryption is enabled, Artifactory will fail to start up with the following error in logs: Couldn't convert configs encryption: javax.crypto.BadPaddingException: Given final block not properly padded : Couldn't convert configs encryption

Running apt-get update on Ubuntu Trusty (14.04) against Debian repositories fails with the following error: Sub-process https received a segmentation fault

For Artifactory HA installations, single-phase upgrades (with downtime) from version 4.x to version 5.6 without going through version 5.4.6 fails. Please refer to the Upgrade Notice in the Artifactory 5.5 Release Notes.

When resolving a package from an npm repository, Artifactory throws a deserialize error to the log file if one of the package's dependencies in the corresponding package.json file is declared using the following format:

“<dependency_name>” : { “version” : “<version_number>” }.

For example: "deep-diff" uses this format. As a result, the npm client fails to resolve the package.

Note: For a workaround, please refer to the issue details.

A system import on a High Availability installation of Artifactory 5.4.x with files exported from a version that is below 5.4, will fail.

RTFACT-14510

RTFACT-14279

Following an upgrade from Artifactory version 4.4 or below to 5.3 directly, Artifactory will fail to start up.  
23-May-2017: If upgrading from 4.4 or below, we recommend waiting for a patch which should be released shortly.

Note: Upgrading from version 4.4.1 and above to 5.3 is not affected and Artifactory will start up after the upgrade.

RTFACT-14619

User Plugins that contain the realms execution point will fail to be executed and throw an HazelcastSerializationException exception when running on Artifactory HA installations.

Most downloaded widget in Artifactory home can cause the DB to stall.

RTFACT-13764

When viewing Smart Remote Repositories in the tree browser, folders under the repository that contain a space in their names, will not expand.

'npm install' fails when all of the following conditions occur together:

• You are trying to resolve a scoped package from a virtual repository and,
• The scoped package is actually hosted under one of the remote repositories aggregated by the virtual repository and,
• That remote repository has 'Store artifacts locally' disabled.

Python metadata calculation will fail if the Python metadata version is set to 1.2 inside the METADATA or PKG-INFO files.

NuGet virtual repositories that aggregate more than one local or remote repository may omit results when searching for a package

Uploading a file containing a dot in the target path will fail and a 500 error will be returned to the client

Note: The maven-site-plugin creates upload URLs containing a dot. Therefore, uploading artifacts through the plugin is currently not supported

RTFACT-13618

When all artifacts have been deleted from a folder, the folder is not pushed to the pruning queue even though it is empty, and is, therefore, not deleted.