You should first check if your OS is updated properly.
Are you running on (Redhat) linux by any chance?
If you do then you have to be carefull that your linux kernel, libc and JVM
version are compatible (pre or post redhat 9)
This is because the new thread library, Native POSIX Thread Library (NP
hmm, very interesting. What other processes are running outside the VM?
do you have process monitors, intrusion detection or other memory/IO intensive
processes running on the same box?
you can rule out native drivers as a possible cause.
the VM still could be causing it.
tomcat is most lik
Peter Lin wrote:
as someone else mentioned, these types of seg fault errors have been the
result of database drivers in the past. Specifically, using native
drivers.
I am not using any native drivers.
I am aware of this type of behavior occuring with other drivers like JMS
that wrap native cod
as someone else mentioned, these types of seg fault errors have been the result of
database drivers in the past. Specifically, using native drivers.
I am aware of this type of behavior occuring with other drivers like JMS that wrap
native code. Make sure your database driver isn't the cause.
Clere, Jean-Frederic wrote:
Jeff Rogers wrote:
Hello,
I hate to post this to the dev list, but we need consulting help. I
have no idea where to look for reputable Tomcat consulting.
We are at our wits end and ready to make the jump to commercial
software due to a "signal 11" crashing problem
Jeff Rogers wrote:
Hello,
I hate to post this to the dev list, but we need consulting help. I
have no idea where to look for reputable Tomcat consulting.
We are at our wits end and ready to make the jump to commercial software
due to a "signal 11" crashing problem with our Tomcat servers.
"sig
