proxool-developer

[Proxool-developer] #1 registered a statement as closed which wasn't known to be open.

[Prigozhin, R. <Rom...@ob...>]

Hi All,
	I'm new to the Proxool, I've been using it only for a month.
I'm getting message from proxool :  000001 (01/01/00) - #1 registered a =
statement as closed which wasn't known to be open.
I suspect that it happens when I'm closing PreparedStatement ( JDBC ) in =
finally block even if it was never open , I just check if it's not null =
and execute .close() statement just to be on the safe side.

Question :
	Is it ok ? or proxool will leak memory / connections etc ?
	How to avoid this message ?


Thanks,
Roman
###########################################=0A=
=0A=
This message has been scanned by F-Secure Anti-Virus for Microsoft =
Exchange.=0A=
For more information, connect to http://www.F-Secure.com/

Re: [Proxool-developer] #1 registered a statement as closed which wasn't known to be open.

[Bill H. <bi...@lo...>]

Hi Roman,

Prigozhin, Roman wrote:

> I'm getting message from proxool :  000001 (01/01/00) - #1 registered 
> a statement as closed which wasn't known to be open.
>
> I suspect that it happens when I'm closing PreparedStatement ( JDBC ) 
> in finally block even if it was never open , I just check if it's not 
> null and execute .close() statement just to be on the safe side.
>
> Question :
>         Is it ok ? or proxool will leak memory / connections etc ?
>
Yes, it's okay. It's exactly as you say: you're closing a statement 
twice. There's nothing wrong with that (according to the JDBC spec.).

>         How to avoid this message ?
>
Hmm, that would be tricky. I think maybe we should make Proxool be a 
little quieter in that respect. It's a bit over cautious. Now that bit 
of code is pretty mature we can be sure what is going on there. I'll see 
what I can do.

- Bill