Hi Tim,
check at your tomcat home if exists a file with the pattern hs_err_pid*.log
maybe your JVM was killed, and in that log you will know the reason.
regards
Clóvis
On Tue, Jul 8, 2008 at 6:26 PM, Tim Hunt <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a Linux (Centos 4) system running Tomcat
P/1.1 default connector). I was not able to reproduce the problem
> after hours of test (it usually happens after 10-20 minutes of heavy load).
> Pushed the configuration change to one of our 4 productions servers to
> monitor the efficiency.
>
> So far we didn't have any problem
Hi, Christophe,
in the follow link you will encounter the IBM Thread and Monitor Dump
Analyzer for Java:
http://www.alphaworks.ibm.com/tech/jca
its a great tool to analyse a sequence of jstack snapshots
i hope this helps you to find your problem too.
regards
Clóvis
On Tue, Jul 1, 2008 at 12:
hi, Christophe,
well, i still dont find the reason about what is my problem, but some things
that help me to avoid the problem to occurs frequently,
i checked the limit for open files on linux, you can check yous with ulimit
-a, here i set to 4096,
how the machines are connected? its with gigabi
n the thread "Tomcat
> bottleneck on InternalInputBuffer.parseRequestLine" ?
>
> Christophe.
>
> - Original Message - From: "Clovis Wichoski" <
> [EMAIL PROTECTED]>
> To: "Tomcat Users List"
> Sent: Thursday, July 03, 2008 3:26 AM
Hi Anthony,
i have same problem sometimes in version 6.0.16, when the thread stuck
occurs again, execute the follow shell script, please adjust for your
scenario.
#!/bin/bash
today=`date +%Y%m%d%H%M%S`
psId=`/opt/java/jdk1.6.0_06/bin/jps | grep Bootstrap | cut -d' ' -f1`
/opt/java/jdk1.6.0_06/bi
Hi,
i'm using tomcat 6.0.16 and if i configure a class that implements
javax.sql.DataSource as the value of the attribute driverClassName of the
Resource element,
when the server starts, the first try to get a connection from JNDI that
fails with follow Exception:
org.apache.tomcat.dbcp.dbcp.SQLN