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
