there is a workaround for this problem. setting the pool parameters via
"additional properties" works. would be nice thou if the pool settings page in
the gf admin console could be used.
i was able to locate the glassfish code that sets the additional driver
properties, but not the code that passes the pool settings to the jdbc drivers
datasource implementation... so i have no idea yet, what method glassfish
tries to call to set the maximum pool size. i can live with the workaround
described above for now. when things slow down a bit here, i am going to
investigate glassfishs code a little further.
btw, a while ago i posted a fix to the sun specific
org.firebirdsq.sun.AppserverDataSource class to enable the setting of
"resultSetHoldable" property.. did this make it into the trunk yet? i am still
using my custom implementation here....

thanks for reading,
lutz

On Thursday 07 May 2009 23:54:58 David Jencks wrote:
> 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]