On 2001.09.24 19:02:02 -0400 Daniel Ferrante wrote:
> I assume that this means that I am creating and releasing a connection.
> However, I am not sure that's what this
> indicates. Can you verify that's what this indicates.
>
> [licensePool] Pool licensePool [46/46/Unlimited] gave out pooled object:
> org.opentools.minerva.jdbc.xa.wrapper.XAConnectionImpl@21d02f
> [licensePool] Pool licensePool [45/46/Unlimited] returned object
> org.opentools.minerva.jdbc.xa.wrapper.XAConnectionImpl@21d02f to the
> pool.
this one ("returned") was returned
>
> [licensePool] Pool licensePool [46/46/Unlimited] gave out pooled object:
> org.opentools.minerva.jdbc.xa.wrapper.XAConnectionImpl@21d02f
> [licensePool] Pool licensePool [45/45/Unlimited] destroyed object
> org.opentools.minerva.jdbc.xa.wrapper.XAConnectionImpl@21d02f.
>
this one ("destroyed") was not, something bad happened and the "physical"
db connection was hopefully closed before it was discarded. What went
wrong? Look in your server log -- as far as I know this shouldn't really
happen. You might be crashing connections and permanently using up db
server resources--just a guess.
Let me say it again, louder: PUT A REASONABLE MAXSIZE IN YOUR POOL!
If your app doesn't work well with a fairly small value proportional to the
load on your app, there is something wrong that you need to fix.
david jencks
> Thanks,
> Dan
>
> -----Original Message-----
> From: David Jencks [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 24, 2001 6:37 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] JBoss and MySql Problems
>
>
> Well, setting maxsize to 0 means no limit. Some db/driver combinations
> have a limit on the number of concurrent connections, at least from one
> ip
> address. Try setting maxsize rather small -- say 5 or 10 -- and verify
> you
> really are releasing connections.
>
> david jencks
>
> On 2001.09.24 18:00:22 -0400 Daniel Ferrante wrote:
> > Hi -
> > Below is my setup for a connection pool with mysql. I am using CMP
> with
> > JBoss and MySQL
> >
> > <mbean code="org.jboss.jdbc.XADataSourceLoader"
> > name="DefaultDomain:service=XADataSource,name=dbPool">
> > <attribute name="PoolName">dbPool</attribute>
> > <attribute
> >
> name="DataSourceClass">org.opentools.minerva.jdbc.xa.wrapper.XADataSourc
> > eImpl</attribute>
> > <attribute name="URL">jdbc:mysql:url</attribute>
> > <attribute name="JDBCUser">user</attribute>
> > <attribute name="Blocking">true</attribute>
> > <attribute name="MaxSize">0</attribute>
> > <attribute name="Password">pass</attribute>
> > <attribute name="LoggingEnabled">true</attribute>
> > </mbean>
> >
> > I am trying to debug why my application constantly dies (or hangs)
> after
> > 100 connections are created. I have made sure that I am closing all
> the
> > connections to the database in my code (that is anywhere I make a
> direct
> > connection to the database not using the entity beans).
> >
> > I understand since Blocking is set to true that it waits for a new
> > connection. Is this a problem with CMP, mySQL, or do you see anything
> > in the XADataSourceLoader.
> >
> > Thanks
> > Dan
> >
> > _______________________________________________
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-user
> >
> >
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
