For those who also suffer from the same pain: I never had this problems
again as soon as I updated to 1.502 and increases MaxPermGen to 128m.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving
Thank you so much for your kind help!
Jenkins 1.500 is running on Tomcat 6 / JDK 1.6.0_18 / Debian 6 / x86.
Configured inside is JDK 1.6.0_38 and JDK 1.7.0_11, and Maven 3.0.4. I
downloaded the latest and greatest WAR and put into
/var/lib/tomcat6/webapps as ROOT.war (so it is the only bound
Meanwhile I restarted Jenkins and started another build on all projects.
The result was that all threads on master and slave ended up in a Dead
(!) state, and the Jenkins log said that Jenkins had a
ArrayIndexOutOfBoundException when loading the latest build. I gave it
another reboot and
Depends on what container Jenkins is hosted in. Could you provide some
environment details?
Thanks
Michael
On 10 Feb 2013, at 12:10, Markus KARG mar...@headcrashing.eu wrote:
Meanwhile I restarted Jenkins and started another build on all projects.
The result was that all threads on master and
Still Tomcat6 / JDK 1.6.0_18 / Debian 6 / x86.
Am Sonntag, 10. Februar 2013 14:11:03 UTC+1 schrieb Michael Clarke:
Depends on what container Jenkins is hosted in. Could you provide some
environment details?
Thanks
Michael
On 10 Feb 2013, at 12:10, Markus KARG
Til today my Jenkins 1.500 worked well.
Then I started setting up a Windows slave, and added a few free style ant
projects running on that slave.
It all was good, but since I copied one of that free style projects, my
dashboard is running crazy.
It misses builds that just finished a minute ago.
One more nice thing detected now... Clicked on build now, build
finished successfully, then clicked on the build number to see the result,
got 404 NOT FOUND!
Am Samstag, 9. Februar 2013 19:28:21 UTC+1 schrieb Markus KARG:
Til today my Jenkins 1.500 worked well.
Then I started setting up a
Sorry, but ... Have you tried turning it off and on again? :)
And check the stdout and stderr of Jenkins. Is it printing exceptions and/or
stacktraces? If so, put them into pastebin/gist and tell us. Also it might be
helpful to see your config.xml files (and remember to remove any sensitive
