-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Satish,
On 1/26/17 2:28 PM, Satish Chhatpar 02 wrote: > we are using Apache Tomcat/7.0.39 for our java application. I highly recommend an upgrade for both Tomcat and Java. There are published vulnerabilities for both product versions you are using. > There are 4 tomcat instances using same tomcat version and java > version. yesterday all 4 tomcats crashed with below error in > hs_err_pid log file. All on the same hardware? Or separate machines? > This log file was created for all 4 tomcats. > > Its very peculiar behaviour that all 4 crashed around same time. If they are in a cluster, one going down could cause the load on the others to go up, increasing the chances of a problem. > Any information can help us to mitigate this incident. > > Apache Tomcat/7.0.39 Unless this is a package-managed version of Tomcat with an unfortunately inaccurate version number, that version of Tomcat is nearly 3 years old. The current version in the 7.0.x line is 7.0.75 (released yesterday). > java version "1.7.0_21" Java(TM) SE Runtime Environment (build > 1.7.0_21-b11) Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, > mixed mode) That version of Java is also nearly 3 years old. Latest 1.7 build is 1.7.0_80 release nearly 3 years ago. Note that Java 7 is no longer supported unless you have a long-term support contract with Oracle, in which case the latest version is 1.7.0_131, released earlier this month. > OS used > > > Red Hat Enterprise Linux Server release 6.3 (Santiago) Ouch! 5 years old! > # # A fatal error has been detected by the Java Runtime > Environment: # # SIGSEGV (0xb) at pc=0x00007fed24ecfe9e, > pid=21352, tid=140656275650304 # # 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 # This is either a JVM bug is a hardware error. Given that the OS if 5 years old, I'm guessing the hardware is at least that old. I'd expect 5-year old hardware to be fairly trustworthy, but it may not have been properly-tested before going into production. If it's all on a single piece of hardware (all 4 Tomcats), I'd blame the hardware and look for a speedy replacement (properly-tested this time). If it was on different machines, I'd suspect a JVM bug. - -chris -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJYilqXAAoJEBzwKT+lPKRYk8gQAJxyGn+KWUb6V0fzWdiF0gzi xh5p9tjmszS7ixEkMNZmkJH5cwWL8SjrXy0bO3s/50bfzEAOIKnqii+AEBWvKSsw W/zmh/OFJzONOPhSWFvzkI1q9pND+gwRqyIVIkHYMs/l0Vi8GeqoWwJHjaIfSRtG ZW9mDg1cH6p8/QrEynTU/B9XzNxKwIxg7YdUu97/uYPXVICDoRyF6Z8y+ISPMSpF 6OT36NDpdQXTL3xWnYM9149HE37dXjAiz1T+ms0FvP4UKLWN8hy58OdUnjW9EQpj 5IpsruGyRKsAKZzUfwWS68t4d2pq8/QUSvi+t23ZVnOkvdUy99thJ+rIUigb2942 NN6mMzpexOxkq36S7DyJrfXUVWdseeoYgEBFz+9mso2TaTf+9RD4JgLIPXjJ2LZp CvUuHZ1G45uP62qgEsek4LQdPQ8urOzPuDvW578JleRXxE0w80eNPlnFfjb5mFmz TrjGMWZE9ErnfFu6WB0ef5aNpGC5vh3TMXvT5NCVZvqRz/cBP4cXape0CZZdxxkf /lfXqOWb0fBGrzS6BoeI44nyL+Nyqei9UZDl8RZaWjah1aGE9bGYSuvvhWXhgorb Fs/4yvllgIpjRx9gDVcreE0oUFtPYh+FWLSEBYETjEFZCIZVsAGUNNDKa4kDDtXK pxsK5m9udi1kAN+sqBzC =lACD -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
