If the DBA is manually killing off your connections, then the pool needs to be
paranoid about checking to see if the connection is available before each operation.
So this adds overhead to using the pool. In addition, consider this code:
Connection cn = pool.allocate();
Statement stmt = cn.createStatement("some sql here");
ResultSet rs = stmt.execute();
Given the above, the pool could check the state of the connection before it returns
from allocate(), but the other exception handling would be up to you. A SQLException
could get thrown from createStatement() or from execute() if the DBA whacks the
connection. You could also get an exception while iterating thru the resultset.
So, I don't think that a more robust connection pool would totally solve your problem.
--Kevin
-----Original Message-----
From: Rick Reumann [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 27, 2002 10:40 AM
To: Struts List
Subject: [OT] conn pooling - what next?
I know this topic has come up in the past, but I'm wondering if
someone can help. I haven't tried Struts or Tomcat connection pooling,
but have tried some others recommended. The latest one recommended on
a Tomcat post was http://connpool.jensn.de/index.html and it seemed to
be working great.
The problem, though, with this one and other ones I've tried, is that
when the open connections are manually killed by the DBA the conn pool
does not work.
I end up with an error like this:
java.sql.SQLException: Io exception:
Software caused connection abort:
socket write error
or
java.sql.SQLException:
ORA-00028: your session has been killed
Is there connection pooling that someone can recommend that will be
able to handle when connections are manually killed? I wouldn't be
surprised with the way things are set up here that no connection
pooling will work in our environment, but maybe someone can recommend
a very good one to use. Should I go with the struts pooling, tomcat's,
or maybe even poolman if it's still around?
Thanks for any help.
--
Rick
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
