Re: Getting "This ResultSet is closed" exceptions
От | Andres Olarte |
---|---|
Тема | Re: Getting "This ResultSet is closed" exceptions |
Дата | |
Msg-id | 3fccaa690802181110j4b5d1429ta8ea641f4ebb160@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Getting "This ResultSet is closed" exceptions ("Paul Tomblin" <ptomblin@gmail.com>) |
Ответы |
Re: Getting "This ResultSet is closed" exceptions
|
Список | pgsql-jdbc |
You might go for using a single connection per thread. Works for me. On Feb 18, 2008 12:59 PM, Paul Tomblin <ptomblin@gmail.com> wrote: > On Feb 18, 2008 1:51 PM, Andres Olarte <olarte.andres@gmail.com> wrote: > > 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 > > Well, no other method is using the same PreparedStatement. So I guess > it's likely that another thread is doing the same query, and that's > what's closing the ResultSet. I guess it's time to make some of these > methods synchronized. > > -- > 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 6: explain analyze is your friend >
В списке pgsql-jdbc по дате отправления: