Sonatype fully supports versions of Nexus Professional for one year after their release date. Older releases are supported on a best effort basis and the release dates of these versions are listed in our download archives.
Host Operating System
Any Windows, Linux, or Macintosh operating system that can run a supported Sun/Oracle Java version will work. Other operating systems may work, but they are not tested by Sonatype. See here for the list of Oracle certified operating systems.
The most widely used operating system for Nexus is Linux and therefore customers should consider it the best tested platform.
Note: Some customers are running on AIX, HP/UX and Solaris successfully, but these systems are not internally tested. When possible, Sonatype Support will make an attempt to provide support for these systems. However you may still be required to reproduce issues on a standard Linux distribution.
Dedicated Operating System User Account
Unless you are testing the repository manager or running it only for personal use, a Nexus Repository Manager user account specific to the operating system is strongly recommended for running.
The Nexus Repository Manger process user is typically named
nexus and must be able to create a valid shell.
As a security precaution, do not run Nexus as the root user.
Adequate File Handles
The Nexus Repository Manager process may want to consume more file handles than the default value allowed by your operating system.
We recommend increasing the available file handles for Nexus preemptively to avoid potential errors at runtime.
Sonatype Nexus is a Java server application that requires specific versions to operate.
Supported Sun/Oracle JRE version
|1.9 and earlier||5 or 6|
|2.0-2.5||6 or 7|
8+ will not work
8+ may work but is not thoroughly tested
|2.11.2-2.13.0||8u31+ strongly recommended
7u79+ no further public updates as of April 2015
|2.14.x+||The most recent version of Java 8 available.
Java 7 is not tested and problems using Java 7 will not be addressed.
We strongly suggest using the latest compatible release version of Java available from Oracle.
OpenJDK has been known to work in most cases, but we do not actively test it. Additionally, GCJ will not work and is not supported.
IBM JDK can be used on systems that do not have a Sun/Oracle JRE available, but our support of this is done on a best effort basis. There are known issues with IBM Server Name Indication (SNI) support which can cause some proxy repositories to SSL based remotes not work correctly.
Java Cryptography Extension (JCE)
Java Cryptography Extension (JCE) is required by some Nexus features. This includes Secure Central and Smart Proxy.
If you see
java.security.InvalidKeyException: Illegal key size in your log is an indicator that Nexus requires the JCE.
It is the user's responsibility to verify that installing JCE is permissible under local regulations. Installing it allows stronger encryption algorithms to be used.
Obtain JCE from your JVM vendor:
Nexus Repository Manager performance is primarily bounded by IO (disk and network) rather than CPU. So any reasonably modern 2-4 core CPU will generally be sufficient for normal use.
The default JRE max heap size of Nexus Professional is 768Mb, and the codebase of Nexus Repository Manager will consume approximately another 1GB. So factoring in operating system overhead you will need at least 4GB of RAM, assuming no other large applications are running on the machine.
For very large Nexus Repository Manager instances you will need to bump up the maximum heap space. If you do this you should increase RAM on the system accordingly.
Sonatype Nexus, installed, consumes less than 100MB. The bulk of disk space will be held by your deployed and proxied artifacts, as well as any search indexes. This is highly installation specific.
For a detailed discussion of disk space, see this article.
You should note that downloading some search indexes, like Maven Central, can consume several GB of disk.
There are strategies to manage the disk space consumed by Nexus Repository Manager.
We have some optimization suggestions to use at your discretion. We recommend to avoid using NFS for the repository manager search index and storage locations, especially in large installations, as this will impact performance. Also consider the
noatime option for your work directory mounts and limit the symbolic links used as this will cause increased overhead whenever the repository manager needs to resolve an absolute file path.
Our general policy is to support the most recent modern browser version for your supported OS at time of Nexus release date. This table is updated for the most recent Nexus release.
|Google Chrome||latest at Nexus release|
|Firefox||latest and ESR at Nexus release|
|Safari||on OSX only, latest at Nexus release|
|Opera||untested and not supported|
|Internet Explorer||9, 10, 11 Check this article for known issues.|