Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Closed ResultSet error
- From: Kris Jurka <books(at)ejurka(dot)com>
- To: Bayless Kirtley <bkirt(at)cox(dot)net>
- Cc: "List, Postgres" <pgsql-general(at)postgresql(dot)org>
- Subject: Re: Closed ResultSet error
- Date: Wed, 30 Apr 2008 16:06:37 -0400 (EDT)
- Message-id: <Pine(dot)BSO(dot)4(dot)64(dot)0804301604490(dot)11710(at)leary(dot)csoft(dot)net>
On Wed, 30 Apr 2008, Bayless Kirtley wrote:
I am migrating from another database to PostgreSQL and have run into a serious problem. The Java program runs fine on the other DB but under PostgreSQL it gives the error, "ResultSet is closed."I have removed all occurrences of closing any result sets and there are no instances of closing underlying statements within those methods. Finally, I have stepped through the entire operation with a debugger and found no unexpected events. Each time a new result set was created, the debugger indicated it to be a new entity. When finally returning to the original, it appeared to be the correct instance.
When the same statement is used to execute a second query, the first ResultSet is closed automatically. I'm guessing that this is what's happening to you and you need to be sure to create a new Statement for each concurrently open ResultSet you have.
Kris Jurka
- References:
- Closed ResultSet error
- From: Bayless Kirtley
- Closed ResultSet error
- Prev by Date: Closed ResultSet error
- Next by Date: Full Text Search. In 8.3.1 How ?
- Previous by thread: Closed ResultSet error
- Next by thread: Full Text Search. In 8.3.1 How ?
- Indexes: