- Original Message -
From: Arthur D'Alessandro [EMAIL PROTECTED]
To: Tomcat Users List tomcat-user@jakarta.apache.org; Hari
Mailvaganam [EMAIL PROTECTED]
Cc: Igor [EMAIL PROTECTED]
Sent: Tuesday, February 01, 2005 3:40 PM
Subject: Re: Failed JDBC connection hangs Tomcat
What version of the JTDS are you referring to, I know they recently
released 1.0 code...
On Sun, 30 Jan 2005 20:06:07 -0800, Hari Mailvaganam [EMAIL PROTECTED] wrote:
The JTDS driver can cause the hanging you described - this has occured
in a test we did on Win 2k, SQL Server 2k, 1.5 JDK.
Users List tomcat-user@jakarta.apache.org; Hari Mailvaganam
[EMAIL PROTECTED]
Cc: Igor [EMAIL PROTECTED]
Sent: Tuesday, February 01, 2005 3:40 PM
Subject: Re: Failed JDBC connection hangs Tomcat
What version of the JTDS are you referring to, I know they recently
released 1.0 code...
On Sun, 30
and sendNetPacket may hang.
Igor
- Original Message -
From: Arthur D'Alessandro [EMAIL PROTECTED]
To: Tomcat Users List tomcat-user@jakarta.apache.org; Hari
Mailvaganam [EMAIL PROTECTED]
Cc: Igor [EMAIL PROTECTED]
Sent: Tuesday, February 01, 2005 3:40 PM
Subject: Re: Failed JDBC connection hangs
The JTDS driver can cause the hanging you described - this has occured
in a test we did on Win 2k, SQL Server 2k, 1.5 JDK.
reagrds,
Hari Mailvaganam
On Sun, 30 Jan 2005 08:39:50 +0200, Igor [EMAIL PROTECTED] wrote:
We have the same problem, that described in
We have the same problem, that described in
http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg58799.html
There is ServletContextListener in our application, that schedule two tasks for
repeated fixed rate execution on context initialization
(Timer.scheduleAtFixedRate).
First task
Here is some sample init() method code that I use to test the db
connection on context startup:
try {
/*-
* The driver objects register themselves with the driver
manager
* at the time of loading,
Yes, it is important to close your connections when you're done with
them, and this is considered in each of our methods.
The problem we are seeing with the hung connections, however, occurs
before any SQLException has been thrown, anywhere in the servlet
engine. In fact, even if the very
hmm
I think in that case you would have to set a Timeout on the
connection. You might want to test the connection upon context startup and
if the connection times out, then throw an error or redirect to a static
page saying that the app is temporarily unavailable.
Not sure what else you
Sorry it's been a week since you sent this message... Too much traffic
here for me to keep up. This problem is the only reason I'm subscribed
to this list at all. I normally only follow -dev (and if I could point
to a specific problem in Tomcat I'd ask there instead).
I have this problem
HI Paul,
You simply need to make sure that you've let go of your resources such as
connections, resultsets, etc
Here is some sample code for that...
Connection conn = null;
PreparedStatement pstmt = null;
ResultSet rs = null;
String query = SELECT * FROM mytable;
try {
pstmt =
BTW, in the code below, I forgot to create the connection at the beginning
of the try statment. Just wanted to note that you will need to do that.
conn = openConn(); //openConn() grabs the connection from a pool or
creates a brand new connection
Just insert that and whatever you need to do
Let me first set up my situation. On my server, I
have two webapps running, webapp A and webapp B.
Webapp A uses JDBC Thin driver to contact an Oracle
database at remote location 1. Webapp B uses JDBC
Thin driver to contact an Oracle database at remote
location 2.
If the internet connection
PROTECTED]
Subject: Failed JDBC connection hangs Tomcat
Let me first set up my situation. On my server, I
have two webapps running, webapp A and webapp B.
Webapp A uses JDBC Thin driver to contact an Oracle
database at remote location 1. Webapp B uses JDBC
Thin driver to contact an Oracle
I attempted that, and webapp B still hangs up waiting
on webapp A.
--- Andrew Conrad [EMAIL PROTECTED] wrote:
That sounds like a threading issue for the JDBC
Driver, if you are using
the same instance. You could move the Oracle Driver
to the WEB-INF\lib
directory for each webapp.
-
similar problems. Do you have the
same problem with two stand-alone applications?
-Andrew
-Original Message-
From: Bill D [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 08, 2002 4:08 PM
To: Tomcat Users List
Subject: RE: Failed JDBC connection hangs Tomcat
I attempted that, and webapp B
16 matches
Mail list logo