Thanks David-
You're right, I am using the XADataSourceLoader...Below
<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">10</attribute>
<attribute name="Password">pass</attribute>
<attribute name="LoggingEnabled">true</attribute>
</mbean>
I went back through my code and did find a connection leak after sending
the previous message.
Thanks again for the advice,
Dan
-----Original Message-----
From: David Jencks [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 21, 2001 9:18 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Connection Pool Problems with JBoss
Are you sure you showed the right piece of configuration? what you show
is
from a ConnectionFactoryLoader configuration, which is extremely
inconvenient to use in 2.2.2 - each time you start jboss, you have to
deploy by hand or program a resource adapter (rar). Is it possible that
you are actually using an XADatatSourceLoader with blocking = false?
One popular way to use up all the connections and break the pool is to
use
BMP and hold onto a connection over a transaction boundary, for instance
by
caching the connection between activation and passivation. Proper use
of
connections in jboss is like this:
(something starts the transaction, either the container or you)
(get the DataSource ds)
Connection c = ds.getConnection();
try {
do something and close all the resources you use.
}
finally{
c.close();
}
(transaction ends, either by container or by your code)
sun has many examples of holding onto connections, well, forever,
however
this is inconsistent with their explanation of how pooling works.
Hope this helps
david jencks
On 2001.09.21 17:41:23 -0400 Daniel Ferrante wrote:
> Hi All -
> I am using JBoss 2.2.2 with Tomcat. We are using minerva database
> connection pools and are having problems with
> connections returning null. The main problem is that once the null
> connection object is returned and the exception is caught, we need
> to restart JBoss, the connection pool dies and doesn't give out
anymore
> connections. I debated setting the MaxSize variable to 0 (constantly
> growing the PoolSize).
>
> Any help you can give to me in understanding how to approach this
> problem would be greatly appreciated.
>
> I used the default MaxSize of Connections to 10 (See Below),
>
> <attribute name="ConnectionManagerProperties">
> # Pool type - uncomment to force, otherwise it is the default
> #PoolConfiguration=per-factory
>
> # Connection pooling properties - see
> # org.opentools.minerva.pool.PoolParameters
> MinSize=0
> MaxSize=10
> Blocking=true
> GCEnabled=false
> IdleTimeoutEnabled=false
> InvalidateOnError=false
> TrackLastUsed=false
> GCIntervalMillis=120000
> GCMinIdleMillis=1200000
> IdleTimeoutMillis=1800000
> MaxIdleTimeoutPercent=1.0
> </attribute>
>
> 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
