-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chuck,
Caldarale, Charles R wrote: |> From: Pop Olimpiu [mailto:[EMAIL PROTECTED] |> Subject: hs_err_pidPID.log reading |> |> After following the error logs I found an hs_err_pidPID.log |> which seams to show me what is the problem.... | | This is a JVM, not Tomcat, problem. I would try moving to the latest | version of 1.6 and see if the problem persists. If it does, file a bug | report with Sun, as described in the message you're seeing. My experience with Sun has been that they casually look at SIGSEGV reports, but basically nothing ever gets fixed. The reason is that seg faults, though sometimes caused by bad code in the VM, are usually due to other outrageous reasons like stray alpha particles and bad hardware. As stupid as this sounds, it's often the truth. Every time I've heard of a SIG11 happening on a Java app, a hardware replacement has fixed it 100% of the time. For the OP: http://www.bitwizard.nl/sig11/ - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgOD3AACgkQ9CaO5/Lv0PC8CACeJyZ6xDjzUzUFaJWcUsa52pRx 1l4An3wY/B755cToHX3VkAspsNrEHpmd =nQm4 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
