don't worry, the community is here to solve problems :)
Ciao ;)
Simo
On Fri, Jan 15, 2010 at 1:58 PM, Daniele Bonetto
wrote:
> i've found the problem.
> it was fixed in the latest release (1.5.4), but rebuilding the source
> eclipse doesn't change the lib in webapp (that remains 1.5.2).
>
> i con
i've found the problem.
it was fixed in the latest release (1.5.4), but rebuilding the source
eclipse doesn't change the lib in webapp (that remains 1.5.2).
i confirm that if borrowObject throws an exception the pool invalidates
the broken object, so is unnecessary invalidate the object in the
On 15/01/2010 12:07, Daniele Bonetto wrote:
> I've already the latest version... :(((
>
> Other suggestions??
Could be a pool bug. Could you provide some more detail about what your
obejct factory is doing when the network is down. Does it create
objects? Does it validate them?
Mark
>
> Daniel
I've already the latest version... :(((
Other suggestions??
Daniele
Il 15/01/2010 12.23, Mark Thomas ha scritto:
On 15/01/2010 10:59, Daniele Bonetto wrote:
yes, but if i don't invalidate the object i continue to have the problem
Timeout waiting for idle object
that blocks my pool as
It sounds invalidating the object doesn't afflict the pool status,
since in some cases you invalidate null. try following Mark
suggestions.
all the best,
Simo
On Fri, Jan 15, 2010 at 11:59 AM, Daniele Bonetto
wrote:
> yes, but if i don't invalidate the object i continue to have the problem
>
> Ti
On 15/01/2010 10:59, Daniele Bonetto wrote:
> yes, but if i don't invalidate the object i continue to have the problem
>
> Timeout waiting for idle object
>
> that blocks my pool as u can see in the following examples... :(
Which version of pool are you using? If not 1.5.4, try upgrading as
ther
yes, but if i don't invalidate the object i continue to have the problem
Timeout waiting for idle object
that blocks my pool as u can see in the following examples... :(
*/Example 1: without invalidateObject/*
MaxActive = 2
NumActive = 0
--> Network is ok.
Borrow obj1 --> ok [numActive 1]
Bo
In the example, the catch group catches exceptions that could be
thrown by the object _use_, I *suppose* whenever you catch a
java.util.NoSuchElementException you don't need to invalidate the
object, that's what Mark was pointing.
let us know, all the best,
Simo
On Fri, Jan 15, 2010 at 11:26 AM, D
Ok, if the borrow throws an exceptin the obj was null.
But i'm not sure that the invalidate was unnecessary. take a look at
this:
http://commons.apache.org/pool/apidocs/org/apache/commons/pool/ObjectPool.html
Example of use:
Object obj =|null|;
|try| {
obj = pool.borrowObject();