-
Improvement
-
Resolution: Fixed
-
Major
-
None
Hudson recently switched to using Jetty as an embedded servlet engine. It has a very small size, and very very good performance.
Put bluntly, the current use of Winstone SUCKS, and due to its threaded design will cause performance to slow to a crawl at 240+ requests a minute even on high end hardware with aggressive varnish caching. At the same time using an external Java EE container isn't that easy, so by following hudson and switching to Jetty we get the best of both worlds.
Thanks
md_5
- depends on
-
JENKINS-20128 HTTP two-way remoting does not work (jenkins-cli.jar without JNLP)
-
- Resolved
-
- is related to
-
JENKINS-20682 Starting Jenkins with defined --webroot or JETTY_HOME not working.
-
- Resolved
-
-
JENKINS-20074 JellyTagException following log message "org.eclipse.jetty.util.log.JavaUtilLog warn"
-
- Resolved
-
Hi Jason,
We ran into the same issue as you with Ubuntu 11.04. What ended up working was the following:
1. Create (or choose) a directory where you want to have the WAR be extracted, and make sure the "jenkins" user has R/W access to it. We ended up using $JENKINS_HOME/tmp
2. Modify the /etc/default/jenkins file to specify the java.io.tmpdir option as an argument to starting Jenkins. For example something like:
JAVA_ARGS="-Djava.io.tmpdir=$JENKINS_HOME/tmp"
3. Restart Jenkins