Skip navigation

We've made two changes to our repository configuration as brought up in the forum (  The first is that the proxy repositories have been added to the public group.  This means that the public configuration can be used for both anonymous and developer builds.  This should not have an impact on existing build configurations and it should allow the recommended build configuration to be simplified.


The other configuration change that took place over the weekend is that the server has been configured to allow standard http requests for the public repository group (  Other parts of the repository (including anything that requires a login) will still require https.  No formal performance testing has been done so far, but downloads seem to be significantly faster using standard http.


The wiki documentation related to the recommended Maven settings will be updated this week to reflect these changes.

We are continuing to work on improving the performance of the Maven repository.  Last week Sonatype suggested that we remove the custom-metadata-plugin due to a possible memory leak.  We also increased the amount of memory available to Nexus from 512 MB to 1024 MB.  This was done Monday (Apr 26) evening and the server was restarted.  This seems to have improved the memory issues.

We also had a problem starting last Thursday (Apr 29) where certain maven metadata files could not be downloaded.  The server logs contained an error message about too many files being open on the server.  Gradually more files became locked until the whole system became unresponsive.  After restarting Nexus, this problem disappeared.  The operating system open files limit on the server has also been increased to avoid this problem in the future.


This week Sonatype made a configuration change to our authentication configuration (moving the internal Nexus realm before the http realm) which should improve the performance of the security system, and reduced some of the errors/warning we were seeing in the logs.  We have also noticed some timeouts ( when deploying snapshots to the server, but we have not yet determined the cause of this.


In the near future we're also planning to change the configuration of our QA environment (hudson) which should reduce the load on our main repository server.  We're also planning to upgrade Nexus to version 1.6.0 which includes many bug fixes.