Thanks. Found something. Will take a while to see if it is the problem or only the first problem to be found.
I had not (imagine me blushing) added the setenv.sh file into Tomcat's bin folder. I had only put the memory setting into setenv.local in Tomcat's conf folder. That meant I was never changing the memory available as I modified setenv.local. Noticed this was the problem when I came in this morning and found Jenkins unresponsive. Did a ps and saw the command lines for the Jenkins task and the build task. The build task command line had the -X settings for memory but the Jenkins (well ... really tomcat) task didn't. That was the last clue that sent me looking into how to change Tomcat's memory settings. The "out of memory" may be telling me it needs more memory what with all the builds now being done (and the new Jenkins version). I guess I'll find out given some time. Thanks to everyone. Lee On Thu, Feb 9, 2012 at 10:10 AM, Les Mikesell <lesmikes...@gmail.com> wrote: > On Thu, Feb 9, 2012 at 9:17 AM, Lee Meador <l...@leemeador.com> wrote: > >> >> Any ideas on how to figure out whether it just needs more memory or >> something is eating (slowly or rapidly) itself out of memory space? >> >> > Give the jvm enough more memory to run longer and then monitor with > jconsole to see if the usage levels out eventually or keeps creeping up. > > -- > Les Mikesell > lesmikes...@gmail.com > > -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com
