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 chan
On Thu, Feb 9, 2012 at 9:17 AM, Lee Meador 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 leve
cifics
>
> -- Sami
>
> Lee Meador kirjoitti 8.2.2012 kello 20.24:
>
> > Jenkins 1.446 running under Tomcat 6.0.32, Sun/Oracle Java 1.6 64bit on
> > RHEL 5.6 Linux 64 bit. That's all running an a VSphere VM with two cpus and
> > 6 GB memory.
> >
>
>
> Lee Meador kirjoitti 8.2.2012 kello 20.24:
>
> > Jenkins 1.446 running under Tomcat 6.0.32, Sun/Oracle Java 1.6 64bit on
> RHEL 5.6 Linux 64 bit. That's all running an a VSphere VM with two cpus and
> 6 GB memory.
> >
> > The Tomcat task dies now and then.
.2012 kello 20.24:
> Jenkins 1.446 running under Tomcat 6.0.32, Sun/Oracle Java 1.6 64bit on RHEL
> 5.6 Linux 64 bit. That's all running an a VSphere VM with two cpus and 6 GB
> memory.
>
> The Tomcat task dies now and then. For example, it died this morning around
> 4:15 (
Jenkins 1.446 running under Tomcat 6.0.32, Sun/Oracle Java 1.6 64bit on
RHEL 5.6 Linux 64 bit. That's all running an a VSphere VM with two cpus and
6 GB memory.
The Tomcat task dies now and then. For example, it died this morning around
4:15 (based on when the monitoring plugin quit sh
