I'm having a weird problem with Tomcat locking up. I have a couple of
functions on my site that rely heavily on transactions. To do a simple
load test, I picked the function that hits the database the most and
opened that same page in two different browser windows. I hit the
submit button at
Howdy,
Can you share your code that serves the page that locked up?
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Hooper, Brian [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 11:19 AM
To: Tomcat Users List
Subject: Tomcat Deadlock
I'm having a weird
(but that
isn't very precise due to buffers and caches).
Sorry for the rest.
-Original Message-
From: Hooper, Brian [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 5:19 PM
To: Tomcat Users List
Subject: Tomcat Deadlock
After that, the site was no longer accessible. The
only way
;
}
}
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 11:23 AM
To: Tomcat Users List
Subject: RE: Tomcat Deadlock
Howdy,
Can you share your code that serves the page that locked up?
Yoav Shapira
Millennium ChemInformatics
-Original
AM
To: Tomcat Users List
Subject: RE: Tomcat Deadlock
The code itself is pretty long. Maybe it would be better if I explain
how I handle database connectivity (which I'm guessing has some flaws),
and I know I should be encapsulating my queries in EJB's, but for now I
just have a lot of inline SQL
: RE: Tomcat Deadlock
First off, if you have the option you might try using a database pool
instead of using 1 connection for multiple threads (As in Tomcat).
At one company I worked for we had some problems with using 1
connection. Data would be read/written incorrectly. Results from one
query
[mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 12:20 PM
To: Tomcat Users List
Subject: RE: Tomcat Deadlock
I thought I was by defining the data source (using
org.apache.commons.dbcp.BasicDataSourceFactory) in my server.xml file
and using JNDI to access it?
-Original Message-
From
:25 PM
To: 'Tomcat Users List'
Subject: RE: Tomcat Deadlock
Take a look at this.
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-datasource-examples
-how
to.html
Every time you load a page open the connection, then close it to release
it to the pool. That way each thread should get 1
.
-Original Message-
From: Hooper, Brian [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 12:50 PM
To: Tomcat Users List
Subject: RE: Tomcat Deadlock
I followed the example for Tomcat 4.x when I set it up. The only reason
I have a separate object is to hide some of the complexity. I'm
up that checks to see if the user
is authenticated, so the database is hit before every page request.
-Original Message-
From: Steve Nelson [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 1:59 PM
To: 'Tomcat Users List'
Subject: RE: Tomcat Deadlock
Hrmm... Do you create
To: Tomcat Users List
Subject: Tomcat Deadlock
I'm having a weird problem with Tomcat locking up. I have a couple of
functions on my site that rely heavily on transactions. To do a simple
load test, I picked the function that hits the database the most and
opened that same page in two different
11 matches
Mail list logo
