How to increase Jetty thread pool size for a Nexus Repository running in a container

To increase the Jetty thread pool size for a Nexus Repository running in a container, you need to modify the jetty.xml configuration file inside your Nexus installation. Here’s how you can do it:

1. Locate or copy the jetty.xml file
   • If you are using persistent storage (e.g., with Docker or Kubernetes), copy the default /opt/sonatype/nexus/etc/jetty/jetty.xml from the container to your persistent storage location, such as /nexus-data/etc/jetty/jetty.xml or a similar path used by your deployment.
   • For Helm-based deployments, place your customized jetty.xml in persistent storage and ensure Nexus uses it on startup.
2. Edit the jetty.xml file

   • Open the file and find the section like this:

     <Arg name="threadpool">
         <New id="threadpool" class="org.sonatype.nexus.bootstrap.jetty.InstrumentedQueuedThreadPool">
             <Set name="maxThreads">400</Set>
         </New>
     </Arg>

   • Change the value of maxThreads to your desired number, for example:

     <Set name="maxThreads">800</Set>

3. Ensure Nexus uses your custom jetty.xml
   • For containerized deployments, you need to set the nexus-args in INSTALL4J_ADD_VM_PARAMS environment variable to point to your custom jetty.xml. For example: -Dnexus-args=/nexus-data/etc/jetty/jetty.xml,/opt/sonatype/nexus/etc/jetty/jetty-http.xml,/opt/sonatype/nexus/etc/jetty/jetty-requestlog.xml This ensures Nexus loads your configuration file on startup.
4. Restart the Nexus container
   • A restart is required for the changes to take effect. There is no supported way to reload the Jetty configuration without a restart in a containerized environment.