Thanks guys for you replys,
Carl - Please update this thread with results of your check for 6u20.
I've decided to install x86 version of JDK - jdk-6u7-linux-i586.bin
(stability is my main concern now)
So in my installation I just installed jdk-6u7-linux-i586.bin version.
1. Changed symlink:
# rm jdk
# ln -s jdk1.6.0_07 jdk
2. Updated paths with:
# alternatives --remove jar /srv/jdk1.6.0_18/bin/jar
# alternatives --remove java /srv/jdk1.6.0_18/bin/java
# alternatives --remove javac /srv/jdk1.6.0_18/bin/javac 100
# alternatives --install /usr/bin/java java /srv/jdk1.6.0_07/bin/java 100
# alternatives --install /usr/bin/jar jar /srv/jdk1.6.0_07/bin/jar 100
# alternatives --install /usr/bin/javac javac /srv/jdk1.6.0_07/bin/javac 100
# /usr/sbin/alternatives --config java
There are 2 programs which provide 'java'.
Selection Command
-----------------------------------------------
*+ 1 /srv/jdk1.6.0_18/bin/java
2 /srv/jdk1.6.0_07/bin/java
Enter to keep the current selection[+], or type selection number: 2
# java -version
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
3. Updated setenv.sh to some basic defaults:
# cat /srv/tomcat/bin/setenv.sh
export JAVA_HOME=/srv/jdk
export PATH="${PATH}:${JAVA_HOME}/bin/"
# CATALINA_OPTS="-server -XX:+UseParallelGC -Xms2048m -Xmx2048m
-XX:MaxPermSize=1024m -XX:+CMSClassUnloadingEnabled
-XX:+CMSPermGenSweepingEnabled -Djava.awt.headless=true"
CATALINA_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=512m $JAVA_OPTS
-Djava.awt.headless=true "
export CATALINA_OPTS
export CATALINA_PID="$CATALINA_HOME/tomcat.pid"
I'm going to monitor this server and see how it goes.
Best Regards,
Leon Kolchinsky
On Thu, May 27, 2010 at 00:20, Carl <c...@etrak-plus.com> wrote:
> I am the person who reported occasional but persistent abrupt terminations
> of the 1.6 JVM on levels 6u10 and above. I did go back to 6u7 and the
> application has run without a burp for three months. I had tested
> 6u18/6u19, both of which produced the same result. I am getting ready to
> start testing 6u20 as I would like to keep current so I don't have any
> security issues hanging out.
>
> Thanks,
>
> Carl
> ----- Original Message ----- From: "Caldarale, Charles R" <
> chuck.caldar...@unisys.com>
> To: "Tomcat Users List" <users@tomcat.apache.org>
> Sent: Wednesday, May 26, 2010 8:00 AM
>
> Subject: RE: Tomcat died on "java.lang.OutOfMemoryError: requested
> 2147483664 bytes for Chunk::new. Out of swap space?" message
>
>
> From: Caldarale, Charles R
>> Subject: RE: Tomcat died on "java.lang.OutOfMemoryError: requested
>> 2147483664 bytes for Chunk::new. Out of swap space?" message
>>
>> The current JVM version is 6u20, so you might want to try running with
>> that before filing a bug report or expanding the swap file.
>>
>
> Should also mention that another Tomcat admin reported occasional but
> persistent abrupt terminations of the 1.6 JVM on levels 6u10 and above, but
> went back to 6u7 and that appeared to rectify the problem. I think the
> highest level he had tested was 6u17, but I'm not positive.
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you received
> this in error, please contact the sender and delete the e-mail and its
> attachments from all computers.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
