I had a similar problem on RH EL just a couple of weeks ago. Might not be
the same as yours, though, because in my case apache wasnt hung, just
tomcat. but that might just be a difference in versions, so i'll share it
anyway.
Here's what i did..
I used kill -QUIT on the tomcat process after it
If you havent already done it, next time it goes crazy try to get a stack
trace of all threads with kill -QUIT.
-Original Message-
From: John Villar [mailto:[EMAIL PROTECTED]
Sent: Saturday, 21 August 2004 12:16 AM
To: Tomcat Users List
Subject: Re: Help with a real ugly one
how
records. In JDBC caching is primarily
the responsability of the Driver.
Brad McEvoy escribió:
something like this should do the trick
...
PreparedStatement pstmt =
con.prepareStatement(sql,ResultSet.TYPE_FORWARD_ONLY,ResultSet.CONCUR_READ_
O
NLY);
pstmt.setFetchSize(100);
ResultSet rs
I'm using Clob's with oracle at the mo, and i've found that the standard
ResultSet interface has everything we need, but the Clob (or Blob) is the
thing which needs to be cast to an oracle specific class
public ResultSet rs;
public Clob clob;
...
rs = cmd.executeQuery();
clob = rs.getClob(1);
something like this should do the trick
...
PreparedStatement pstmt =
con.prepareStatement(sql,ResultSet.TYPE_FORWARD_ONLY,ResultSet.CONCUR_READ_O
NLY);
pstmt.setFetchSize(100);
ResultSet rs = pstmt.executeQuery();
...
-Original Message-
From: QM [mailto:[EMAIL PROTECTED]
Sent:
are below..
linux Red Hat EL
kernel 2.4.21-17.ELsmp (as per recommendation on Bug 120341 for ibm blades)
tomcat 4.1.30
apache 2.0.49
mod_jk 2.04
glibc 2.3.2-95.20
java 1.4.2_02 - Sun VM
Any help would be greatly appreciated,
Brad McEvoy