Search code examples
maventomcatnexusarchiva

nexus on tomcat stops responding - alternative to this repository manager

Last year I got virtual server for my server needs, configuration is not great, but things work without problem... Few months ago I installed Nexus Repository manager and after that I have daily problem with tomcat... I now restart machine every night, but still it seems that nexus is unavailable most of time.

I am working on OS project and we need to have repository manager (RM) available to host all our stuff and also all libraries our project needs...

I have currently 3 options (how to solve this problem):

  1. Downgrading maven version to 1.6 (or at least some that is stable and doesn't need so much resources)
  2. Using artifactory (their package seems to be the same size as nexus, but I don't know if it will be better - resource wise)
  3. Using archiva (no idea how stable this is and how good it is)

I am thinking about going with option 3, I just don't know if this is right solution. I am sure some of you have your own RM running, what would you recommend? Do you have perhaps any other options? If I use option 1, which version would you recomend...

Thanks in advance, Andy

Solution

  • I would suggest to run Nexus with the native jetty as supplied by the default download bundle instead of on tomcat. This will give you better performance and also better support.

    Of course if you can get all libraries into the Central Repository via OSSRH it would be even easier since you could get by without maintaining a repository manager altogether.