In 3.0, I think this is a bug and that it used to work. Could I convince you to write a junit test for our testsuite demonstrating this problem using DefaultDS? Please have the test descend from JBossTestCase and put it in the org/jboss/test/jca/test directory/package. As long as it can get one more than the "maxSize" there is a problem.
I'm still thinking how to support dynamic resizing in the reimplementation of the pooling code I am working on. Thanks! david jencks On 2002.02.06 05:26:11 -0500 [EMAIL PROTECTED] wrote: > Surely you remember that I had any questions about dynamic reconfigurable > Connectionpools to Databases. I tried to increase the size of an > Database-Connection-Pool dynamically... > > First testing JBoss v2.4.3. Setting MaxSize=10 and blocking=false, so > there > were only 10 Connections possible. But changing this MaxSize Parameter > during > the pool is running wasn't possible for me... > > Then testing JBoss v3.0.0 (from the jboss-download side and then the > newest > versions from CVS). Using the Hypersonic Database and an extern Oracle > Database. In one test more than 8000 concurrent connections could be > established > until the error "java.lang.OutOfMemory (no stack trace availble)" > occured. > Really I set MaxSize=10 in the ConnectionManagerProperties: > > <mbean code="org.jboss.resource.ConnectionFactoryLoader" > name="JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Oracle"> > <attribute name="ManagedConnectionFactoryProperties"> > ConnectionURL=jdbc:oracle:thin... > DriverClass=oracle.jdbc.driver.OracleDriver > </attribute> > <attribute name="JndiName">Oracle</attribute> > <attribute > name="TransactionManagerName">java:/TransactionManager</attribute> > <mbean-ref name="ResourceAdapterName">JCA:service=RARDeployment,name=Minerva > JDBC LocalTransaction ResourceAdapter > </mbean-ref> > <mbean-ref > >name="ConnectionManagerFactoryLoaderName">JCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory > </mbean-ref> > <attribute name="ConnectionManagerProperties"> > BlockingTimeoutMillis=0 > IdleTimeoutMinutes=30 > MaxSize=10 > CleanupIntervalMinutes=10 > MinSize=0 > MaxIdleTimeoutPercent=1.0 > </attribute> > <attribute name="PrincipalMappingClass"> > org.jboss.resource.security.ManyToOnePrincipalMapping > </attribute> > <attribute name="PrincipalMappingProperties"> > userName=... > password=... > </attribute> > </mbean> > > > So I arrived at the conclusion, that there is (in Jboss 3.0.0) yet a > dynamic > Connectionpool !!! (Please correct me, if I'm wrong..) > > But I do not really understand, how it works. > > There is a Connectionpool with (e.g. 10 prepooled Connections) but this > isnt > the upper bound. If there isn't any available Connection in the pool, > then a > new physical Connection will be created. > or > Maybe there is no real Connectionpool and every requested Connection will > be > established (in the limits of the system and the internal > databasesettings) > > > Maybe anybody could explain it for me?? > > Thank you very much! > > -- > GMX - Die Kommunikationsplattform im Internet. > http://www.gmx.net > > > _______________________________________________ > 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
