http://java.sun.com/products/jsp
http://archives.java.sun.com/jsp-interest.html
http://forums.java.sun.com
http://www.jspinsider.com
AM
To: [EMAIL PROTECTED]
Subject: Re: Closing a ResultSet, was "Re: odd oracle error"
rs.close() and stmt.close() should be in the finally block.
-
I have had a problem too when closing the result set. I found t
general Exception
returning back now..");
throw new ServletException();
}
} //end doGet
Regards,
Martin
- Original Message -
From: "William W. Nelson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, Feb
ltSet, was "Re: odd oracle error"
rs.close() and stmt.close() should be in the finally block.
-
I have had a problem too when closing the result set. I found this
example on "Resin's" web site
rs.close() and stmt.close() should be in the finally block.
-
I have had a problem too when closing the result set. I found this
example on "Resin's" web site. It is not an Oracow database, but it may
serve as an exa
To: [EMAIL PROTECTED]
> Subject: Closing a ResultSet, was "Re: odd oracle error"
>
> Cosmin Cremarenco <[EMAIL PROTECTED]> wrote:
>
> > I agree that the Statement and the PreparedStatement must be
> > explicitly closed. But what about the ResultSet. How come t
I have had a problem too when closing the result set. I found this
example on "Resin's" web site. It is not an Oracow database, but it may
serve as an example.
T.K.
public void init()
throws ServletException
{
try {
Context env = (Context) new
InitialContext().lookup("java:comp/e
Hi all,
Its always better to explicitly close the ResultSet. I have followed the
just closing the statement approach and have still got the max open cursors
error with Oracle.
Pranav
At 09:46 AM 1/31/2003 -0500, you wrote:
>Cosmin Cremarenco <[EMAIL PROTECTED]> wrote:
>
>> I agree that the Statem
Closing the statement closes the resultSet.
-
I agree that the Statement and the PreparedStatement must be explicitly
closed. But what about the
ResultSet. How come the following piece of code works?
try{
for(int i=0;i<1000;i++)
WRes.selectInfoProd(connection,182);
}catch(E
Cosmin Cremarenco <[EMAIL PROTECTED]> wrote:
> I agree that the Statement and the PreparedStatement must be
> explicitly closed. But what about the ResultSet. How come the following
> piece of code works?
> ...
According to the SDK v1.4.1 API documentation for the ResultSet
interface:
"A ResultS
ECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 29, 2003 1:10 PM
Subject: Re: odd oracle error
> We used to get this too and fixed it by making sure that any Statements
and
> ResultSets we create are explicitly closed in finally blocks. It appears
> that these objects hold a c
nt: Wednesday, January 29, 2003 4:39 PM
Subject: Re: odd oracle error
> Database end
> You need to increase the number of allowable
> open cursors at the database end. Please lookup
> your Oracle documentation to get to the right
> point.
>
> Close ResultSets
> This happ
Database end
You need to increase the number of allowable
open cursors at the database end. Please lookup
your Oracle documentation to get to the right
point.
Close ResultSets
This happens because you do not close ResultSets.
Rule - close everything
Remember that the rule is to close every resour
hello
at rare, random times we get the following error from our oracle 8i server
(8.1.7):
java.sql.SQLException: ORA-01000: maximum open cursors exceeded
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
at oracle.jdbc.t
14 matches
Mail list logo
