Re: Empty resultset returned by JDBC Connection
Then it looks like caching issues.
You could try writing the Statement/ResultSet object references to the log to see if you are re-using objects that you already swept.
I also recommend you to be very careful with calling the close() method in your Statement and Connection objects, everywhere. This is particularly important when using connection pools.
It could be also some issue on the server or something else already reported on the client. Have you checked your server logs and application server logs?
Subject
Written By
Posted
Re: Empty resultset returned by JDBC Connection
May 04, 2020 04:45PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.