We have been runing Jenkins 1.480 for quite some time. Today we tried upgrading to 1.518 and restarted Jenkins. It seemed to spawn the proper Java process and even seemed to be running jobs but apache just gives 503 errors. I suspect some change between these versions that causes Jenkins to run on a different port than what we are used to. So when running I see:
jenkins 10320 1 9 22:48 ? 00:02:05 /usr/lib/jvm/java-1.6.0/bin/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -XX:MaxPermSize=128m -Xms1536M -Xmx3072M -DJENKINS_HOME=/home/jenkins/home -jar /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --daemon --httpPort=-1 --debug=5 --handlerCountMax=600 --handlerCountMaxIdle=80 --prefix=/jenkins As you can see we use httpPort=-1 because we are using HTTPS apache redirecting to ajp13 via mod_jk. I noticed we are not passing in a value for 'ajp13Port' (because it did not exist before) but it should default to 8009, which is the default ajp13 port in mod_jk. However, I wonder if the real default is 9009 as indicated in the https://wiki.jenkins-ci.org/display/JENKINS/Apache+frontend+for+security section for mod_jk. Anyone have similar issues? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
