0 Replies Latest reply on Jan 24, 2002 12:16 PM by sjus00

    still with databasepool problems

    sjus00

      Ok, a few days ago I posted a question about managing the size of databasepools ( with JBoss 2.4.3). My Tests for it doesn't work...

      Now I'm using JBoss 3.0.0. In the default-configuration there is the Hypersonic database "default", which I think is managed by JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=DefaultDS.

      ConnectionManagerFactoryLoaderName JCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory

      ConnectionManagerProperties
      #
      #Wed Aug 15 16:17:29 EDT 2001
      MinSize=0
      MaxSize=3
      BlockingTimeoutMillis=5000
      IdleTimeoutMinutes=30
      CleanupIntervalMinutes=10
      MaxIdleTimeoutPercent=1.0
      JndiName: DefaultDS
      ManagedConnectionFactoryProperties
      ConnectionURL=jdbc:hsqldb:hsql://localhost:1476
      DriverClass=org.hsqldb.jdbcDriver
      UserName=sa
      Name: ConnectionFactoryLoader
      PrincipalMappingClass
      PrincipalMappingProperties
      ResourceAdapterName
      ResourceAdapterName
      State 3
      StateString Started
      TransactionManagerName java:/TransactionManager


      In this MBean I found:
      ConnectionManagerProperties
      and there you can set the MaxSize.
      (In the actual Docu is written: MaxSize. The maximum number of managed connections in the pool. Requests beyond this will block => so I think only "MaxSize" Connections could be established to the database).

      So I tested, whether Database-Connections will be blocked, if the number of connections equals the MaxSize-number. I set MaxSize to 3, but I could open 11 (and more...) concurrent DatabaseConnections (which wrote something to an existing table => I found the validation of this writing in the file /db/default.script)

      Is there something wrong?
      Thank you!