Closing Statements and ResultSets

I just recently realized that you need to close Statements and ResultSets in order to avoid getting the "Too many cursors"-message.
My question is:
Do you need to close both Statements and ResultSets?
- not that it's a problem...
if so:
Does it matter which one you close first?

I usually place the stmt.close() code in my finally block, to ensure that the statement gets closed, even if a SQLException occurs during the query/update. The ResultSet does not explicitly have to be closed, ... it is automatically closed when the Statement is closed, or if a new query is run on the same statement.

Similar Messages

JDBC: Closing Connection does it close statement and resultset

In my application I am facing ORA-0100 Maximum open cursors exceeded problem. We are executing quite a few queries and stored procedures before we close the connection object. But in few places statements and resultsets are not closed. Can these be a problem? Shouldn't they be automatically closed when the connection is closed?
We are executing this block of code in a loop.

in few places statements and
resultsets are not closed. Can these be a problem?Yes.

Statement and ResultSet Interface type of Object

Hi,
Can any one explains me where exactly (in which Class) the implementation of the Statement and ResultSet Interface type of Object Instance be created
Regards
Krishna

I dont really understand what you are trying to ask but:
Your JDBC driver has concrete implementations of Statement and Resultset. If you want to know what classes are being used try something like:Connection con = ??;
Statement st = con.createStatement();
ResultSet rs = st.executeQuery( "???" );
System.out.println( "Connection class: " + con.getClass().getName() );
System.out.println( "Statement class: " + st.getClass().getName() );
System.out.println( "ResultSet class: " + rs.getClass().getName() );

Pooling Prepared Statement and Resultset

Is their any mechanism in Weblogic by which we can pool prepared statements and
resultset.

Yes you can cache prepared statements. The connection pool will
automatically cache the prepared statements (10 prepared statement was the
limit in previous so you may want to write some startup class to load the
imp prepared statements.). When you reuse the prepared statement the
connection pool will pick it from its prepared statement cache. In 6.1 you
can configure the number of prepared statements that you want to cache.
But you cannot have multiple resultsets open for the same statement object.
You can have cache rows though.
Please search the bea newsgroups for more info. There are a bunch of posts
that will be helpful to you.
http://search.bea.com/weblogic/gonews/
sree
"hogan" <[email protected]> wrote in message
news:3bd9cf88$[email protected]..
>
Is their any mechanism in Weblogic by which we can pool preparedstatements and
resultset.

Automatically closing statements

Hi. Is there a way to automatically close all statements and ResultSets associated with a Connection if all you have is the Connection? (without closing the Connection)
Thanks.

No, but you can make one. Subclass or wrap Connection, and every time a statement is requested, keep a reference to it. Then you can just iterate through all your references and close them.

How to find out resultset,statements and connections are not closed

Hello,
In Jdeveloper 10.1.2 how can I find out that in my code,
I have resultset,statements and connections are not being closed.
Any help is highly appreciable.
Thanks

Hello Vijay,
On MSSQL truncation of transaction log does not shrink the size of the transaction log. It simply removes the content within the transaction log and writes it to the backup.
Meaning the free percentage within the transaction log will increase.
If you want to Resize the transaction log size, you need to do something else.
The shrinking procedure is given here:
http://support.microsoft.com/kb/907511
Regards,
Siddhesh

TopLink and ResultSet: ojdbc14 vs. ojdbc6 - Closed command

Hi all,
I have problem with ojdbc library. We updated our ojdbc library from ojdbc14 to ojdbc6. But now, we have problem with SQLExcpetion: "java.sql.SQLException Closed statement".
We have following code:
Object result = session.executeQuery(query, args);
Map map = (Map)((Vector)result).firstElement();
// the data is in data type OracleResultSetImpl !!!
OracleResultSet out_data = (OracleResultSet) map.get(EmtasConstant.GRID_PROCEDURE_DATA_OUT);
OracleResultSetMetaData metadata = (OracleResultSetMetaData) out_data.getMetaData();
If we used library "ojdbc14.jar" everything works fine, we get metadata, read data from resultSet, etc... No problem!
But if we using "ojsbc6.jar" and call getMetadata, then throws: "java.sql.SQLException: Closed command: getMetaData" .. or "ava.sql.SQLException: Closed command: next()" or whatever we call on OracleResultSet out_data (we try OracleResultSet and ResultSet too)..
If we used "ojdbc14.jar" and I call out_data.close(), they throws same exception => Why is the ResultSet in library ojdbc6.jar closed??????
Any idea? I'm really stuck and I all day trying to come to solve the problem, but I resolved nothing.
Pls help!
Thx!
Best regards, KLD!
Sry for my English ;)

Yes, I have newest version of TopLink (11.1.1. ...) and Java (1.6_09).
Or, is any option how to convert ResultSet to any "normal" java object (like hasmap,collection, list, ...)
I returned multiple cursor objects from stored procedure, and I resolved it as follows:
More output cursors with StoredProcedureCall?
but now I have problem with ResultSet and i don't want call more times the procedure call (first option)...

Weblogic JTA timeout and PreparedStatement cache problem (Closed Statement)

Hello,
I am facing up a problem using a Weblogic connection pool with a PreparedStatement.
Here is the environement :
- Weblogic application server 10.3
- JDBC connection pool with Oracle Thin driver (from server library) - all parameters by default i.e. StatementCache size = 10
- JTA transaction timeout = 30s
The problem is : if a prepared statement ends because of a JTA timeout, I receive the following stack exception/ stack trace
java.sql.SQLException: The transaction is no longer active - status: 'Rolling Back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 33 seconds
BEA1-000D8AE7230EFAA3EDC9]'. No further JDBC access is allowed within this transaction.
at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:178)
at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:188)
at weblogic.jdbc.wrapper.Connection.preInvocationHandler(Connection.java:92)
at weblogic.jdbc.wrapper.Connection.clearCachedStatement(Connection.java:814)
at weblogic.jdbc.wrapper.PreparedStatement.clearCachedStatement(PreparedStatement.java:1357)
and then, if we try to re-execute immediately the same operation (*same statement* but new request, new thread, new JTA transaction ...) we receive without delay the following exception :
java.sql.SQLException: Closed Statement
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:229)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:403)
It seems like a bug in the caching mechanism of Weblogic, the 1st stack trace shows method from the statement cache implementation, I presume weblogic is trying the clear the statement from the cache after the iniitial TimedOutException (SQLException), but as the JDBC connection is unusable at this point, the clearing fails and the statement remains in the cache but is physically closed by JDBC.
1st question, why weblogic does need to call JTSConnection.checkConnection() for clearing a statement from its internal cache, it is a pure java memory operation isnt'it ?
2nd question : How to solve the problem without setting the StatementCache size to 0 (I tried, it solves the problem)? I don't want to disable completely the Weblogic statement caching, I have a small PreparedStatement called very frequently.
Thanks for any help

The main issue is that the transactional context that is supposed to underlay the JDBC code being executed,
has gone away. Indeed, any DBMS changes that may have been made by your code so far, have been rolled
back and are gone. Your code should not be trying to continue JDBC as normal, and WebLogic is trying to stop
you. The control flow should go back up to the location where the transaction was initiated, so as to restart from
the beginning if that is what is desired, including getting a new JDBC connection and remaking all the statements
etc.
HTH,
Joe
Edited by: Joe Weinstein on Dec 3, 2010 9:12 AM

One Statement - Many ResultSets??

Hey Folks,
how good of an idea is it to use just one DB Statement and than make many queries on it ending up in different resultsets:
Like this:
try
               Class.forName("com.mysql.jdbc.Driver").newInstance ();
               con = DriverManager.getConnection (url, benutzer, passwort);
               stmt = verbindung.createStatement();
          catch (Exception e)
               e.printStackTrace();
ResultSet rs7 = null;
          try {
               rs7 = stmt.executeQuery("SELECT * FROM artikel WHERE `artikel_nr` = " + artikelnr);
               while ( rs7.next() ) {
                    level = rs7.getInt("persopreislevel");
          } catch (SQLException e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
rs7.close();
ResultSet rs8 = null;
          try {
               rs8 = stmt.executeQuery("SELECT * FROM artikel WHERE `artikel_nr` = " + artikelnr);
               while ( rs8.next() ) {
                    level = rs8.getInt("persopreislevel");
          } catch (SQLException e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
rs8.close();Or would I have to create one Statement per ResultSet?? How do I avoid creating to many Objects??
My Problem is that i get NoOperationAllowed after ResultSet closed Errors once in a while, even though I am using different Resultsets but JDBC Api says 1 ResultSet per Statement right?
Best regards
Edited by: eCashier on Apr 1, 2008 7:26 AM

Why not use a prepared statement and then a loop iterating through the parameters that you want to supply to the query instead of hardcoding eight queries that do essentially the same thing?
But no, there's no profound overhead from opening multiple resultsets in sequence as long as you close them when you're done with them. You should close them in a finally block. The overhead from the result set objects is unlikely to be significant as long as they're closed.

Interleaved executeQuery's intermittant SQLException: Closed Statement

When i run the following code using JDK1.3.1 and Oracle 817 i see the line "cats_rs = cats_stmt.executeQuery();" throw a "SQLException: Closed Statement." about 1 out of 10 times.
All variables, except the connection, are local. the statement example below are just 2 among dozens of others - all using the same connection.
Any ideas why i'd get an intermittant exception like this?
It is totally stumping me. thanks in advance.
memory_stmt = connection.prepareStatement(memory_sql,
ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_READ_ONLY);
cats_stmt = connection.prepareStatement(cats_sql,
ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_READ_ONLY);
index = 1;
memory_stmt.setString(index++, host);
memory_stmt.setString(index++, jvm);
memory_stmt.setLong(index++, starttime);
memory_stmt.setLong(index++, endtime);
memory_rs = memory_stmt.executeQuery();
index = 1;
cats_stmt.setString(index++, host);
cats_stmt.setString(index++, jvm);
cats_stmt.setLong(index++, starttime);
cats_stmt.setLong(index++, endtime);
cats_rs = cats_stmt.executeQuery();
E.g.
java.sql.SQLException: Closed Statement
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:222)
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:285)
     at oracle.jdbc.driver.OracleStatement.ensureOpen(OracleStatement.java:5681)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:409)
     at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:366)
Thx, Tim

I had a hunch that this was a limitation or bug in the driver or pool. I also read in forums that the connection "manages" each Statement it prepares or creates; like it adds it to a List and such ; it also cleans the slate each time the connection is closed.
This code example above is just a small snippit that summarizes over a long time range of data (like days) - that is potentially 1000s of statements and queries and result sets.
It is probably not very common that with jdbc someone prepares and executes 1000s of queries on the same connection over a course of 2 - 10 minutes (that's how long the entire operationcould take). I guessed the connection was worn out and tired .
I changed the code to get a connection and then close the connection periodically - instead of getting one connection and using it for the whole period. After that all these hard to explain Closed Statement exceptions disappeared.
i think the interleaving queries is OK. I guess the connection was blowing out.

Interleaved executeQuery() generates SQLException: Closed Statement

When i run the following code i see the cats_stmt.executeQuery() line throw a "SQLException: Closed Statement.".
Since I just created the cats_stmt statement - why could it be closed?
The memory_stmt.executeQuery runs without exception.
memory_stmt = connection.prepareStatement(memory_sql,
ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_READ_ONLY);
cats_stmt = connection.prepareStatement(cats_sql,
ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_READ_ONLY);
index = 1;
memory_stmt.setString(index++, host);
memory_stmt.setString(index++, jvm);
memory_stmt.setLong(index++, starttime);
memory_stmt.setLong(index++, endtime);
memory_rs = memory_stmt.executeQuery();
index = 1;
cats_stmt.setString(index++, host);
cats_stmt.setString(index++, jvm);
cats_stmt.setLong(index++, starttime);
cats_stmt.setLong(index++, endtime);
cats_rs = cats_stmt.executeQuery(); <<- throws exception.
On JDK1.3.1 and Oracle 817
E.g.
java.sql.SQLException: Closed Statement
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:222)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:285)
at oracle.jdbc.driver.OracleStatement.ensureOpen(OracleStatement.java:5681)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:409)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:366)

I had a hunch that this was a limitation or bug in the driver or pool. I also read in forums that the connection "manages" each Statement it prepares or creates; like it adds it to a List and such ; it also cleans the slate each time the connection is closed.
This code example above is just a small snippit that summarizes over a long time range of data (like days) - that is potentially 1000s of statements and queries and result sets.
It is probably not very common that with jdbc someone prepares and executes 1000s of queries on the same connection over a course of 2 - 10 minutes (that's how long the entire operationcould take). I guessed the connection was worn out and tired .
I changed the code to get a connection and then close the connection periodically - instead of getting one connection and using it for the whole period. After that all these hard to explain Closed Statement exceptions disappeared.
i think the interleaving queries is OK. I guess the connection was blowing out.

Difference in Customer account statement and collections

Kindly clarify my doubts about customer account steatement and Collections. basically whats the difference in the two and what are the standard T_codes for these two.
thanks
anya

HI ANYA
T-code: F.27
Definition
An account statement and open item list are two types of correspondence. They differ with respect to the information they contain and the way it is displayed. Unlike an open item list, an account statement displays all items in a specified period along with the balance carried forward. The open item list merely displays the open items for a certain key date.
Type of correspondence that your company sends to its customers.
The system includes a SAPscript form that you can use for customer account statements for the Philippines, form F140_CUS_STAT_P1. You can modify this template to meet your company's requirements. To do so, from the SAP Easy Access screen, choose Tools ® Form printout ® SAPscript ® Form.
Structure
The following information is displayed in the template for the customer account statement:
Account balance at the start of the selected period
Open item list as of the key date, including the total
It is sorted by transactions with or without special G/L indicators, currency, posting date, and document number.
Account balance at the end of the selected period
Cleared item list between selected key dates
It is sorted by currency, posting date, and cleared item document number.
Withholding tax list between selected key dates
It is sorted by withholding tax type, posting date, and document number.
Aging in 0, 30, 60, 90, and 120 days
Integration
You can print the customer account statement.
Note the following restrictions regarding customer statements:
You cannot create statements for one-time customers.
In the case of customer head offices with local branches, customer statements contain the address of the head office and not that of the branch.
The account statement can be created for your customers or vendors is an extract from the customer account which enables him to check the items there or is merely for information purposes. The account statement displays the balance carried forward, all items in the chosen period and the closing balance of the account.
The open items list is a special form of account statement. It is also sent to the customer for verification or information purposes. Occasionally, the list is also used as a reminder letter. The open items up to the chosen key date are displayed in this list.
Both letters contain the document number or reference document number, the document date, the document type, the currency and the amount for every item as well as the balance of the open items at the key date. The account statement may also contain the clearing document number. If branches were included in the letter of a head office, their addresses are listed at the end of the letter.
The layout of the letter is determined via a form. Depending on the form used, the letter may also contain, for example, the days in arrears per item at the key date or other information. The form must be defined and stored in the system.
Printing Customer Account Statements
Use
Printing of customer account statements is based on correspondence type SAPP3. Correspondence type SAPP3 is preconfigured to run the RFKORDP3 print program, which is delivered with report variant SAP&SAPP3. You can modify SAP&SAPP3 to meet your company's needs. For example, you can change the aging period and the number of the aging column.
To modify or define a new report variant for the RFKORDP3 print program, in Customizing for Financial Accounting, choose Financial Accounting Global Settings -- Correspondence -- Assign Programs for Correspondence Types. Select correspondence type SAPP3 and choose Environment -- Maintain variants.
Procedure
Printing Individual Account Statements:
Request correspondence type SAPP3 . To do so, from the SAP Easy Access screen, choose Accounting -- Financial Accounting --Accounts Receivable --Account -- Correspondence --Request.
Issue the correspondence request by choosing Accounting -- Financial Accounting -- Accounts Receivable -- Periodic processing -- Print correspondence -- As per request.
Print the customer account statement from the spool file by choosing System -- Own spool requests. Select your spool request and choose print.
COLLECTIONS
Collection is the settlement of receivables due, in particular, bills of exchange.
Collection Account
Definition
A G/L account that the system uses to record checks receivable that you have presented to banks for collection. It denotes that a check has been sent to a bank and is awaiting clearing
Reward if useful to u
narendran vajravelu

Closed Statement Exception

hi,
I'm using OC4J version "Oracle Application Server Containers for J2EE 10g (9.0.4.3.0) (build 060411.1838)" as my application server running on AIX 5.3 with java version "1.4.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1)
Classic VM (build 1.4.1, J2RE 1.4.1 IBM AIX build ca1411-20030930 (JIT enabled:
jitc)).
Recently i encountered the Closed Statement Exception occasionally, from the stack trace, this exception was thrown during the time i commit the transaction. I wonder is this a bug in the OC4j.jar file ? Please advice me how to overcome this problem. Thanks
java.sql.SQLException: Closed Statement
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java(Compiled Code))
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java(Inlined Compiled Code))
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java(Inlined Compiled Code))
at oracle.jdbc.driver.OracleStatement.ensureOpen(OracleStatement.java(Inlined Compiled Code))
at oracle.jdbc.driver.OraclePreparedStatement.sendBatch(
OraclePreparedStatement.java(Compiled Code))
at oracle.jdbc.driver.OracleConnection.commit(OracleConnection.java(Compiled Code))
at com.evermind.sql.FilterConnection.commit(FilterConnection.java(Compiled Code))
at com.evermind.sql.OrionCMTConnection.commit(OrionCMTConnection.java(Compiled Code))
at com.evermind.sql.ConnectionBCELProxy.commit(ConnectionBCELProxy.java(Compiled Code))

thanks for the replies, from the stack trace, it seems that the exception is thrown at the time of "commit", but my close statement is put in the finally block, so there is no way the connection is closed and recently this exception just disappear without changing code.

Closed Statement,

Hi,
I am using JDBC8.1.6 thin driver
with Apache Jserv on Sun Solaris 7 box.
I am using PooledConnection to get the connection from the database.
On some of the queries I am getting "Closed Statement" when I am trying to execute them,
although I am getting the connection right before I execute the query.
There is no explicit call to "close()"
between the "prepareStatement()" and
"executeQuery()", nevertheless, I am
getting "Closed Statement" error in about 50%
of all the cases.
Please help me!
Please, CC to [email protected]
Thank you!
Michael Larionov.
The stack trace follows:
java.sql.SQLException: Closed Statement
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.sql.SQLException.<init>(SQLException.java:43)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:219)
at oracle.jdbc.driver.OracleStatement.ensureOpen(Compiled Code)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(Compiled
e)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(Compiled C
at com.sonata.mysonata.edit.consumer.c_home.EnableServiceModule.popul
(Compiled Code)
at com.sonata.delivery.module.AbstractModule.initialize(AbstractModul
ava:233)
at com.sonata.delivery.jsp.SonataJSP.handleCurrentPageInitialization(
ataJSP.java:505)
at com.sonata.delivery.jsp.SonataJSP.service(SonataJSP.java:283)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
at org.gjt.jsp.JspServlet$Page.process(Compiled Code)
at org.gjt.jsp.JspServlet.service(JspServlet.java:284)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
at org.apache.jserv.JServConnection.processRequest(JServConnection.ja
339)
at org.apache.jserv.JServConnection.run(JServConnection.java:202)
at java.lang.Thread.run(Thread.java:479)
null

This could happen if you got another
logical connection after you got the
first one. The spec. says that yoou can't
have more than one logical connection and
the most recent one is the active. So
we remove the connection link to the ones
created earlier.
Please read the JDBC 2.0 optional spec.
for further details.

Oracle :Closed statement exception

Hi,
Iam trying to migrate a j2ee application to NetWeaver. Iam getting Oracele closed statement exception while executing a code which works fine with other servers like weblogic and jboss. My code is some thing like this
stmt = con.prepareStatement
result = stmt.executequery
if(result.next())
working_fine = result.getString("something");
callInsertMethod(con);
con.commit();
not_working_fine = result.getString("somethingelse")
I am getting this exception at the above bolded line. iam calling another method where some database insertions and al happen and connection commit also happens.Any help?

Sujesh,
if I understood correctly, you're calling bothe some instertions + commit in the method callInsertMethod(con) before the emphasised line is called. As far as my experience tells me, that's not ok, because a commit might clear/close other result sets on the same connection. For the code snippet you've posted I'd say just move the emphasized line before callInsertMethod(con).
Additionally I'd suggest to explicitly close the statement (the result set too if you're not relying on driver JDBC compliance) and if callInsertMethod(con) already commits, to delete the con.commit().
Btw., the JavaDoc should be your best friend, here a detail from java.sql.Connection.commit():
Makes all changes made since the previous commit/rollback permanent and releases any database locks currently held by this Connection object.

Closing Statements and ResultSets

Similar Messages

Maybe you are looking for