[opencms-dev] Cannot get a connection, pool error: Timeout waiting for idle object

[Mario Jäger]

Hi Kumar,

Do you still get the error: Cannot get a connection, 
pool error: Timeout waiting for idle object?

-- 
Kind Regards,
Mario.
 
-------------------
Mario Jäger
 
Alkacon Software GmbH  - The OpenCms Experts                    
http://www.alkacon.com - http://www.opencms.org      


Kumar Annamalai schrieb:
> Hi Mario,
>
> I implemented the changes which you have mentioned, but the pool size keep
> on increasing.
> I guess this will be a problem in the long run.
>
> And i also have a question, whether this is a bug in OpenCms, this basically
> occurs at occasions when it is not able handle certain files. 
>
> It seems the connection is not closed, so succesive unclosed connections
> cause all the objects in the pool to expire, and there will be no object to
> share.
>
> So timing is geting out, waiting for an idle object.
>
> Is there some other way other than this?
>
> Kindly help me.
>
> Regards,
> A.K
>
>
> Kumar Annamalai wrote:
>   
>> Ji Mario,
>>
>> This is wonderful, what an instant reply from the OpenCms forum.
>>
>> Thanks mario, i will change this immediately, will check and will let you
>> know.
>>
>> Since this issue, occurs in weekly basis, i will wait for the result and
>> will get back to you.
>>
>> Thanks for your time.
>>
>>
>> Mario Jäger wrote:
>>     
>>> Hi Kumar,
>>>
>>> please change in the opencms.properties file the line in section 
>>> #action to take when the pool is exhausted {grow|block|fail}
>>>
>>> from:
>>> db.pool.default.whenExhaustedAction=block
>>>
>>> to:
>>> db.pool.default.whenExhaustedAction=grow
>>>
>>>
>>> So endless loops are prevented.
>>>
>>> -- 
>>> Kind Regards,
>>> Mario.
>>>  
>>> -------------------
>>> Mario Jäger
>>>  
>>> Alkacon Software GmbH  - The OpenCms Experts                    
>>> http://www.alkacon.com - http://www.opencms.org           
>>>
>>>
>>>
>>> Kumar Annamalai schrieb:
>>>       
>>>> Hi All, I am facing this issue in my OpenCms servers, once in every 
>>>> week. In that case, restarting the server is the only option, and the 
>>>> issue will be fixed. More details here, Tomcat 5.x, MySQL,OpenCms 7.x 
>>>> I have attached the Opencms.properties 
>>>> <http://old.nabble.com/file/p26262970/Opencms.properties> file, and a 
>>>> brief overview below, # the maximum number of objects that can be 
>>>> borrowed from the pool db.pool.default.maxActive=25 # the maximum 
>>>> amount of time before throwing an exception when the pool is exhausted 
>>>> db.pool.default.maxWait=2000 # the minimum number of objects that will 
>>>> kept connected db.pool.default.minIdle=3 # the maximum number of 
>>>> objects that can sit idled in the pool db.pool.default.maxIdle=10 # 
>>>> action to take when the pool is exhausted {grow|block|fail} 
>>>> db.pool.default.whenExhaustedAction=block # connections will be 
>>>> validated before they are borrowed from the pool 
>>>> db.pool.default.testOnBorrow=false # connections will be validated by 
>>>> evictor thread db.pool.default.testWhileIdle=true # number of 
>>>> milliseconds to sleep between runs of the evictor thread # -1 means no 
>>>> idle connection evictor thread will be run 
>>>> db.pool.default.timeBetweenEvictionRuns=3600000 # number of 
>>>> connections tested in a run of the evictor thread 
>>>> db.pool.default.numTestsPerEvictionRun=3 # minimum amount of time in 
>>>> milliseconds a connection may be idle in the pool before it is 
>>>> eligable for eviction db.pool.default.minEvictableIdleTime=1800000 # 
>>>> the query to validate connections #db.pool.default.testQuery=SELECT 
>>>> STRUCTURE_ID FROM CMS_OFFLINE_STRUCTURE WHERE RESOURCE_PATH = '/' 
>>>> db.pool.default.testQuery=SELECT 1 # number of attempts to connect to 
>>>> the database during startup (default = 10) db.pool.default.connects=10 
>>>> # sleep time between two attempts to connect to the database during 
>>>> startup in ms (default = 5000) db.pool.default.wait=5000 # # 
>>>> Configuration for statement pooling 
>>>> ################################################################################# 
>>>> db.statements.default.pooling=true db.statements.default.maxActive=200 
>>>> db.statements.default.maxWait=2000 db.statements.default.maxIdle=100 
>>>> db.statements.default.whenExhaustedAction=block Kindly help me in 
>>>> resolving this issue.
>>>> View this message in context: Cannot get a connection, pool error: 
>>>> Timeout waiting for idle object 
>>>> <http://old.nabble.com/Cannot-get-a-connection%2C-pool-error%3A-Timeout-waiting-for-idle-object-tp26262970p26262970.html>
>>>> Sent from the OpenCMS - Dev mailing list archive 
>>>> <http://old.nabble.com/OpenCMS---Dev-f654.html> at Nabble.com.
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>> _______________________________________________
>>>> This mail is sent to you from the opencms-dev mailing list
>>>> To change your list options, or to unsubscribe from the list, please
>>>> visit
>>>> http://lists.opencms.org/mailman/listinfo/opencms-dev
>>>>         
>>>       
>>>
>>>
>>> _______________________________________________
>>> This mail is sent to you from the opencms-dev mailing list
>>> To change your list options, or to unsubscribe from the list, please
>>> visit
>>> http://lists.opencms.org/mailman/listinfo/opencms-dev
>>>
>>>
>>>       
>>     
>
>