Re: Derby Error Starting Glassfish

OpenXGroup Inc. wrote:

You could also follow up on Manfred's suggestion and determine if this bug
was addressed by Derby as I think there was a bug logged in the past.  Also,
you can test with MySQL if possible and compare results using the
logging/debugging techniques suggested in the forum.

On Fri, May 1, 2009 at 10:59 AM, jsexton0 <jsexton0@gmail.com> wrote:

>
> Hello -
>
> This is interesting...
> This error is happening on the Derby database, very early in Glassfish's
> startup.  I am not (directly) using the Derby database in any of my code.
> Are you suggesting a change to Glassfish's default setup for its Derby
> pool?
> I can certainly try that...
>
> Thanks
>
>
> OpenXGroup Inc. wrote:
> >
> > Take a look at wrong XA state as well...
> >
> > Can you change javax.sql.ConnectionPoolDataSource to
> javax.sql.DataSource?
> > Or use XA datasource altogether?
> > I increased the "Initial and Minimum Pool Size" from 32 (default) to 64.
> > The
> > error vanished, but I don't know if it just depends on how many times per
> > timer event a connection is requested. May be the error will occure again
> > with more connection requests. Do you now what the maximal possible value
> > is
> > for the Initial and Minimum Pool Size? The value of 128 seemed not to be
> > accepted.
> >
> > I was able to resolve my problem by changing the resource type to
> > java.sql.ConnectionPoolDataSource.
> >
> > Do you need transactional capability. If not, you can set your pool to
> > return non-transactional-connections.
> >
> > Set non-transactional-connections="true" in your <jdbc-connection-pool>
> > configuration.
> >
> > There are two type of transactions we can talk about in general
> > (pertaining
> > to this thread).
> >
> > 1) There is the transaction that you can write using SQL which you (the
> > programmer) write yourself.
> > 2) There is the transaction that java handles at a system level which can
> > apply to any operation or series of operations you require to be
> performed
> > from beginning to end without error (including database operations).
> >
> > By setting non-transactional-connections to true you will not get the
> > protection from system failure as described in number 2.
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Derby-Error-Starting-Glassfish-tp23334048p23334482.html
> Sent from the NetBeans - EntPack mailing list archive at Nabble.com.
>
>