From: | Tim McAuley <mcauleyt(at)tcd(dot)ie> |
---|---|
To: | Barry Lind <blind(at)xythos(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Issues with calling stored prcedures |
Date: | 2003-08-27 10:33:33 |
Message-ID: | 3F4C88FD.3090405@tcd.ie |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
> I suspect the problem is that your stored procedures are generating
> notice messages to the client. These notice messages get queued up in
> the jdbc driver as warning objects. I bet if you called getWarnings()
> you would see all of the notice messages. That would be your 'memory
> leak'.
>
> In the current code these warnings are queued per statement object,
> but in older versions of the code they are queued per connection.
Barry,
You are a life saver. I only figured out last night that the stored
procedures seemed to be the weak link but didn't even think to look for
NOTICE messages. You are absolutely correct!
I have lowered the messages to debug level and also added a check for
sql warnings on the connection to warn of this in the future.
Many thanks!
Tim
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2003-08-27 12:14:55 | Re: DatabaseMetaData.get(Imi|Ex)portedKeys() and FK_NAME |
Previous Message | kevin | 2003-08-27 09:31:03 | Re: resultset.first() untrappable error |