o: "Tomcat Users List"
Sent: Tuesday, October 17, 2006 9:17 AM
Subject: Re: jvm thread dump
Riz,
> hmmm...still having issues with this. Dont understand why..I commented
> out the A1 appender and uncommented the R appender (as below). The
> applications are still logging to catalina.out !! How do I stop this???
> Please help!
> log4j.rootLogger=INFO, R
> log4j.appender.R=org.apache.log4
hmmm...still having issues with this. Dont understand why..I commented
out the A1 appender and uncommented the R appender (as below). The
applications are still logging to catalina.out !! How do I stop this???
Please help!
#
# Configures Log4j as the Tomcat system logger
#
#
# Configure th
> From: Rizwan Merchant [mailto:[EMAIL PROTECTED]
> Subject: Re: jvm thread dump
>
> #
> # Configure the logger to output info level messages into a rolling
log file.
> #
> #log4j.rootLogger=INFO, R
>
> #
> # To continue using the "catalina.out" file (w
Riz,
> But I am seeing the same log messages (info level from the application)
> being dumped into catalina.out, so these are definitely not System.out
> logs.
You must have an appender that is using stdout or stderr as its
destination. Check out your log4j configuration.
> I do have a log4j.pro
Chris,
I cant thank you enough for all your help. If only there was a rating
system on this forum! ;)
thing is, I am not using ant System.out commands in my app. I have log4j
set up in the app which is logging to a different log file that rolls
nightly.
But I am seeing the same log messages
Riz,
> Quick question, when you look at a thread dump, how do you tell which
> threads are idle?
Idle threads are ones that are not handling any requests. That seems
kind of self-explanatory, but you have to understand what those threads
are doing when they are not doing anything else: they are w
Thanks Chris. You have been very helpful. I will implement your
recommendations and see what happens.
Quick question, when you look at a thread dump, how do you tell which
threads are idle?
Also, any inputs on my other postings regarding the session count and
catalina.out logging?
http://m
Riz,
> here is the thread dump from when the app hung.
> Any insights?
Well, a quick run-through of the thread dump suggests that your DBCP was
definitely stalled for some reason.
I counted about 70 idle threads, about 30 threads waiting on database
connections, and maybe 15 doing other things (
Riz,
> We are using BasicDataSource from apache dbcp for pooling, and the
> methods to set the debug options you mentioned have been deprecated.
Check out
http://wiki.apache.org/jakarta-commons/DBCP#head-735f1d0347421ab736748d8c6ed547ab5050e450
They seem to indicate that (in spite of deprecating
Riz,
> I had to restart tomcat, but I am not sure if there was a simpler way to
> solve the problem at that time.
> There were threads that were waiting on loading user from db (for
> authentication), which explains why I couldnt login.
They were waiting on loading the user data? Or, they were wa
I had to restart tomcat, but I am not sure if there was a simpler way to
solve the problem at that time.
There were threads that were waiting on loading user from db (for
authentication), which explains why I couldnt login.
I can send the thread dump (of hen the problem occurred) tomorrow from
c.Driver
org.hibernate.dialect.MySQLDialect
To: "Tomcat Users List"
Sent: Tuesday, October 10, 2006 3:15 PM
Subject: Re: jvm thread dump
Riz,
> Basically, we could not log into the system at all (which sounded like
> the app could not get a connection to the db to authenticate my user
> name and password). I had someone else try to log in, but he could not
> either.
That sounds like a wild guess at the problem. Your previous threa
Appreciate all your help.
Basically, we could not log into the system at all (which sounded like
the app could not get a connection to the db to authenticate my user
name and password). I had someone else try to log in, but he could not
either.
Here are our tomcat and dbcp settings. We are u
Riz,
> Actually, we had a bit of a situation yesterday, it seems the threads
> were all locked up and/or the db connection pool was not handing out
> connections. I am not sure what happened and have been monitoring the
> threads ever since.
Well, there's yer problem ;)
> Below are some threads
Thanks for the response Chris.
Actually, we had a bit of a situation yesterday, it seems the threads
were all locked up and/or the db connection pool was not handing out
connections. I am not sure what happened and have been monitoring the
threads ever since.
Below are some threads from the
Riz,
> When I perform a thread dump I am seeing some threads are locked on a
> socketRead0 (like http-443-Processor49 in the dump below).
Let's take a look:
> "http-443-Processor49" daemon prio=1 tid=0xb208fe80 nid=0x40c5 runnable
> [0x06fdd000..0x06fddf40]
>at java.net.SocketInputStream
18 matches
Mail list logo
