Am Freitag, den 25.01.2008, 16:40 -0500 schrieb tc:
> The calls look like this:
>
> public void testXXX(DataSource ds, String login) {
> PreparedStatement ps=null;
> ResultSet rs=null;
>
> try {
> ...
> }catch (Exception e) {
> System.out.println("Exception: " + e);
>
> -BEGIN PGP SIGNED MESSAGE-
>
> Are you using a connection pool? If so, which one?
>
I'm trying to figure this out. I don't see any evidence of one configured
in the server.xml file. If not, I presume it would be a good idea for us
to start using one?
> You need to make sure that you
> From: Christopher Schultz [mailto:[EMAIL PROTECTED]
> Subject: Re: Tomcat App becomes Unresponsive
>
> David Delbecq has already told you that sending a SIGQUIT to a running
> JVM will generate a thread dump on standard output.
I recently found another tool to take stack dum
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tc,
tc wrote:
| Thanks for the suggestions. I will have a look at the source and see how
| the app is interacting with the database.
|
| I don't think the whole tomcat server freezes; just the one application.
Okay. That could be an app-specific db
ry 21, 2008 8:22 PM
Subject: Re: Tomcat App becomes Unresponsive
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Tc,
> >
> > tc wrote:
> > | The developers think there may some issue with the database. They
have
> > | also done mu
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Tc,
>
> tc wrote:
> | The developers think there may some issue with the database. They have
> | also done multi-user testing without being able to reproduce the
> problem.
>
> If they think it's the database, it's probably their code interacti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tc,
tc wrote:
| The developers think there may some issue with the database. They have
| also done multi-user testing without being able to reproduce the problem.
If they think it's the database, it's probably their code interacting
with the databa
Okay, sounds good. Thanks. Now if I could just figure out how to cause
it to happen...
> If you are on a UNIX jvm, issue a signal 3 (SIGQUIT) to the jvm process
> when tomcat stops responding. It will dump on standard-out (normaly
> redirected to catalina.out) the list of Threads with a stacktra
If you are on a UNIX jvm, issue a signal 3 (SIGQUIT) to the jvm process
when tomcat stops responding. It will dump on standard-out (normaly
redirected to catalina.out) the list of Threads with a stacktrace for
each. By invstigating stacktrace you will get clues as where the problem
is. I don't
I have been asked to investigate a tomcat/java application.
The basic problem is that this application sometimes becomes unresponsive
if more than one user uses it at a time. Restarting Tomcat clears the
problem. I don't think it has ever occurred when only one person was
using the app.
It is a
10 matches
Mail list logo
