Re: Getting "This ResultSet is closed" exceptions
От | Andres Olarte |
---|---|
Тема | Re: Getting "This ResultSet is closed" exceptions |
Дата | |
Msg-id | 3fccaa690802181051r377afa2an33fb9e1a3a7b65ca@mail.gmail.com обсуждение исходный текст |
Ответ на | Getting "This ResultSet is closed" exceptions ("Paul Tomblin" <ptomblin@gmail.com>) |
Ответы |
Re: Getting "This ResultSet is closed" exceptions
|
Список | pgsql-jdbc |
Another thread my close the result set if it's using the same statement. Or the thread may close the connection, but i think that would throw another exception. Other wise your code look right On Feb 18, 2008 8:19 AM, Paul Tomblin <ptomblin@gmail.com> wrote: > I have some code that works most of the time, but I left it running > overnight and at 3am I got the "This ResultSet is closed" exception on > the "while (rs.next())" line in the following code: > > ResultSet rs = getPerformancesOnVenueStmt.executeQuery(); > > while(rs.next()) > { > Performance performance = parseResultSet(null, null, rs); > if (performance != null) > retList.add(performance); > } > rs.close(); > > The method "parseResultSet" does not close the result set, it just > does the various "rs.get..." calls and creates a Performance object. > > Is it possible that another thread doing a commit on the same > Connection could cause this? > > -- > For my assured failures and derelictions I ask pardon beforehand of my > betters and my equals in my Calling here assembled, praying that in > the hour of my temptations, weakness and weariness, the memory of this > my Obligation and of the company before whom it was entered into, may > return to me to aid, comfort and restrain. > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly >
В списке pgsql-jdbc по дате отправления: