ObjectPoolHelper should use WHEN_EXHAUSTED_GROW policy

[GoogleCodeExporter]

I'm using the wro4j at runtime and having troubles with the ObjectPoolHelper 
class. I'm processing css with LessCss post-processor and getting a 
NoSuchElementException from commons-pool.
java.lang.RuntimeException: Cannot get object from the pool
    at ro.isdc.wro.extensions.processor.support.ObjectPoolHelper.getObject(ObjectPoolHelper.java:50) ~[wro4j-extensions-1.4.3.jar:1.4.3]
    at ro.isdc.wro.extensions.processor.css.LessCssProcessor.getEngine(LessCssProcessor.java:162) ~[wro4j-extensions-1.4.3.jar:1.4.3]
    at ro.isdc.wro.extensions.processor.css.LessCssProcessor.process(LessCssProcessor.java:129) ~[wro4j-extensions-1.4.3.jar:1.4.3]
    at ro.isdc.wro.extensions.processor.css.LessCssProcessor.process(LessCssProcessor.java:180) ~[wro4j-extensions-1.4.3.jar:1.4.3]
Caused by: java.util.NoSuchElementException: Timeout waiting for idle object
    at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1167) ~[commons-pool-1.5.6.jar:1.5.6]
    at ro.isdc.wro.extensions.processor.support.ObjectPoolHelper.getObject(ObjectPoolHelper.java:47) ~[wro4j-extensions-1.4.3.jar:1.4.3]

Our app in dev ask wro4j for 6 css files and 3 of them fail with the 
NSEException. I tried by changing the when_exhausted policy to "GROW" or 
increasing the timeout and everything works just fine.

what is your opinion on using the WHEN_EXHAUSTED_GROW policy or increase the 
timeout?

Original issue reported on code.google.com by alex.obj...@gmail.com on 31 Jan 2012 at 12:32

[GoogleCodeExporter]

Original comment by alex.obj...@gmail.com on 1 Feb 2012 at 10:06

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by alex.obj...@gmail.com on 12 Feb 2012 at 10:55

• Changed title: ObjectPoolHelper should use WHEN_EXHAUSTED_GROW policy