I haven't looked at jaybird in years but if I were to guess I would
suspect that there's a jaybird connection pool of size 10 and a
glassfish pool of larger size that is trying to pool the jaybird
connections from the size-10 pool. After glassfish tries to set up
more than 10 connections it wouldn't be able to get any more. What I
used to expect was that in an app server you'd use the j2ca connector
and let the app server handle the pooling from there. What's the
current recommendation?

thanks
david jencks

On May 7, 2009, at 5:53 AM, Roman Rokytskyy wrote:

>
>
> > in PooledConnectionQueue, line 477
> >
> > boolean maximumCapacityReached =
> > getConfiguration().getMaxPoolSize() <= totalConnections &&
> > getConfiguration().getMaxPoolSize() != 0 &&
> > getConfiguration().isPooling();
> >
> > evaluates to true, because getConfiguration().getMaxPoolSize()
> returns 10,
> > regardless of what i configure in glassfishs admin console. any
> idea what i
> > could do to solve this?
>
> The value 10 is the default value of the maxPoolSize property.
>
> Do you really use 10 connections simultaneously? If that is the case,
> then the bug is somewhere in setting the maxPoolSize property...
>
> Maybe next week I will have some time to check the issues with pool in
> JBoss and Glassfish...
>
> Roman
>
>



[Non-text portions of this message have been removed]