Re: Do we need to manually close SQLProcesser?

t, Scott. > org.ofbiz.entity.connection.DBCPConnectionFactory tells me. > > > -Original Message- > From: Scott Gray [mailto:scott.g...@hotwaxmedia.com] > Sent: 2009年9月14日 11:02 > To: user@ofbiz.apache.org > Subject: Re: Do we need to manually close SQLProcesser? > > java.sql.Connection

RE: Do we need to manually close SQLProcesser?

Yes, you're right, Scott. org.ofbiz.entity.connection.DBCPConnectionFactory tells me. -Original Message- From: Scott Gray [mailto:scott.g...@hotwaxmedia.com] Sent: 2009年9月14日 11:02 To: user@ofbiz.apache.org Subject: Re: Do we need to manually close SQLProcesser? java.sql.Connecti

Re: Do we need to manually close SQLProcesser?

PoolableConnection. -Original Message- From: Scott Gray [mailto:scott.g...@hotwaxmedia.com] Sent: 2009年9月14日 10:44 To: user@ofbiz.apache.org Subject: Re: Do we need to manually close SQLProcesser? No the connection implementation is a PoolableConnection and closing it returns it to the

RE: Do we need to manually close SQLProcesser?

gt; > -Original Message----- > From: Larry.Liu [mailto:xiangqian@wizitsoft.com] > Sent: 2009年9月14日 9:45 > To: user@ofbiz.apache.org > Subject: Re: Do we need to manually close SQLProcesser? > > Hi Gray, > > Thanks for your help, > > S

Re: Do we need to manually close SQLProcesser?

f you close it by yourself, the pool will be run out. -Original Message- From: Larry.Liu [mailto:xiangqian@wizitsoft.com] Sent: 2009年9月14日 9:45 To: user@ofbiz.apache.org Subject: Re: Do we need to manually close SQLProcesser? Hi Gray, Thanks for your help, So according to my und

RE: Do we need to manually close SQLProcesser?

qian@wizitsoft.com] Sent: 2009年9月14日 9:45 To: user@ofbiz.apache.org Subject: Re: Do we need to manually close SQLProcesser? Hi Gray, Thanks for your help, So according to my understanding, trying to close the SQLProcessor will cause available connection in the pool fewer and fewer

Re: Do we need to manually close SQLProcesser?

Hi Gray, Thanks for your help, So according to my understanding, trying to close the SQLProcessor will cause available connection in the pool fewer and fewer and there will be "No ManagedConnections Available!" exception in the end, isn't it? Now we have a B2C website running on ofbiz, using Dat

Re: Do we need to manually close SQLProcesser?

This also sounds like the kind of thing that should be in a finally block in order to guarantee the close will execute even after an exception. org.ofbiz.core.entity.jdbc.SQLProcessor sqlProcessor = null; try { sqlProcessor = new org.ofbiz.core.entity.jdbc.SQLProcessor( /*datasource*/ ); s

Re: Do we need to manually close SQLProcesser?

Hi Liu, 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. Regards Scott HotWax Media http://www.hotwaxmedia.com On 11/09/2009, at 2:44 PM, Larry.Liu wr

Do we need to manually close SQLProcesser?

Hi, We have created SQLProcessor in our code manually and also invoke process.close() after execute the sql query or update, and we are assumpting this caused error of No ManagedConnections Available I have looked into the file EntitySQLProcessor.bsh, that's the file for webtools module SQL Pr