[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
SCM/JIRA link daemon commented on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Code changed in jenkins User: Kohsuke Kawaguchi Path: pom.xml war/pom.xml http://jenkins-ci.org/commit/jenkins/2394c0cd0e233449c85da3bc75628420a2b07a05 Log: FIXED JENKINS-18366 Winstone is now powered by Jetty (cherry picked from commit b19f4650d7cc146e28398a33ad0625d46991e27f) Conflicts: changelog.html war/pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
dogfood commented on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Integrated in jenkins_main_trunk #3787 FIXED JENKINS-18366 Winstone is now powered by Jetty (Revision 2394c0cd0e233449c85da3bc75628420a2b07a05) Result = SUCCESS jesse glick : 2394c0cd0e233449c85da3bc75628420a2b07a05 Files : war/pom.xml pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
Jesse Glick resolved JENKINS-18366 as Fixed Jetty should be used rather than Winstone for embedded deployments @maschuru migration to jetty seem to ignore JENKINS_HOME File a separate bug (with a JIRA link) please. Do not reopen this one. Change By: Jesse Glick (30/Jan/14 4:45 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
S Stack commented on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Solaris 10: CLI broken at Jenkins 1.535+ Per https://issues.jenkins-ci.org/browse/JENKINS-20128?focusedCommentId=188660page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-188660, CLI works fine up to and including 1.534 @Josh, we're running Solaris 10 and while the Jenkins UI appears to work just fine in 1.535 and above, the CLI hangs: java -jar 1.538/WEB-INF/jenkins-cli.jar -s http://cits.icc.intcx.net:8080 version Exception in thread "main" java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:385) at java.net.Socket.connect(Socket.java:546) at hudson.cli.CLI.connectViaCliPort(CLI.java:211) at hudson.cli.CLI.init(CLI.java:134) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) at hudson.cli.CLI._main(CLI.java:469) at hudson.cli.CLI.main(CLI.java:384) Observations Jetty is unpacked to the -Djava.io.tmpdir directory regardless of setting -DJETTY_HOME=/some/dir/. JNLP port is enabled; setting this to either random or a fixed port did not address the CLI timeout. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
Joshua Wherrett commented on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Hi, I am having trouble getting the Jenkins webpage up using a Solaris 10 server (JRE 1.6.0_26-b03). The log shows Jenkins started successfully (Jenkins is fully up and running). However when I try to connect using a web browser (tried IE and Firefox from Jenkins server localhost and remote machines) it hangs indefinitely. Checking netstat shows the connection is ESTABLISHED. All versions of Jenkins prior to 1.535 work perfectly under Solaris 10 and no versions after 1.534 work. So I can only assume it was the introduction of Jetty in 1.535 that has caused this issue. Cheers, Josh This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
Benjamin Dewez
commented on JENKINS-18366
Jetty should be used rather than Winstone for embedded deployments
I have the same error with our Jenkins after an upgrade to 1.539. It extract the war file into our /tmp folder but this one is cleaned by some other process and I can't guarantee that all files will not be deleted... This is a horrible behavior for us and so, it's blocker.
Nov 20, 2013 3:29:14 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: jetty-8.y.z-SNAPSHOT
Nov 20, 2013 3:29:14 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Extract jar:file:/usr/lib/jenkins/jenkins.war!/ to /tmp/jetty-0.0.0.0-8181-jenkins.war-_jenkins-any-/webapp
Nov 20, 2013 3:29:16 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: NO JSP Support for /jenkins, did not find org.apache.jasper.servlet.JspServlet
Jenkins home directory: /data/jenkins found at: System.getProperty("JENKINS_HOME")
@dev, I have try to use your solution and I define another tmp folder for Jenkins but it still extract its war file into our /tmp folder.
Here an echo of my command line exectuded when I start the service.
Starting Jenkins
JAVA_CMD : /usr/java/java6/bin/java -Djava.awt.headless=true -XX:MaxPermSize=512M -Xms512m -Xmx4096m -DJENKINS_HOME=/data/jenkins -jar /usr/lib/jenkins/jenkins.war
PARAMS : --logfile=/data/logs/jenkins/jenkins.log --webroot=/data/jenkins/war --daemon --httpPort=8181 --ajp13Port=8010 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 -Djava.io.tmpdir=/data/jenkins/tmp --prefix=/jenkins --accessLoggerClassName=winstone.accesslog.SimpleAccessLogger --simpleAccessLogger.format=combined --simpleAccessLogger.file=/var/log/jenkins/access_log
Thx for any help
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
dev @ doxo.com commented on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Hi Benjamin, Looks like you are passing the "-Djava.io.tmpdir" argument to the Servlet container, not to the Java runtime. That "-D" argument needs to be a part of JAVA_CMD. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
Alex Ouzounis commented on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Hi, Just to add my observations here. Following the instructions from dev #comment-189758 the issue is gone for my Jenkins 1.539 installation. The only thing to add is make are that the JENKINS_HOME var is defined before the JAVA_ARGS var. Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
Benjamin Dewez commented on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments @dev, Oh my god, you right ! I define this property into the JENKINS_ARGS and no JAVA_ARGS. I fix this error tomorrow and I keep you aware of the result. Thx This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
Alex Ouzounis edited a comment on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Hi, Just to add my observations here. Following the instructions from dev #comment-189758 the issue is gone for my Jenkins 1.539 installation. The only thing to add is make sure that the JENKINS_HOME var is defined before the JAVA_ARGS var. Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
Jason Belt commented on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments I am seeing something similar to Dennys and Matthias under 1.538 running on Ubuntu 12.04. JENKINS_HOME is set to /var/lib/jenkins and Jenkins is started with the argument -webroot=/var/cache/jenkins/war but Jetty extracts jenkins.war to /tmp/jetty-0.0.0.0-8080-jenkins.warany/webapp. It runs fine for awhile but then some process deletes most of the files under the webapp directory (oddly the directories are not deleted). I tried setting the environment variable JETTY_HOME=$JENKINS_HOME but the war file is still extracted to /tmp. Is there a way to get Jetty to extract it to somewhere other than /tmp? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
Jason Belt edited a comment on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments I am seeing something similar to Dennys and Matthias under 1.538 running on Ubuntu 12.04. JENKINS_HOME is set to /var/lib/jenkins and Jenkins is started with the argument webroot=/var/cache/jenkins/war but Jetty extracts jenkins.war to /tmp/jetty-0.0.0.0-8080-jenkins.warany-/webapp. It runs fine for awhile but then some process deletes most of the files under the webapp directory (oddly the directories are not deleted). I tried setting the environment variable JETTY_HOME=$JENKINS_HOME but the war file is still extracted to /tmp. Is there a way to get Jetty to extract it to somewhere other than /tmp? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
Jason Belt edited a comment on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments I am seeing something similar to Dennys and Matthias under 1.538 running on Ubuntu 12.04. JENKINS_HOME is set to /var/lib/jenkins and Jenkins is started with the argument webroot=/var/cache/jenkins/war but Jetty extracts jenkins.war to /tmp/jetty-0.0.0.0-8080-jenkins.war-any/webapp. It runs fine for awhile but then some process deletes most of the files under the webapp directory (oddly the directories are not deleted). I tried setting the environment variable JETTY_HOME=$JENKINS_HOME but the war file is still extracted to /tmp. Is there a way to get Jetty to extract it to somewhere other than /tmp? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
Dennys Hsieh commented on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments JETTY_HOME works for me on 1.538, thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
Michael D created JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Issue Type: Improvement Assignee: Unassigned Components: core Created: 16/Jun/13 9:06 AM Description: 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 Project: Jenkins Priority: Major Reporter: Michael D This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
