On Thu, May 5, 2011 at 3:03 PM, Thomas Freitag <tho...@freit.ag> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Jakub, > > On 05/05/2011 02:19 AM, Jakub Królikowski wrote: >> I made an Tomcat and JVM upgrade few weeks ago (to Tomcat 6.0.32 and >> jdk 1.6.0.24), and since that time I can notice a very strange >> behavior: >> sometimes, even once a day, Tomcat stops suddenly. There is no java >> process anymore, there is no errors in catalina.out log file, >> and, what is the most confusing, there is no hs_err_pid*.log file >> anywhere, or I cannot find it. >> Before upgrade, if jvm crashed, the hs_err_pid*.log file was always in >> root home directory. > > I'm not really sure if the hotspot error file is placed in the home > directory or the current working dir. Two java options might help you: > 1) -XX:ErrorFile=<path>/hs_err_pid%p.log (I usually place the file in > the tomcat log directory ($CATALINA_BASE/logs). > 2) -XX:OnError=<executable> (You can run any command you like).
Thanks, I will observe logs for a while now! > > Your milage may vary, if the JVM is killed with SIGKILL, no files will > appear. > >> This is my enviroment, takes with JMX: >> >> VM arguments: >> -Djava.util.logging.config.file=/usr/lib/tomcat/conf/logging.properties >> -Xmx3000m -Xms1500m -Xmn700m -XX:PermSize=768m -XX:MaxPermSize=1000m >> -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode >> -XX:+CMSIncrementalPacing -XX:CMSIncrementalDutyCycleMin=0 >> -XX:CMSIncrementalDutyCycle=10 -XX:+UseParNewGC >> -XX:+CMSClassUnloadingEnabled -XX:MaxGCPauseMillis=250 >> -XX:MaxGCMinorPauseMillis=100 >> -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false >> -Dcom.sun.management.jmxremote >> -Dcom.sun.management.jmxremote.authenticate=true >> -Dcom.sun.management.jmxremote.password.file=/usr/lib/tomcat/conf/jmxremote.password >> -Dcom.sun.management.jmxremote.access.file=/usr/lib/tomcat/conf/jmxremote.access >> -Dcom.sun.management.jmxremote.ssl=false >> -Djava.rmi.server.hostname=xxx.xxx.xxx.xxx >> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager >> -Djava.endorsed.dirs=/usr/lib/tomcat/endorsed >> -Dcatalina.base=/usr/lib/tomcat -Dcatalina.home=/usr/lib/tomcat >> -Djava.io.tmpdir=/usr/lib/tomcat/temp > > Looks okay for me, just curious: Do you really need that large perm gen? You mean these params: "-XX:PermSize=768m -XX:MaxPermSize=1000m" ? Well, my app is under intensive development now and I need to reload context quite often. I know it's a big numbers, but without that after few reloads I'm getting a memory exception. > > Regards, > - -- > Thomas Freitag > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAk3CoAsACgkQGE5pHr3PKuVowACfdMOwEeqq7Hyjta6ZmJZ74z7j > 9LwAnjXR4vJ69gqC7cxxn5v4whEPV8iP > =W1xu > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > 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
