Re: tomcat crashes with Java1.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Rejesh, On 1/26/17 9:54 PM, Rajesh Cherukuri wrote: > can some one help me on this , tomcat servers crashes if i use java > 1.7 ir was running fine for more than an year This sounds shockingly similar to this: http://markmail.org/thread/iicz5xyeksaxxi54 - -chris > # # A fatal error has been detected by the Java Runtime > Environment: # # SIGSEGV (0xb) at pc=0x7f1ff1018787, > pid=13185, tid=139773910861568 # # JRE version: 7.0_21-b11 # Java > VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode > linux-amd64 compressed oops) # Problematic frame: # J > org.apache.http.impl.cookie.BestMatchSpec.formatCookies(Ljava/util/Lis t;)Ljava/util/List; > > # > # Failed to write core dump. Core dumps have been disabled. To > enable core dumping, try "ulimit -c unlimited" before starting Java > again # # If you would like to submit a bug report, please visit: # > http://bugreport.sun.com/bugreport/crash.jsp # > > --- T H R E A D --- > > Current thread (0x7f1fb426b000): JavaThread "AD Thread > Pool-Global25" daemon [_thread_in_Java, id=31406, > stack(0x7f1fa63e4000,0x7f1fa64e5000)] > > siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), > si_addr=0x003f09db1aac > > Registers: RAX=0x0007e1468c30, RBX=0x0004, > RCX=0x003f09db1aa0, RDX=0x > RSP=0x7f1fa64e3010, RBP=0x0005, > RSI=0x0007e13b6358, RDI=0x0007e13b6354 R8 > =0x0001, R9 =0x0001, > R10=0x7fff, R11=0x > R12=0x, R13=0x00066ea4add8, > R14=0x, R15=0x7f1fb426b000 > RIP=0x7f1ff1018787, EFLAGS=0x00010202, > CSGSFS=0x0033, ERR=0x0004 > TRAPNO=0x000e > -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJYi5UQAAoJEBzwKT+lPKRYOdUP/RFsHGGNHTBaxt0QF2TNSqlm eh3mXDwM5EzBb3oanS6AMzDS0MNnXLO/bZpbThMTRg0Vg9cSSCaew9qAr2P+c9wa xUr+1OTbFyYqUoQaM++oGwxsWHgb7IbXWCvNzwhgXxb/V/VSUjoW20NcVOmRElIU B53iwvPHERYREmRQdCaXIblqk/nGSZANDWC3dEZ6RvnnvtroIvOCbst1FD1oOweK 19hNdl1EBnSqB7w3rWjoepRi5Flv+Mpgd/hlmuaxOm5kapZgExS+Itd1YIwD9lUa x7kcFrUrLDmuy0SWyq3wQCF9+35FYJ+JbsjsxhuBHCJsXpC8K8xxlXWhWl+rTllD kxsbx21MnffKQ7aF7+/j6KNOP8F7paV2EK7m812RL8xoV9bGV/OoGPY1eSiWKFpr 34xFr7U9RzoDp0Th9FZTHWr1WJKHxeh83HudOb3E8k1bHWuxrG8f8Ava3tIM/ccV NSMdS3OoozTrwJd1ZMd5dcNkbGjgZzuvWra69OZQOyksEC96k0//nOGj4yvkD4lE CN0TYRAoo1ASo1a00R882FI2n0LhN4UeN2ZTgqjwaD8f8lXdcB/Hgqfa5pz3he4C EjefDJywNaaKh8tOf0l8Hgc/b4ntHAskOaZII8WvSw+KcN4dp7VuUR7rsLTCnF8z P0NUoMH2/nIGzd4BGIOn =hsS1 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat crashes with java 1.7
Sure ,Will try this On Oct 29, 2016 11:02 PM, "Christopher Schultz" < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Rajesh, > > On 10/28/16 6:41 AM, Rajesh Cherukuri wrote: > > these severs has been migrated , i was told that it was working on > > the source server > > Okay. That gives us no information whatsoever that can help us help you. > > We don't know what the implications of the "servers [have] been > migrated" means or what a "source server" is. > > If what you mean is "these are newly-provisioned servers, and the > servers from which these services were migrated (to the new ones) were > working fine before migration" then I would again steer you toward > running a hardware test on the new servers to make sure you don't have > defective components. > > So many people assume that when they purchase new hardware it's going > to be in perfect working condition. I would say that some significant > percentage of RAM chips I've been sold have been sub-par and required > replacement immediately upon provisioning. I would guess something > like 10% of all RAM chips I've ordered had to be replaced before > seeing any actual service. > > That's why I always demand at least 24-hours of memtest86 or > equivalent, and at least 2 complete cycles through the RAM (sometimes > 2 complete cycles takes more than 24 hours, since RAM sizes are so big > these days). > > I don't have time to waste chasing-down phantom JVM bugs caused by > unreliable hardware. Just run a hardware test and see what happens. If > the hardware seems fine, try a different version of the JVM. > > - -chris > > > On Fri, Oct 21, 2016 at 8:10 PM, Christopher Schultz < > > ch...@christopherschultz.net> wrote: > > > > Rajesh, > > > > On 10/21/16 2:13 AM, Rajesh Cherukuri wrote: > can some one help me on this , tomcat servers crashes if i > use java 1.7 , i have tried chaining this to java 1.6 and i > am be to start the tomcat , issue is only when i use 1.7 > > here is the log when i use 1.7 after it crashes > > Oct 21, 2016 7:37:28 AM > org.apache.catalina.core.StandardService startInternal INFO: > Starting service Catalina Oct 21, 2016 7:37:28 AM > org.apache.catalina.core.StandardEngine startInternal INFO: > Starting Servlet Engine: Apache Tomcat/7.0.53 # # A fatal > error has been detected by the Java Runtime Environment: # # > SIGSEGV (0xb) at pc=0xfbc7e41c, pid=2081, tid=21 # # JRE > version: Java(TM) SE Runtime Environment (7.0_79-b15) (build > 1.7.0_79-b15) # Java VM: Java HotSpot(TM) Server VM > (24.79-b02 mixed mode solaris-sparc ) # Problematic frame: # > J 78 C2 > java.util.HashMap.getEntry(Ljava/lang/Object;)Ljava/util/HashMap$En > try > > > > ; > (86 bytes) @ 0xfbc7e41c [0xfbc7e380+0x9c] > > > > This is a JVM bug and, almost by definition, is not linked to > > Tomcat. > > > > Try switching to a higher or lower version of Java 1.7 (e.g. 7u80 > > or 7.76). > > > > You also might want to test your CPU+RAM to see if they are buggy. > > > > -chris > >> > >> - > >> > >> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > >> For additional commands, e-mail: users-h...@tomcat.apache.org > >> > >> > > > -BEGIN PGP SIGNATURE- > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBCAAGBQJYFN0bAAoJEBzwKT+lPKRYNtcQAIsG3QWPswAKbeCWfI9gLdJZ > YTAN4NZXQ/PIjrQUC4kou00r6SMaumRgraY4qqND9BjISLWkfAvtu0zP3T2gcVB5 > OAykxv6Mzh6IMhIwdQCnQE5xV2a3ce19rLdo5Zgo73nAxPoQDFluU4n8coLij7Vc > 8cpFAhzE6JM8Om/QKnPQCpKYud6Ttv5KHa8PEujg0dlU27RhIbL7Clt6MkHjvJNi > PBbUquSQtq/zVBK1jYQ+TPVtbAQIj9i1lgUNgfhgGD6/Q1oH1rnmODXbSfVwtqe0 > Gh7aMGKCMP4jhkwFQfyVvZqCPtfmEjzQgRQdf49ihEYkIjxizMVPWKrig7ICsI1j > 0Uf3YZDvdasaTXoqkHfodKV++B1MG2L8Sj+VPYc9hkWGMlIlmoFOqzrZfSatvmy5 > P/lUmzrbY6zSTxrhJnubk2RJpg6vfD3Dnl7btvDcBp4zBZQLPZ3DBg6boIL/KQQb > QvkDzZwk0U3n4YN3urpJ7o6HHF15zNDJSBV2tn4j6LFCqyhn0vn3kIB+PpPfopVc > 11X5hUBEM8NBDj9XI0yPOXhNYLyi+3pWF61brAu9HGM0W9NZ87Z0Dj8LsUQXqbv6 > hDZYg67lY+QLBgLvcDIsIxBFn6ThenRiK+c6st1TflwP/MnbaDSI5ETyJV9BaDa9 > lQMBtt/6fqqx/r7Gyl3q > =WDk3 > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: Tomcat crashes with java 1.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Rajesh, On 10/28/16 6:41 AM, Rajesh Cherukuri wrote: > these severs has been migrated , i was told that it was working on > the source server Okay. That gives us no information whatsoever that can help us help you. We don't know what the implications of the "servers [have] been migrated" means or what a "source server" is. If what you mean is "these are newly-provisioned servers, and the servers from which these services were migrated (to the new ones) were working fine before migration" then I would again steer you toward running a hardware test on the new servers to make sure you don't have defective components. So many people assume that when they purchase new hardware it's going to be in perfect working condition. I would say that some significant percentage of RAM chips I've been sold have been sub-par and required replacement immediately upon provisioning. I would guess something like 10% of all RAM chips I've ordered had to be replaced before seeing any actual service. That's why I always demand at least 24-hours of memtest86 or equivalent, and at least 2 complete cycles through the RAM (sometimes 2 complete cycles takes more than 24 hours, since RAM sizes are so big these days). I don't have time to waste chasing-down phantom JVM bugs caused by unreliable hardware. Just run a hardware test and see what happens. If the hardware seems fine, try a different version of the JVM. - -chris > On Fri, Oct 21, 2016 at 8:10 PM, Christopher Schultz < > ch...@christopherschultz.net> wrote: > > Rajesh, > > On 10/21/16 2:13 AM, Rajesh Cherukuri wrote: can some one help me on this , tomcat servers crashes if i use java 1.7 , i have tried chaining this to java 1.6 and i am be to start the tomcat , issue is only when i use 1.7 here is the log when i use 1.7 after it crashes Oct 21, 2016 7:37:28 AM org.apache.catalina.core.StandardService startInternal INFO: Starting service Catalina Oct 21, 2016 7:37:28 AM org.apache.catalina.core.StandardEngine startInternal INFO: Starting Servlet Engine: Apache Tomcat/7.0.53 # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xfbc7e41c, pid=2081, tid=21 # # JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15) # Java VM: Java HotSpot(TM) Server VM (24.79-b02 mixed mode solaris-sparc ) # Problematic frame: # J 78 C2 java.util.HashMap.getEntry(Ljava/lang/Object;)Ljava/util/HashMap$En try > ; (86 bytes) @ 0xfbc7e41c [0xfbc7e380+0x9c] > > This is a JVM bug and, almost by definition, is not linked to > Tomcat. > > Try switching to a higher or lower version of Java 1.7 (e.g. 7u80 > or 7.76). > > You also might want to test your CPU+RAM to see if they are buggy. > > -chris >> >> - >> >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> > -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJYFN0bAAoJEBzwKT+lPKRYNtcQAIsG3QWPswAKbeCWfI9gLdJZ YTAN4NZXQ/PIjrQUC4kou00r6SMaumRgraY4qqND9BjISLWkfAvtu0zP3T2gcVB5 OAykxv6Mzh6IMhIwdQCnQE5xV2a3ce19rLdo5Zgo73nAxPoQDFluU4n8coLij7Vc 8cpFAhzE6JM8Om/QKnPQCpKYud6Ttv5KHa8PEujg0dlU27RhIbL7Clt6MkHjvJNi PBbUquSQtq/zVBK1jYQ+TPVtbAQIj9i1lgUNgfhgGD6/Q1oH1rnmODXbSfVwtqe0 Gh7aMGKCMP4jhkwFQfyVvZqCPtfmEjzQgRQdf49ihEYkIjxizMVPWKrig7ICsI1j 0Uf3YZDvdasaTXoqkHfodKV++B1MG2L8Sj+VPYc9hkWGMlIlmoFOqzrZfSatvmy5 P/lUmzrbY6zSTxrhJnubk2RJpg6vfD3Dnl7btvDcBp4zBZQLPZ3DBg6boIL/KQQb QvkDzZwk0U3n4YN3urpJ7o6HHF15zNDJSBV2tn4j6LFCqyhn0vn3kIB+PpPfopVc 11X5hUBEM8NBDj9XI0yPOXhNYLyi+3pWF61brAu9HGM0W9NZ87Z0Dj8LsUQXqbv6 hDZYg67lY+QLBgLvcDIsIxBFn6ThenRiK+c6st1TflwP/MnbaDSI5ETyJV9BaDa9 lQMBtt/6fqqx/r7Gyl3q =WDk3 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat crashes with java 1.7
Chris these severs has been migrated , i was told that it was working on the source server On Fri, Oct 21, 2016 at 8:10 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Rajesh, > > On 10/21/16 2:13 AM, Rajesh Cherukuri wrote: > > can some one help me on this , tomcat servers crashes if i use java > > 1.7 , i have tried chaining this to java 1.6 and i am be to start > > the tomcat , issue is only when i use 1.7 > > > > here is the log when i use 1.7 after it crashes > > > > Oct 21, 2016 7:37:28 AM org.apache.catalina.core.StandardService > > startInternal INFO: Starting service Catalina Oct 21, 2016 7:37:28 > > AM org.apache.catalina.core.StandardEngine startInternal INFO: > > Starting Servlet Engine: Apache Tomcat/7.0.53 # # A fatal error has > > been detected by the Java Runtime Environment: # # SIGSEGV (0xb) > > at pc=0xfbc7e41c, pid=2081, tid=21 # # JRE version: Java(TM) SE > > Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15) # Java VM: > > Java HotSpot(TM) Server VM (24.79-b02 mixed mode solaris-sparc ) # > > Problematic frame: # J 78 C2 > > java.util.HashMap.getEntry(Ljava/lang/Object;)Ljava/util/HashMap$Entry > ; > > (86 bytes) @ 0xfbc7e41c [0xfbc7e380+0x9c] > > This is a JVM bug and, almost by definition, is not linked to Tomcat. > > Try switching to a higher or lower version of Java 1.7 (e.g. 7u80 or > 7.76). > > You also might want to test your CPU+RAM to see if they are buggy. > > - -chris > -BEGIN PGP SIGNATURE- > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBCAAGBQJYCmg3AAoJEBzwKT+lPKRYoxMP/iDMLrF6o054zEY/PWm13ac7 > 9kjCoukd7lCN0GxrEvtuCuSuCZT5WkLKp318oyEIgd4DRqkuhEyLl1OBz2sNMlw9 > +HODmAoMM2P19FWagL5HFCzhHx/8MTBKsB2FdmKAN6Db6yBJPlqOTBPvigx4jNpq > 1Ub32fn5Rqk3HX+LoyOFCalePOUlJnyz/KQ7XNAMHoHaJAIZ6N/ZQVJjFYLIuChS > ZgSC1CxyZPXcuXTJxQmNasiRlAAU4SpIFBlA4B1h74iSYc5z4YP/cjz0F1v7/UbY > RvovOUa5pj2SgUO9QnBhnpfnqrlqr6hM3ByOLMuQdqnif30eTONmV0yGaOswoQ8s > lpvOVAXGLvI5pbp8IAp9vXDvQSrmnAz/PJAD2uStPCkIvdXAunjqDG2hlqgkvuxP > 1/AkX2LP3Pv4yCgbqGG8o7THmR7+IsV2IYNkvOEKEF+pIKIVCh493uE6ST069mSL > +OiyvZv9tGgVEp61bgpIKhb5vCZj+4uaVoXzF37dLNWTNrWG9uTMeEbnh21tAsNO > CcSgWpodXZC3jRlnKv+pM62hNRxONtVHO4sFHMqN0PsG2Qlv4ldDXmq726aUCk1r > 3gaCrTMAjjbwLdzzrNtMnsfxQF8I7sK8bLy9cjyt9rB2vDhrFNE7U+kgkLz2xEn3 > JYX9YS53PxfN24kCe6ue > =k9kI > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: Tomcat crashes with java 1.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Rajesh, On 10/21/16 2:13 AM, Rajesh Cherukuri wrote: > can some one help me on this , tomcat servers crashes if i use java > 1.7 , i have tried chaining this to java 1.6 and i am be to start > the tomcat , issue is only when i use 1.7 > > here is the log when i use 1.7 after it crashes > > Oct 21, 2016 7:37:28 AM org.apache.catalina.core.StandardService > startInternal INFO: Starting service Catalina Oct 21, 2016 7:37:28 > AM org.apache.catalina.core.StandardEngine startInternal INFO: > Starting Servlet Engine: Apache Tomcat/7.0.53 # # A fatal error has > been detected by the Java Runtime Environment: # # SIGSEGV (0xb) > at pc=0xfbc7e41c, pid=2081, tid=21 # # JRE version: Java(TM) SE > Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15) # Java VM: > Java HotSpot(TM) Server VM (24.79-b02 mixed mode solaris-sparc ) # > Problematic frame: # J 78 C2 > java.util.HashMap.getEntry(Ljava/lang/Object;)Ljava/util/HashMap$Entry ; > (86 bytes) @ 0xfbc7e41c [0xfbc7e380+0x9c] This is a JVM bug and, almost by definition, is not linked to Tomcat. Try switching to a higher or lower version of Java 1.7 (e.g. 7u80 or 7.76). You also might want to test your CPU+RAM to see if they are buggy. - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJYCmg3AAoJEBzwKT+lPKRYoxMP/iDMLrF6o054zEY/PWm13ac7 9kjCoukd7lCN0GxrEvtuCuSuCZT5WkLKp318oyEIgd4DRqkuhEyLl1OBz2sNMlw9 +HODmAoMM2P19FWagL5HFCzhHx/8MTBKsB2FdmKAN6Db6yBJPlqOTBPvigx4jNpq 1Ub32fn5Rqk3HX+LoyOFCalePOUlJnyz/KQ7XNAMHoHaJAIZ6N/ZQVJjFYLIuChS ZgSC1CxyZPXcuXTJxQmNasiRlAAU4SpIFBlA4B1h74iSYc5z4YP/cjz0F1v7/UbY RvovOUa5pj2SgUO9QnBhnpfnqrlqr6hM3ByOLMuQdqnif30eTONmV0yGaOswoQ8s lpvOVAXGLvI5pbp8IAp9vXDvQSrmnAz/PJAD2uStPCkIvdXAunjqDG2hlqgkvuxP 1/AkX2LP3Pv4yCgbqGG8o7THmR7+IsV2IYNkvOEKEF+pIKIVCh493uE6ST069mSL +OiyvZv9tGgVEp61bgpIKhb5vCZj+4uaVoXzF37dLNWTNrWG9uTMeEbnh21tAsNO CcSgWpodXZC3jRlnKv+pM62hNRxONtVHO4sFHMqN0PsG2Qlv4ldDXmq726aUCk1r 3gaCrTMAjjbwLdzzrNtMnsfxQF8I7sK8bLy9cjyt9rB2vDhrFNE7U+kgkLz2xEn3 JYX9YS53PxfN24kCe6ue =k9kI -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat crashes after startup
Chris, Here is the first few lines of the output.. I don't think I want to copy my entire cert here. ___ F:\Serena\Dimensions 2009 R2\Common Tools\jre\6.0\bin>keytool -list -v -keystore wcmdev-ssl.jks -alias tomcat Enter keystore password: Alias name: tomcat Creation date: Nov 10, 2011 Entry type: trustedCertEntry Owner: CN=wcmdev.nexweb.us, OU=USN, OU=PKI, OU=DoD, O=U.S. Government, C=US Thanks, Justin LaRose Database & Web Services Administrator NEXCOM (757) 631-3443 justin.lar...@nexweb.org From: Christopher Schultz To: Tomcat Users List Date: 12/13/2011 03:08 PM Subject: Re: Tomcat crashes after startup -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Justin, On 12/13/11 8:35 AM, Justin Larose wrote: > I actually followed the document here: > http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html because I am > using Tomcat 6. Okay. You just hadn't mentioned that (version) before. > I also did import the cert with the alias "tomcat" (see screenshot > below). Is there an order in which to import the certs? I imported > the server cert first, then the CA, then the root cert. Your screenshot has been suppressed from the list. Instead, can you post a text copy/paste for a "keytool -list"? > "I would advise against using the same keystore for both the > "keystore" and the "truststore". The trust store is only used for > validating client certificates and, IMO, should be kept separate > from the certificates you use for the web service itself." > > These config settings were in place long before I worked here... I > was just copying the info from the old server.xml and adding in the > new keystore info. If we do not Use any client certs can I remove > the truststore line? Almost certainly. You probably want to fix one problem at a time, though. :) - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7nsIkACgkQ9CaO5/Lv0PD1EgCeNlYJ1udAFvbU4LGOw0lAxrKc s/0An3XMoGo1WCkYjRe7OhJ9gkdj1GlK =ANqY -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat crashes after startup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Justin, On 12/13/11 8:35 AM, Justin Larose wrote: > I actually followed the document here: > http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html because I am > using Tomcat 6. Okay. You just hadn't mentioned that (version) before. > I also did import the cert with the alias "tomcat" (see screenshot > below). Is there an order in which to import the certs? I imported > the server cert first, then the CA, then the root cert. Your screenshot has been suppressed from the list. Instead, can you post a text copy/paste for a "keytool -list"? > "I would advise against using the same keystore for both the > "keystore" and the "truststore". The trust store is only used for > validating client certificates and, IMO, should be kept separate > from the certificates you use for the web service itself." > > These config settings were in place long before I worked here... I > was just copying the info from the old server.xml and adding in the > new keystore info. If we do not Use any client certs can I remove > the truststore line? Almost certainly. You probably want to fix one problem at a time, though. :) - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7nsIkACgkQ9CaO5/Lv0PD1EgCeNlYJ1udAFvbU4LGOw0lAxrKc s/0An3XMoGo1WCkYjRe7OhJ9gkdj1GlK =ANqY -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat crashes after startup
Chris, "You need to have a key in your keystore with the alias "tomcat" as well. If you have been following http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html#Configuration, you have either missed or misinterpreted a step." I actually followed the document here: http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html because I am using Tomcat 6. I also did import the cert with the alias "tomcat" (see screenshot below). Is there an order in which to import the certs? I imported the server cert first, then the CA, then the root cert. "I would advise against using the same keystore for both the "keystore" and the "truststore". The trust store is only used for validating client certificates and, IMO, should be kept separate from the certificates you use for the web service itself." These config settings were in place long before I worked here... I was just copying the info from the old server.xml and adding in the new keystore info. If we do not Use any client certs can I remove the truststore line? Thanks, Justin ** This email and any files transmitted with it are intended solely for the use of the individual or agency to whom they are addressed. If you have received this email in error please notify the Navy Exchange Service Command e-mail administrator. This footnote also confirms that this email message has been scanned for the presence of computer viruses. Thank You! **
Re: Tomcat crashes after startup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Justin, On 12/12/11 3:49 PM, Justin Larose wrote: > I edited the connector with the information for the new certificate > I just installed (not the old self signed one) and now I am seeing > this error: > > [snip] > > java.io.IOException: Alias name tomcat does not identify a key > entry You need to have a key in your keystore with the alias "tomcat" as well. If you have been following http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html#Configuration, you have either missed or misinterpreted a step. > disableUploadTimeout="true" enableLookups="false" keyAlias="tomcat" > keystoreFile="conf/wcmdev-ssl.jks" keystorePass="" > maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150" > minSpareThreads="25"port="8443" scheme="https" secure="true" > sslProtocol="TLS" strategy="ms" > truststoreFile="conf/wcmdev-ssl.jks" truststorePass=""/> I would advise against using the same keystore for both the "keystore" and the "truststore". The trust store is only used for validating client certificates and, IMO, should be kept separate from the certificates you use for the web service itself. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7mcdgACgkQ9CaO5/Lv0PBsDACfTjv3vJqiBMdl3v1TInDyRYku gIsAnjVQNgh4eyeH2tSwyfSIeIN4GsDJ =XlwU -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat crashes after startup
Thank you Mark, I edited the connector with the information for the new certificate I just installed (not the old self signed one) and now I am seeing this error: (I have attached the modified server.xml and the output for tomcat key entry cert below) ___ Dec 12, 2011 3:38:24 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-18080 Dec 12, 2011 3:38:24 PM org.apache.coyote.http11.Http11Protocol init SEVERE: Error initializing endpoint java.io.IOException: Alias name tomcat does not identify a key entry at org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:546) at org.apache.tomcat.util.net.jsse.JSSESocketFactory.init(JSSESocketFactory.java:481) at org.apache.tomcat.util.net.jsse.JSSESocketFactory.createSocket(JSSESocketFactory.java:156) at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:538) at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:176) at org.apache.catalina.connector.Connector.initialize(Connector.java:1022) at org.apache.catalina.core.StandardService.initialize(StandardService.java:703) at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:838) at org.apache.catalina.startup.Catalina.load(Catalina.java:538) at org.apache.catalina.startup.Catalina.load(Catalina.java:562) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:261) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Dec 12, 2011 3:38:24 PM org.apache.catalina.core.StandardService initialize SEVERE: Failed to initialize connector [Connector[HTTP/1.1-8443]] LifecycleException: Protocol handler initialization failed: java.io.IOException: Alias name tomcat does not identify a key entry at org.apache.catalina.connector.Connector.initialize(Connector.java:1024) at org.apache.catalina.core.StandardService.initialize(StandardService.java:703) at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:838) at org.apache.catalina.startup.Catalina.load(Catalina.java:538) at org.apache.catalina.startup.Catalina.load(Catalina.java:562) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:261) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) ___ F:\Serena\Dimensions 2009 R2\Common Tools\jre\6.0\bin>keytool -list -v -keystore wcmdev-ssl.jks -alias tomcat Enter keystore password: Alias name: tomcat Creation date: Nov 10, 2011 Entry type: trustedCertEntry Owner: CN=wcmdev.nexweb.us, OU=USN, OU=PKI, OU=DoD, O=U.S. Government, C=US ___ Thanks, Justin From: Mark Thomas To: Tomcat Users List Date: 12/12/2011 03:29 PM Subject: Re: Tomcat crashes after startup On 12/12/2011 20:20, Justin Larose wrote: > Group, > > Can anyone help me with this error below from the catalina.log? > I have attached my server.xml as well. I have done some searches on the > internet and cannot find much on this error. > > SEVERE: Error initializing endpoint > java.io.IOException: AnyCert TrustManagerFactory not available Seems pretty clear to me. > Fix your broken connector configuration or provide a JSSE implementation that includes this custom truststoreAlgorithm. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org ** This email and any files transmitted with it are intended solely for the use of the individual or agency to whom they are addressed. If you have received this email in error please notify the Navy Exchange Service Command e-mail administrator. This footnote also confirms that this email message has been scanned for the presence of computer viruses. Thank You! **
Re: Tomcat crashes after startup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Justin, Mark already answered your question, but ... On 12/12/11 3:20 PM, Justin Larose wrote: > protocol="HTTP/1.1" redirectPort="8443" server="Unknown Web > Server/1.0"/> :( Really? Masking the server name? At least say "Apache Tomcat" or something like that. Security By Obscurity doesn't actually solve any security problems. Note that the default value for the "server string" is "Apache-Coyote/1.1" which doesn't really give an attacker any meaningful information. > disableUploadTimeout="true" enableLookups="false" keyAlias="tomcat" > keystoreFile="conf/sample-ssl.jks" keystorePass="*" > maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150" > minSpareThreads="25" port="8443" scheme="https" secure="true" > sslProtocol="TLS" strategy="ms" > truststoreFile="conf/sample-ssl.jks" truststorePass="*"/> Note: no "server" attribute, here... attackers can still see you are using "Apache-Coyote/1.1". > disableUploadTimeout="true" enableLookups="false" keyAlias="tomcat" > keystoreFile="conf/sample-ssl.jks" keystorePass="*" > maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150" > minSpareThreads="25" port="8543" scheme="https" secure="true" > sslProtocol="TLS" strategy="ms" truststoreAlgorithm="AnyCert" > truststoreFile="conf/sample-ssl.jks" truststorePass="*"/> Same here. > port="8409" protocol="AJP/1.3" redirectPort="8443" server="Unknown > Web Server/1.0"/> I'm not sure if the AJP connector will return a "Server" response header to the web server. Most web servers will overwrite this value so that the client sees the proxy server's "Server" response header. > > resourceName="UserDatabase"/> If you really are concerned about security, then you shouldn't be using UserDatabaseRealm. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7maHkACgkQ9CaO5/Lv0PCv1QCfWTlqSbf79C0YW81G2FAXLbBK T3UAnA3XgEwv9njrL2YyG8WNx7SKCA4x =Jp6s -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat crashes after startup
On 12/12/2011 20:20, Justin Larose wrote: > Group, > > Can anyone help me with this error below from the catalina.log? > I have attached my server.xml as well. I have done some searches on the > internet and cannot find much on this error. > > SEVERE: Error initializing endpoint > java.io.IOException: AnyCert TrustManagerFactory not available Seems pretty clear to me. > Fix your broken connector configuration or provide a JSSE implementation that includes this custom truststoreAlgorithm. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Crashes out of continuous servicing of stuck request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nishant, Mailing the list is fine: there's no need to mail me separately. On 12/6/2009 11:19 PM, Hadole, Nishant IN BOM SISL wrote: > Tomcat crashes means, the free memory starts declining dramatically > to zero, and server stops responding to new requests. Does the JVM and/or Tomcat actually crash? That's an important difference: if Tomcat simply stops responding to requests, that's likely to be a different problem than an actual crash. > I am sure with little modifications, this can be handled in code > itself, and this is not a concern at all. Eh... okay, if you say so. > I am more interested in knowing whether there exists any > configuration for such cases, which stops processing after some > predefined time-out. No. > I know that this can be done for KEEPALIVE requests. What @ requests > in SERVICE stage. I'm not sure what you mean, here. > The screenshot for Tomcat Manager is attached for the same. The screenshot indicates that you have 756MiB free of a 1016MiB heap. That looks good to me. It also indicates that your "jvehelp" servlet seems to be taking forever to do its work. Perhaps you should take a thread dump and figure out what your servlet is doing when it stalls? Only one thread is in the "keepalive wait" state, and it has been there for 6.5 seconds. What is your keepalive timeout? Is it set to an appropriate amount? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksecS8ACgkQ9CaO5/Lv0PCH+gCffSPXVFy7KAdXKCrS3hCOr+GW IvkAn1gSQR6dt5JFIWi2JXMXX3fAPBH7 =2YaM -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat Crashes out of continuous servicing of stuck request
Dear Chris, Tomcat crashes means, the free memory starts declining dramatically to zero, and server stops responding to new requests. I am sure with little modifications, this can be handled in code itself, and this is not a concern at all. I am more interested in knowing whether there exists any configuration for such cases, which stops processing after some predefined time-out. I know that this can be done for KEEPALIVE requests. What @ requests in SERVICE stage. The screenshot for Tomcat Manager is attached for the same. With best regards, Nishant Hadole Siemens IT Solutions and Services SIS PRO SI-I Tel.: +91 22 2495 7816 Fax: +91 22 6660 8521 Mailto: nishant.had...@siemens.com www.siemens.co.in -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Saturday, 05 December, 2009 03:34 AM To: Tomcat Users List Cc: Hadole, Nishant IN BOM SISL Subject: Re: Tomcat Crashes out of continuous servicing of stuck request -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nishant, On 12/4/2009 4:29 AM, Hadole, Nishant IN BOM SISL wrote: > Tomcat continues processing request indefinitely, causing loss of > free heap memory and eventually crashes. When you say "crashes", what exactly to you mean? OOME? JVM failure? > When checked in Tomcat Monitor, under header jk-8009, the stage for > stuck request is SERVICE and time goes on increasing. As others have said, without attempting to send data to the client, you can't know that they have disappeared. :( My question is why your code causes a "crash" when the client disappears, but works just fine when the client gets a proper response. That suggests a mismanagement of resources by your webapp. You might consider reviewing your code to find out why your "loss of free heap memory" is occurring, because Tomcat surely isn't causing that to happen. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksZh0sACgkQ9CaO5/Lv0PBGfwCfVjYr8P9A0iFm6hLKkG7gxKx6 zsoAn2s5Box8os9g0dE6uFgB4TXJWPdr =ssOC -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Crashes out of continuous servicing of stuck request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nishant, On 12/4/2009 4:29 AM, Hadole, Nishant IN BOM SISL wrote: > Tomcat continues processing request indefinitely, causing loss of > free heap memory and eventually crashes. When you say "crashes", what exactly to you mean? OOME? JVM failure? > When checked in Tomcat Monitor, under header jk-8009, the stage for > stuck request is SERVICE and time goes on increasing. As others have said, without attempting to send data to the client, you can't know that they have disappeared. :( My question is why your code causes a "crash" when the client disappears, but works just fine when the client gets a proper response. That suggests a mismanagement of resources by your webapp. You might consider reviewing your code to find out why your "loss of free heap memory" is occurring, because Tomcat surely isn't causing that to happen. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksZh0sACgkQ9CaO5/Lv0PBGfwCfVjYr8P9A0iFm6hLKkG7gxKx6 zsoAn2s5Box8os9g0dE6uFgB4TXJWPdr =ssOC -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Crashes out of continuous servicing of stuck request
On 04.12.2009 11:41, Looijmans, Mike wrote: ... Without trying to send something back to the client, there is no way telling the client closed the window (or pressed reload or switched to another URL). I would expect the socket to be closed, which can be detected at the server side. The exceptions I can think of are the client crashing or a network disconnect. Though apache probably detects the socket's close, it has little means It detects the close only when trying to send something via the socket. There's no monitoring of unused sockets. Although the server received the FIN or RST packets and changes the state of the socket internally, there'*s no application (=Apache) code checking that state when not actually trying to use the socket. You could write such code, but it's not there. The closed socket is detected once the server tries to read from or write to it. of informing the associated servlet because that is blocked waiting for the response from the database. Exactly. Even if the web server knew, you would still have to forward the information to the naxt hop, e.g. Tomcat (and then also the database). The communication between Apache and Tomcat (either via http or via ajp) doesn't have any notification facility of the form "don't proceed working on this request". It can only detect an error on top of request and response communication. So here, once the app actually tries to send something back, Apache will notice the closed socket to the client, and then close the socket to the backend itself (at least in the case of mod_jk) and then Tomcat notices the closed socket to the web server and throws an error itself. Depending on the database, it is usually also no use to try and stop - the query will continue its work even though the requesting user is gone on most DBMSes. So taking a slot in the webserver is not a big issue, the DB is wasting far more resources on that user. Other options to explore are dividing the big query into multiple smaller ones, so that you can abort sooner. Use "INTO TEMP" to store intermediates. That would give you the opportiunity to check whether the client is still listening - and you could even give the client some updates on progress, which may be considered a nice to have feature as well. Best of all would be to optimize the database and make those queries faster, but I guess you must have valid reasons for not doing so. M. -- My reply ends here -- This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation. Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat Crashes out of continuous servicing of stuck request
Just an idea: What happens if you change your DB call into a "Sleep(30)" or something similar? Does tomcat still misbehave then? (the 'retry' could be related to something else than tomcat). M > -Original Message- > From: Hadole, Nishant IN BOM SISL [mailto:nishant.had...@siemens.com] > Sent: vrijdag 04 december 2009 11:06 > To: 'Rainer Jung'; Tomcat Users List > Subject: RE: Tomcat Crashes out of continuous servicing of > stuck request > > Dear Rainer, > > Thanks for explanation. In this particular case, when client > press a button on JSP, it initiates a Database search > operation, which may take time up to 30-45 seconds. > Meanwhile, we are showing a screen which tell user that his / > her request is being processed and no to close the window. > > But, sometimes users are impatient and still close the > window. Yes, as you suggested, it is possible to handle close > event / stop processing by some notification, but application > is full of such utilities, and it is too much of efforts. > > I am interested in some parameterization, which detects > broken connection and automatically drops stuck request. I > have even checked this with requests with STAGE as KEEPALIVE, > but not working with STAGE as SERVICE. Also, I am not able to > figure out, why the processing is repeated. > > With best regards, > Nishant Hadole > Mailto: nishant.had...@siemens.com This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat Crashes out of continuous servicing of stuck request
... > Without trying to send something back to the client, there is > no way telling the client closed the window (or pressed > reload or switched to another URL). I would expect the socket to be closed, which can be detected at the server side. The exceptions I can think of are the client crashing or a network disconnect. Though apache probably detects the socket's close, it has little means of informing the associated servlet because that is blocked waiting for the response from the database. Depending on the database, it is usually also no use to try and stop - the query will continue its work even though the requesting user is gone on most DBMSes. So taking a slot in the webserver is not a big issue, the DB is wasting far more resources on that user. Other options to explore are dividing the big query into multiple smaller ones, so that you can abort sooner. Use "INTO TEMP" to store intermediates. That would give you the opportiunity to check whether the client is still listening - and you could even give the client some updates on progress, which may be considered a nice to have feature as well. Best of all would be to optimize the database and make those queries faster, but I guess you must have valid reasons for not doing so. M. -- My reply ends here -- This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat Crashes out of continuous servicing of stuck request
Dear Rainer, Thanks for explanation. In this particular case, when client press a button on JSP, it initiates a Database search operation, which may take time up to 30-45 seconds. Meanwhile, we are showing a screen which tell user that his / her request is being processed and no to close the window. But, sometimes users are impatient and still close the window. Yes, as you suggested, it is possible to handle close event / stop processing by some notification, but application is full of such utilities, and it is too much of efforts. I am interested in some parameterization, which detects broken connection and automatically drops stuck request. I have even checked this with requests with STAGE as KEEPALIVE, but not working with STAGE as SERVICE. Also, I am not able to figure out, why the processing is repeated. With best regards, Nishant Hadole Mailto: nishant.had...@siemens.com -Original Message- From: Rainer Jung [mailto:rainer.j...@kippdata.de] Sent: Friday, 04 December, 2009 03:14 PM To: Tomcat Users List Cc: Hadole, Nishant IN BOM SISL Subject: Re: Tomcat Crashes out of continuous servicing of stuck request On 04.12.2009 10:29, Hadole, Nishant IN BOM SISL wrote: > I am using Apache HTTP Server 2.0.61, Apache Tomcat Server 6.0.14.0 and > mod_jk 2.0.46 (AJP V 1.3). mod_jk 2.0.46 does not exist. > Scenario - Client call for heavy Post request from JSP. Tomcat receives the > request and starts processing. Before receiving the response, client closes > JSP window. Thus there is no one to receive the output. > > Issue - Tomcat continues processing request indefinitely, causing loss of > free heap memory and eventually crashes. When checked in Tomcat Monitor, > under header jk-8009, the stage for stuck request is SERVICE and time goes on > increasing. > > I have checked several Time-outs setting for tomcat and AJP connectors, but > still of no use. Without trying to send something back to the client, there is no way telling the client closed the window (or pressed reload or switched to another URL). So in order to be able to stop processing long running stuff, you need to try sending something to the client every now and then, and your code working on producing the real response content needs to be stopped by some notification. You will need to implement this yourself. Maybe someone can provide some example code? > Kindly help. Also let me know if any specific parameterization is to ne > mentioned here for this. > > > Note: We cannot avoid client closing window while request processing is in > progress. > > With best regards, > Nishant Hadole > Tel.: +91 22 2495 7816 > Fax: +91 22 6660 8521 > Mailto: nishant.had...@siemens.com Regards, Rainer
Re: Tomcat Crashes out of continuous servicing of stuck request
On 04.12.2009 10:29, Hadole, Nishant IN BOM SISL wrote: I am using Apache HTTP Server 2.0.61, Apache Tomcat Server 6.0.14.0 and mod_jk 2.0.46 (AJP V 1.3). mod_jk 2.0.46 does not exist. Scenario - Client call for heavy Post request from JSP. Tomcat receives the request and starts processing. Before receiving the response, client closes JSP window. Thus there is no one to receive the output. Issue - Tomcat continues processing request indefinitely, causing loss of free heap memory and eventually crashes. When checked in Tomcat Monitor, under header jk-8009, the stage for stuck request is SERVICE and time goes on increasing. I have checked several Time-outs setting for tomcat and AJP connectors, but still of no use. Without trying to send something back to the client, there is no way telling the client closed the window (or pressed reload or switched to another URL). So in order to be able to stop processing long running stuff, you need to try sending something to the client every now and then, and your code working on producing the real response content needs to be stopped by some notification. You will need to implement this yourself. Maybe someone can provide some example code? Kindly help. Also let me know if any specific parameterization is to ne mentioned here for this. Note: We cannot avoid client closing window while request processing is in progress. With best regards, Nishant Hadole Tel.: +91 22 2495 7816 Fax: +91 22 6660 8521 Mailto: nishant.had...@siemens.com Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat crashes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kam, On 6/29/2009 2:39 PM, kam tak wrote: > I am using tomcat 6 and the server crashes all of a sudden creating a core > dump file. Core dump == JVM crash. This is unlikely to be Tomcat's fault. When the JVM dumps core, it should leave-behind a crash file in plain text explaining what happened. Can you post that file? Have you looked at the core file (using gdb or some other tool) to determine the nature of the crash? I'll bet it's a SIGSEGV (segmentation violation, signal #11) and that you have bad memory, motherboard, or memory. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkpJIWQACgkQ9CaO5/Lv0PDWKACfaur/jZMs6biRw1vDSyXP2a/5 yCsAnR0rNehUz0HsAo0TLz1GonZnP17T =6riU -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat crashes
kam tak wrote: Hi, I am using tomcat 6 and the server crashes all of a sudden creating a core dump file. I have no clue why this is happening. Can you please suggest on what all details I need to provide so that some one can help resolve the issue. On which platform ? Which precise version of Tomcat ? Where did you get this Tomcat from ? Can you elaborate on "all of a sudden" ? Is it like 1 minute after it starts, or after a year of working fine ? Do you know where this Tomcat's logfiles are ? If yes, did you consult them to see if maybe there is an interesting message in them, right about when Tomcat crashes ? (shortly before, usually). - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat crashes
filip, JVm has the default options that is shipped out with tomcat distribution. the crash happens in the initial testing even before we apply our custom production changes. thanks bharat Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: looks like it is a VM thread that is crashing, not a tomcat thread.what are your command line options to the JVM? could be a GC bug, Filip daniel steel wrote: > all, > i am not sure if this a bug or OS problem or our install problem (this is > the first ever crash). at one of our new installs at a customer site, the > moment tomcat is started, it crashes with JVM exception. this has happened > with tomcat5 + jdk 1.4. and with tomcat6 and jdk 1.5. Tomcat ( > 6.0.10/6.0.13) doesn't crash if running in console mode but crashes if > running as service. > > thanks > dan > > [jvm log] > # > # An unexpected error has been detected by HotSpot Virtual Machine: > # > # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x6d7a439b, pid=2536, > tid=2316 > # > # Java VM: Java HotSpot(TM) Client VM (1.5.0_11-b03 mixed mode) > # Problematic frame: > # V [jvm.dll+0x6439b] > # > > --- T H R E A D --- > > Current thread (0x00a86208): VMThread [id=2316] > > siginfo: ExceptionCode=0xc005, reading address 0x0400 > > Registers: > EAX=0x0400, EBX=0x04571204, ECX=0x009afc70, EDX=0x045711fc > ESP=0x009afa40, EBP=0x009afa6c, ESI=0x045711fc, EDI=0x009afc70 > EIP=0x6d7a439b, EFLAGS=0x00010287 > > Top of Stack: (sp=0x009afa40) > 0x009afa40: 045711fc 077552c0 6d7ba46b 045711fc > 0x009afa50: 6d7ba43a 045711fc 04571208 045711c8 > 0x009afa60: 0455ee00 07754f08 077552c4 009afa88 > 0x009afa70: 6d83a8c4 045711c8 009afaac 6d8787b4 > 0x009afa80: 00a863e8 6d8787b4 009afabc 6d83a7c9 > 0x009afa90: 0455ee00 00018b02 0455ee00 045c1a08 > 0x009afaa0: 009afaac 0455ee00 00a863e8 6d8787a0 > 0x009afab0: 00a85900 02fb 009afc70 009afae8 > > Instructions: (pc=0x6d7a439b) > 0x6d7a438b: 24 08 57 8b f9 8b 06 85 c0 74 2f 3b 47 1c 73 2a > 0x6d7a439b: 8b 08 83 e1 03 80 f9 03 75 06 8b 00 24 fc eb 0a > > > Stack: [0x0097,0x009b), sp=0x009afa40, free space=254k > Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native > code) > V [jvm.dll+0x6439b] > V [jvm.dll+0xfa8c4] > V [jvm.dll+0xfa7c9] > V [jvm.dll+0xfa6c7] > V [jvm.dll+0x4110d] > V [jvm.dll+0x405ee] > V [jvm.dll+0x404bc] > V [jvm.dll+0x41066] > V [jvm.dll+0x73f3b] > V [jvm.dll+0x64d13] > V [jvm.dll+0x6f8ba] > V [jvm.dll+0x51d3e] > V [jvm.dll+0x6fa5c] > V [jvm.dll+0x12a230] > V [jvm.dll+0x129cfe] > V [jvm.dll+0x129ea7] > V [jvm.dll+0x129c0c] > C [MSVCRT.dll+0x2b530] > C [kernel32.dll+0x24829] > > VM_Operation (0x0b35f5c8): generation collection for allocation, mode: > safepoint, requested by thread 0x0b05b158 > > > --- P R O C E S S --- > > Java Threads: ( => current thread ) > 0x0b3d1310 JavaThread "Keep-Alive-Timer" daemon [_thread_blocked, id=2188] > 0x0b0b8288 JavaThread "TP-Monitor" daemon [_thread_blocked, id=3884] > 0x0b3aa808 JavaThread "TP-Processor4" daemon [_thread_in_native, id=2224] > 0x0b3ce178 JavaThread "TP-Processor3" daemon [_thread_blocked, id=1156] > 0x0b0c1b58 JavaThread "TP-Processor2" daemon [_thread_blocked, id=2148] > 0x0b0c1938 JavaThread "TP-Processor1" daemon [_thread_blocked, id=3848] > 0x0b3a3510 JavaThread "http-8080-Monitor" [_thread_blocked, id=2260] > 0x0b3a2710 JavaThread "http-8080-Processor25" daemon [_thread_in_native, > id=2384] > 0x0b3a1a50 JavaThread "http-8080-Processor24" daemon [_thread_blocked, > id=1008] > 0x0b46db58 JavaThread "http-8080-Processor23" daemon [_thread_blocked, > id=2988] > 0x0b46ce98 JavaThread "http-8080-Processor22" daemon [_thread_blocked, > id=2672] > 0x0b46c1d8 JavaThread "http-8080-Processor21" daemon [_thread_blocked, > id=3304] > 0x0b46b518 JavaThread "http-8080-Processor20" daemon [_thread_blocked, > id=4036] > 0x0b46a858 JavaThread "http-8080-Processor19" daemon [_thread_blocked, > id=336] > 0x0b469b98 JavaThread "http-8080-Processor18" daemon [_thread_blocked, > id=4000] > 0x0b468ed8 JavaThread "http-8080-Processor17" daemon [_thread_blocked, > id=3076] > 0x0b468218 JavaThread "http-8080-Processor16" daemon [_thread_blocked, > id=1024] > 0x0b467558 JavaThread "http-8080-Processor15" daemon [_thread_blocked, > id=3804] > 0x0b24e5d8 JavaThread "http-8080-Processor14" daemon [_thread_blocked, > id=3768] > 0x0b24d930 JavaThread "http-8080-Processor13" daemon [_thread_blocked, > id=2228] > 0x0b24ccd8 JavaThread "http-8080-Processor12" daemon [_thread_blocked, > id=1652] > 0x0b24c0e0 JavaThread "http-8080-Processor11" daemon [_thread_blocked, > id=3868] > 0x0b24b4e8 JavaThread "http-8080-Pro
Re: tomcat crashes
looks like it is a VM thread that is crashing, not a tomcat thread.what are your command line options to the JVM? could be a GC bug, Filip daniel steel wrote: all, i am not sure if this a bug or OS problem or our install problem (this is the first ever crash). at one of our new installs at a customer site, the moment tomcat is started, it crashes with JVM exception. this has happened with tomcat5 + jdk 1.4. and with tomcat6 and jdk 1.5. Tomcat ( 6.0.10/6.0.13) doesn't crash if running in console mode but crashes if running as service. thanks dan [jvm log] # # An unexpected error has been detected by HotSpot Virtual Machine: # # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x6d7a439b, pid=2536, tid=2316 # # Java VM: Java HotSpot(TM) Client VM (1.5.0_11-b03 mixed mode) # Problematic frame: # V [jvm.dll+0x6439b] # --- T H R E A D --- Current thread (0x00a86208): VMThread [id=2316] siginfo: ExceptionCode=0xc005, reading address 0x0400 Registers: EAX=0x0400, EBX=0x04571204, ECX=0x009afc70, EDX=0x045711fc ESP=0x009afa40, EBP=0x009afa6c, ESI=0x045711fc, EDI=0x009afc70 EIP=0x6d7a439b, EFLAGS=0x00010287 Top of Stack: (sp=0x009afa40) 0x009afa40: 045711fc 077552c0 6d7ba46b 045711fc 0x009afa50: 6d7ba43a 045711fc 04571208 045711c8 0x009afa60: 0455ee00 07754f08 077552c4 009afa88 0x009afa70: 6d83a8c4 045711c8 009afaac 6d8787b4 0x009afa80: 00a863e8 6d8787b4 009afabc 6d83a7c9 0x009afa90: 0455ee00 00018b02 0455ee00 045c1a08 0x009afaa0: 009afaac 0455ee00 00a863e8 6d8787a0 0x009afab0: 00a85900 02fb 009afc70 009afae8 Instructions: (pc=0x6d7a439b) 0x6d7a438b: 24 08 57 8b f9 8b 06 85 c0 74 2f 3b 47 1c 73 2a 0x6d7a439b: 8b 08 83 e1 03 80 f9 03 75 06 8b 00 24 fc eb 0a Stack: [0x0097,0x009b), sp=0x009afa40, free space=254k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) V [jvm.dll+0x6439b] V [jvm.dll+0xfa8c4] V [jvm.dll+0xfa7c9] V [jvm.dll+0xfa6c7] V [jvm.dll+0x4110d] V [jvm.dll+0x405ee] V [jvm.dll+0x404bc] V [jvm.dll+0x41066] V [jvm.dll+0x73f3b] V [jvm.dll+0x64d13] V [jvm.dll+0x6f8ba] V [jvm.dll+0x51d3e] V [jvm.dll+0x6fa5c] V [jvm.dll+0x12a230] V [jvm.dll+0x129cfe] V [jvm.dll+0x129ea7] V [jvm.dll+0x129c0c] C [MSVCRT.dll+0x2b530] C [kernel32.dll+0x24829] VM_Operation (0x0b35f5c8): generation collection for allocation, mode: safepoint, requested by thread 0x0b05b158 --- P R O C E S S --- Java Threads: ( => current thread ) 0x0b3d1310 JavaThread "Keep-Alive-Timer" daemon [_thread_blocked, id=2188] 0x0b0b8288 JavaThread "TP-Monitor" daemon [_thread_blocked, id=3884] 0x0b3aa808 JavaThread "TP-Processor4" daemon [_thread_in_native, id=2224] 0x0b3ce178 JavaThread "TP-Processor3" daemon [_thread_blocked, id=1156] 0x0b0c1b58 JavaThread "TP-Processor2" daemon [_thread_blocked, id=2148] 0x0b0c1938 JavaThread "TP-Processor1" daemon [_thread_blocked, id=3848] 0x0b3a3510 JavaThread "http-8080-Monitor" [_thread_blocked, id=2260] 0x0b3a2710 JavaThread "http-8080-Processor25" daemon [_thread_in_native, id=2384] 0x0b3a1a50 JavaThread "http-8080-Processor24" daemon [_thread_blocked, id=1008] 0x0b46db58 JavaThread "http-8080-Processor23" daemon [_thread_blocked, id=2988] 0x0b46ce98 JavaThread "http-8080-Processor22" daemon [_thread_blocked, id=2672] 0x0b46c1d8 JavaThread "http-8080-Processor21" daemon [_thread_blocked, id=3304] 0x0b46b518 JavaThread "http-8080-Processor20" daemon [_thread_blocked, id=4036] 0x0b46a858 JavaThread "http-8080-Processor19" daemon [_thread_blocked, id=336] 0x0b469b98 JavaThread "http-8080-Processor18" daemon [_thread_blocked, id=4000] 0x0b468ed8 JavaThread "http-8080-Processor17" daemon [_thread_blocked, id=3076] 0x0b468218 JavaThread "http-8080-Processor16" daemon [_thread_blocked, id=1024] 0x0b467558 JavaThread "http-8080-Processor15" daemon [_thread_blocked, id=3804] 0x0b24e5d8 JavaThread "http-8080-Processor14" daemon [_thread_blocked, id=3768] 0x0b24d930 JavaThread "http-8080-Processor13" daemon [_thread_blocked, id=2228] 0x0b24ccd8 JavaThread "http-8080-Processor12" daemon [_thread_blocked, id=1652] 0x0b24c0e0 JavaThread "http-8080-Processor11" daemon [_thread_blocked, id=3868] 0x0b24b4e8 JavaThread "http-8080-Processor10" daemon [_thread_blocked, id=2996] 0x0b24a8f0 JavaThread "http-8080-Processor9" daemon [_thread_blocked, id=2944] 0x0b249cf8 JavaThread "http-8080-Processor8" daemon [_thread_blocked, id=2952] 0x0b249140 JavaThread "http-8080-Processor7" daemon [_thread_blocked, id=4056] 0x0b3bf538 JavaThread "http-8080-Processor6" daemon [_thread_blocked, id=4060] 0x0b3be9d8 JavaThread "http-8080-Processor5" daemon [_thread_blocked, id=2464] 0x0b065c1
Re: Tomcat Crashes after 1000 sessions.
Hi, I am trying to configure jmx remote to enable monitoring of the application through Jconsole.As per the documentation i have put the following parameter CATALINA_OPTS="-Dcom.sun.management.jmxremote.port=3050" export CATALINA_OPTS in the catalina.sh file I have also configured the management.properties file which gives the path to a password file.But the service dosen't seem to start on defined port.Please help Thanks & Regards, VIkram On 3/8/06, Tomasz Nowak <[EMAIL PROTECTED]> wrote: > Vikram Godse <[EMAIL PROTECTED]> wrote: > > > > Hi, > > My CATALINA_OPTS parameter has the following values i have 4gb ram on > > my server > > > > > CATALINA_OPTS="-server -XX:MaxPermSize=512m -Xms1024m -Xmx1024m" > > > > This is what i see in the tomcat manager server info. > > > Max threads: 200 Min spare threads: 4 Max spare threads: 50 Current > > thread count: 20 >Current thread busy: 17 > > > Max processing time: 560464 ms Processing time: 2668.859 s Request > > count: 2800 Error >count: 46 Bytes received: 0.00 MB Bytes sent: 27.28 > > MB > > > > My Max threads are 200 of which current thread count is 20 and current > > busy are 17 with > > 128 active sessions. > > The same problem here. > > Tomcat 5.5.15, Java 1.5.0, > CATALINA_OPTS: -XX:MaxPermSize=512m -Xms1024m -Xmx1024m" > > Info from one of the managers webapps: > > Max threads: 200 > Min spare threads: 25 > Max spare threads: 50 > Current thread count: 57 > Current thread busy: 16 > > Sessions: 192 > > -- > T. > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Try not do or do not, there is no try ! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Crashes after 1000 sessions.
Vikram Godse <[EMAIL PROTECTED]> wrote: > > Hi, > My CATALINA_OPTS parameter has the following values i have 4gb ram on > my server > > > CATALINA_OPTS="-server -XX:MaxPermSize=512m -Xms1024m -Xmx1024m" > > This is what i see in the tomcat manager server info. > > Max threads: 200 Min spare threads: 4 Max spare threads: 50 Current > thread count: 20 >Current thread busy: 17 > > Max processing time: 560464 ms Processing time: 2668.859 s Request > count: 2800 Error >count: 46 Bytes received: 0.00 MB Bytes sent: 27.28 > MB > > My Max threads are 200 of which current thread count is 20 and current > busy are 17 with > 128 active sessions. The same problem here. Tomcat 5.5.15, Java 1.5.0, CATALINA_OPTS: -XX:MaxPermSize=512m -Xms1024m -Xmx1024m" Info from one of the managers webapps: Max threads: 200 Min spare threads: 25 Max spare threads: 50 Current thread count: 57 Current thread busy: 16 Sessions: 192 -- T. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Crashes after 1000 sessions.
you can configure maxActiveSession, http://tomcat.apache.org/tomcat-5.0-doc/config/manager.html Vikram Godse wrote: Hi, My CATALINA_OPTS parameter has the following values i have 4gb ram on my server CATALINA_OPTS="-server -XX:MaxPermSize=512m -Xms1024m -Xmx1024m" This is what i see in the tomcat manager server info. Max threads: 200 Min spare threads: 4 Max spare threads: 50 Current thread count: 20 >Current thread busy: 17 Max processing time: 560464 ms Processing time: 2668.859 s Request count: 2800 Error >count: 46 Bytes received: 0.00 MB Bytes sent: 27.28 MB My Max threads are 200 of which current thread count is 20 and current busy are 17 with 128 active sessions. and my JVM shows the following Free memory: 976.13 MB Total memory: 1003.93 MB Max memory: 1003.93 MB What i am worried about is the number of sessions keep on increasing my session timeout value is 30minutes.If i keep it less then the user session times out and the user is logged out of the system.If i run it in a test environment with about 5-10 people connecting then the number of sessions never go beyond 10. Is it so that tomcat is getting less resources due to which it is crashing or is it a configuration problem? Thanks & Regards, VIkram On 3/7/06, Sheets, Jerald <[EMAIL PROTECTED]> wrote: I would look at a few things. First, you should read about and implement the JMX instrumentation (jconsle) to get a clear idea of your garbage collection profile. Second, your JVM server options (Xmx, Xms, etc.) need to be set high enough to handle that number of connections. Make sure you have enough PermGen size (-XX:PermSize=128m, for instance) A lot of times people will throw so much ram at -Xms and -Xmx that they have depleted their PermGen space, and will get odd, nondescript errors that surround the all important "native memory" errors. Make sure you aren't garbage collecting to the tenured space quickly and efficiently, but keeping objeects there forever like luggage. In my experience (top 10 website with millions of views daily), we see that pushing the objects into tenured as quickly as possible is the best scenario, YMMV. Make sure you're garbage collecting effectively. -XX:+UseparNewGC, or maybe even an aggressive setting for GC. This will depend entirely on your own metrics you obtain through the jconsole. Each site is different, and just randomly throwing in numbers that some guy on the internet tells you is not the best idea, REGARDLESS of where he works, what his profile is, or how he does it. You have to tailor the container, you have to tailor the VM, and you have to start looking at the code once those are tuned properly. Jerald Sheets Systems Administrator The Weather Channel Interactive -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vikram Godse Sent: Tuesday, March 07, 2006 8:22 AM To: Tomcat Users List Subject: Tomcat Crashes after 1000 sessions. Hi, I am running Apache Tomcat/5.5.12 with JVM 1.5.0-b64.My O/S is RHEL4.0 ES.My hardware configuration is as follows Intel Xeon 3.0Ghz Dual CPU RAM 4gb I am running an JSP and Servlets based application with connectivity to MySQL 5 for database access. I am facing a problem, when my user sessions(in tomcat) go beyond 1000 the tomcat server stop serving requests and just displays a blank page.What i have observed that, though there are only 150 users actually accessing the website the number of sessions are atleast 800-900. Can anybody tell me where the problem lies? i have been trying a lot but no solution yet. Thanks & Regards, VIkram -- Try not do or do not, there is no try ! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Try not do or do not, there is no try ! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Crashes after 1000 sessions.
Again, I would configure jconsole for remote viewing. I'd keep an eye on a specific server, and watch his activity. My guess is you're going to see a condition graphically which will clearly point out to you what is going on, but you won't know until jconsole is configured and running. --JMS -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vikram Godse Sent: Tuesday, March 07, 2006 1:03 PM To: Tomcat Users List Subject: Re: Tomcat Crashes after 1000 sessions. Hi, My CATALINA_OPTS parameter has the following values i have 4gb ram on my server >CATALINA_OPTS="-server -XX:MaxPermSize=512m -Xms1024m -Xmx1024m" This is what i see in the tomcat manager server info. >Max threads: 200 Min spare threads: 4 Max spare threads: 50 Current thread count: 20 >Current thread busy: 17 >Max processing time: 560464 ms Processing time: 2668.859 s Request count: 2800 Error >count: 46 Bytes received: 0.00 MB Bytes sent: 27.28 MB My Max threads are 200 of which current thread count is 20 and current busy are 17 with 128 active sessions. and my JVM shows the following >Free memory: 976.13 MB Total memory: 1003.93 MB Max memory: 1003.93 MB What i am worried about is the number of sessions keep on increasing my session timeout value is 30minutes.If i keep it less then the user session times out and the user is logged out of the system.If i run it in a test environment with about 5-10 people connecting then the number of sessions never go beyond 10. Is it so that tomcat is getting less resources due to which it is crashing or is it a configuration problem? Thanks & Regards, VIkram On 3/7/06, Sheets, Jerald <[EMAIL PROTECTED]> wrote: > I would look at a few things. > > First, you should read about and implement the JMX instrumentation > (jconsle) to get a clear idea of your garbage collection profile. > Second, your JVM server options (Xmx, Xms, etc.) need to be set high > enough to handle that number of connections. > > Make sure you have enough PermGen size (-XX:PermSize=128m, for > instance) A lot of times people will throw so much ram at -Xms and > -Xmx that they have depleted their PermGen space, and will get odd, > nondescript errors that surround the all important "native memory" errors. > > Make sure you aren't garbage collecting to the tenured space quickly > and efficiently, but keeping objeects there forever like luggage. In > my experience (top 10 website with millions of views daily), we see > that pushing the objects into tenured as quickly as possible is the > best scenario, YMMV. > > Make sure you're garbage collecting effectively. -XX:+UseparNewGC, or > maybe even an aggressive setting for GC. This will depend entirely on > your own metrics you obtain through the jconsole. Each site is > different, and just randomly throwing in numbers that some guy on the > internet tells you is not the best idea, REGARDLESS of where he works, > what his profile is, or how he does it. You have to tailor the > container, you have to tailor the VM, and you have to start looking at > the code once those are tuned properly. > > Jerald Sheets > Systems Administrator > The Weather Channel Interactive > > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vikram > Godse > Sent: Tuesday, March 07, 2006 8:22 AM > To: Tomcat Users List > Subject: Tomcat Crashes after 1000 sessions. > > Hi, > I am running Apache Tomcat/5.5.12 with JVM 1.5.0-b64.My O/S is RHEL4.0 > ES.My hardware configuration is as follows Intel Xeon 3.0Ghz Dual CPU > RAM 4gb I am running an JSP and Servlets based application with > connectivity to MySQL 5 for database access. > I am facing a problem, when my user sessions(in tomcat) go beyond 1000 > the tomcat server stop serving requests and just displays a blank > page.What i have observed that, though there are only 150 users > actually accessing the website the number of sessions are atleast 800-900. > Can anybody tell me where the problem lies? i have been trying a lot > but no solution yet. > Thanks & Regards, > VIkram > > > -- > Try not do or do not, there is no try ! > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Try not do or do not, there is no try ! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Crashes after 1000 sessions.
Hi, My CATALINA_OPTS parameter has the following values i have 4gb ram on my server >CATALINA_OPTS="-server -XX:MaxPermSize=512m -Xms1024m -Xmx1024m" This is what i see in the tomcat manager server info. >Max threads: 200 Min spare threads: 4 Max spare threads: 50 Current thread count: 20 >Current thread busy: 17 >Max processing time: 560464 ms Processing time: 2668.859 s Request count: 2800 Error >count: 46 Bytes received: 0.00 MB Bytes sent: 27.28 MB My Max threads are 200 of which current thread count is 20 and current busy are 17 with 128 active sessions. and my JVM shows the following >Free memory: 976.13 MB Total memory: 1003.93 MB Max memory: 1003.93 MB What i am worried about is the number of sessions keep on increasing my session timeout value is 30minutes.If i keep it less then the user session times out and the user is logged out of the system.If i run it in a test environment with about 5-10 people connecting then the number of sessions never go beyond 10. Is it so that tomcat is getting less resources due to which it is crashing or is it a configuration problem? Thanks & Regards, VIkram On 3/7/06, Sheets, Jerald <[EMAIL PROTECTED]> wrote: > I would look at a few things. > > First, you should read about and implement the JMX instrumentation > (jconsle) to get a clear idea of your garbage collection profile. > Second, your JVM server options (Xmx, Xms, etc.) need to be set high > enough to handle that number of connections. > > Make sure you have enough PermGen size (-XX:PermSize=128m, for instance) > A lot of times people will throw so much ram at -Xms and -Xmx that they > have depleted their PermGen space, and will get odd, nondescript errors > that surround the all important "native memory" errors. > > Make sure you aren't garbage collecting to the tenured space quickly and > efficiently, but keeping objeects there forever like luggage. In my > experience (top 10 website with millions of views daily), we see that > pushing the objects into tenured as quickly as possible is the best > scenario, YMMV. > > Make sure you're garbage collecting effectively. -XX:+UseparNewGC, or > maybe even an aggressive setting for GC. This will depend entirely on > your own metrics you obtain through the jconsole. Each site is > different, and just randomly throwing in numbers that some guy on the > internet tells you is not the best idea, REGARDLESS of where he works, > what his profile is, or how he does it. You have to tailor the > container, you have to tailor the VM, and you have to start looking at > the code once those are tuned properly. > > Jerald Sheets > Systems Administrator > The Weather Channel Interactive > > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vikram > Godse > Sent: Tuesday, March 07, 2006 8:22 AM > To: Tomcat Users List > Subject: Tomcat Crashes after 1000 sessions. > > Hi, > I am running Apache Tomcat/5.5.12 with JVM 1.5.0-b64.My O/S is RHEL4.0 > ES.My hardware configuration is as follows Intel Xeon 3.0Ghz Dual CPU > RAM 4gb I am running an JSP and Servlets based application with > connectivity to MySQL 5 for database access. > I am facing a problem, when my user sessions(in tomcat) go beyond 1000 > the tomcat server stop serving requests and just displays a blank > page.What i have observed that, though there are only 150 users actually > accessing the website the number of sessions are atleast 800-900. > Can anybody tell me where the problem lies? i have been trying a lot but > no solution yet. > Thanks & Regards, > VIkram > > > -- > Try not do or do not, there is no try ! > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Try not do or do not, there is no try ! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Crashes after 1000 sessions.
I would look at a few things. First, you should read about and implement the JMX instrumentation (jconsle) to get a clear idea of your garbage collection profile. Second, your JVM server options (Xmx, Xms, etc.) need to be set high enough to handle that number of connections. Make sure you have enough PermGen size (-XX:PermSize=128m, for instance) A lot of times people will throw so much ram at -Xms and -Xmx that they have depleted their PermGen space, and will get odd, nondescript errors that surround the all important "native memory" errors. Make sure you aren't garbage collecting to the tenured space quickly and efficiently, but keeping objeects there forever like luggage. In my experience (top 10 website with millions of views daily), we see that pushing the objects into tenured as quickly as possible is the best scenario, YMMV. Make sure you're garbage collecting effectively. -XX:+UseparNewGC, or maybe even an aggressive setting for GC. This will depend entirely on your own metrics you obtain through the jconsole. Each site is different, and just randomly throwing in numbers that some guy on the internet tells you is not the best idea, REGARDLESS of where he works, what his profile is, or how he does it. You have to tailor the container, you have to tailor the VM, and you have to start looking at the code once those are tuned properly. Jerald Sheets Systems Administrator The Weather Channel Interactive -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vikram Godse Sent: Tuesday, March 07, 2006 8:22 AM To: Tomcat Users List Subject: Tomcat Crashes after 1000 sessions. Hi, I am running Apache Tomcat/5.5.12 with JVM 1.5.0-b64.My O/S is RHEL4.0 ES.My hardware configuration is as follows Intel Xeon 3.0Ghz Dual CPU RAM 4gb I am running an JSP and Servlets based application with connectivity to MySQL 5 for database access. I am facing a problem, when my user sessions(in tomcat) go beyond 1000 the tomcat server stop serving requests and just displays a blank page.What i have observed that, though there are only 150 users actually accessing the website the number of sessions are atleast 800-900. Can anybody tell me where the problem lies? i have been trying a lot but no solution yet. Thanks & Regards, VIkram -- Try not do or do not, there is no try ! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat Crashes after 1000 sessions.
Vikram Godse wrote: I am facing a problem, when my user sessions(in tomcat) go beyond 1000 the tomcat server stop serving requests and just displays a blank page.What i have observed that, though there are only 150 users actually accessing the website the number of sessions are atleast 800-900. You should check connection timeout and max threads attributes in server.xml. -- Mikolaj Rydzewski <[EMAIL PROTECTED]> Becomo S.A. tel. (12) 2927104 smime.p7s Description: S/MIME Cryptographic Signature
Re: Tomcat Crashes after 1000 sessions.
Have you checked settings like "maxThreads" in your server.xml file? If you have something like 1000 here... you know ;) Cheers, Danny Vikram Godse wrote: actually accessing the website the number of sessions are atleast 800-900. Can anybody tell me where the problem lies? i have been trying a lot but no solution yet. Thanks & Regards, VIkram -- Try not do or do not, there is no try ! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Crashes after 1000 sessions.
Isn't this related to the max thread count setting in server.xml? I would also look into tuning your session expiration value. Perhaps having a logout button or javascript that will invalidate the session when they leave your page... Hope this helps. -Dennis -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vikram Godse Sent: Tuesday, March 07, 2006 8:22 AM To: Tomcat Users List Subject: Tomcat Crashes after 1000 sessions. Hi, I am running Apache Tomcat/5.5.12 with JVM 1.5.0-b64.My O/S is RHEL4.0 ES.My hardware configuration is as follows Intel Xeon 3.0Ghz Dual CPU RAM 4gb I am running an JSP and Servlets based application with connectivity to MySQL 5 for database access. I am facing a problem, when my user sessions(in tomcat) go beyond 1000 the tomcat server stop serving requests and just displays a blank page.What i have observed that, though there are only 150 users actually accessing the website the number of sessions are atleast 800-900. Can anybody tell me where the problem lies? i have been trying a lot but no solution yet. Thanks & Regards, VIkram -- Try not do or do not, there is no try ! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
