Re: Do we need to manually close SQLProcesser?

[Scott Gray]

Hi Liu,




Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

On 11/09/2009, at 2:44 PM, Larry.Liu wrote:

Yes you should call close() on the SQLProcessor and no closing the connection will not prevent it from being returned to the pool. Whether it will solve your problem or not I don't know.

Hi,

We have created SQLProcessor in our code manually and also invoke

process.close()


error of

No ManagedConnections Available


webtools module SQL Processor page, I didn't see any closure of the
SQLProcessor.

So here are two questions,

1. Do we need to manually close the SQLProcessor?


and fewer?

Thanks.

Regards,
Liu Xiangqian

Wizitsoft Information Technology Ltd.
www.wizitsoft.com | (86) 010-62670653 ext 614

after execute the sql query or update, and we are assumpting this caused I have looked into the file EntitySQLProcessor.bsh, that's the file for 2. Close one SQLProcessor instance will cause the connection attached to this process being closed and make available connections in the pool fewer

smime.p7s
Description: S/MIME cryptographic signature