RE: Relationship between JDBC Connections, Statements, ResultSets and open data paths

> It could possibly be that you're allowing garbage collection to take
care of open Statement objects instead
> of the application closing them (although that seems sort of unlikely
as I wouldn't necessarily expect to
> run unless you're memory constrained).


> Its hard to tell if those are psuedo-closed cursors or fully opened
cursors. If they are psuedo-closed cursors, I'm not quite
> sure why they would wax and wain like that. If they're open, perhaps
your application model fits having many of those
> queries 'in flight' at the same time?

Our application is sort of 'real-time' system working with tens of
mobile terminals. Terminals query our application and submit information
to it, while the application queries and/or updates the database. I'm
not sure what do you mean under 'being in fight', but yes, there might
be a couple of same (or different) queries against the same table in the
same time. By the way, we use journaling (transactions) everywhere.

> There are some QAQQINI settings that can control the number of
psuedo-closed
> cursors and how they grow that could help you diagnose too.
> As an information gathering tool, I might also create a small stored
procedure that retrieves the current number of open
> cursors for the job, and call it intermittently and see if you can get
a mental 'map' of how the number of open cursors in the
> backend relates to what your application is doing.
> If anyone wants some example code, I've got a little utility I run in
qshell that I've used for some monitoring similar to this (but > from
outside the job) that could be modified to get put into a stored
procedure.

Yes, please.
Any relevant code snippets, settings, etc. are welcome.

Regards,
Timur