Thank you Mark for answerting.
We are still experiencing the problems: when database becomes unavailabe, in
exact time after CallableStatement.execute() is finished (executed) and when
we start retrieving the records sets from called stored procedure, thread is
never passing the line statement.getObject() (we saw that in debuger).
Here is the part of the source code:
for (int i = 1; i <= outParametersCount; i++) {
resultSet = (ResultSet) statement.getObject(inputParameterCount +
i);
resultSetList.add(resultSet);
resultVector.add(packResultData(resultSet, true));
}
Do anyone have a clue why this happen?
NOTE: We're using tomcat resouce datasouce to access database.
BR,
Drazen
-----Original Message-----
From: Mark Thomas [mailto:[EMAIL PROTECTED]
Sent: 22 March 2007 00:48
To: Tomcat Users List
Subject: Re: Connections in tomcat resource "in busy" state forever
Drazen Nikolic wrote:
> Is there a possibility to remove those connection, or to threat them
> somehow not be become busy forever?
Configuring a time-out (to close them if they are open too long) and a
validation query (to fix any connections broken when the db goes down)
should help.
Mark
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe,
e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
__________ NOD32 2134 (20070322) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
