1 Reply Latest reply on Aug 14, 2002 6:53 PM by Douglas Campbell

    connection pooling jboss 3.0

    Arijit Ghosh Newbie

      Hi,

      I am using Jboss 3.0 with Castor JDO. Struts -> Stateless Session
      Bean --> Castor JDO

      I am using container managed transaction and trying to impement
      connection pooling. I have included the oracle-service.xml file.
      Everytime I am connecting to the database, a new conneciton is being
      created. If I set the MaxSize to 3 then after 3 successful connections,
      it gives an error ---

      "No Managed Connection"

      Any suggestions ? Any other file that needs to be changed ?


      oracle-service.xml

      <?xml version="1.0" encoding="UTF-8"?>





      <depends optional-attribute-name="ManagedConnectionFactoryName">


      OracleDS



      <config-property name="ConnectionURL"
      type="java.lang.String">jdbc:oracle:thin:@192.168.0.124:2000:ORCL</config-property>

      <config-property name="DriverClass"
      type="java.lang.String">oracle.jdbc.driver.OracleDriver</config-property>

      <!--set these only if you want only default logins, not
      through JAAS -->
      <config-property name="UserName"
      type="java.lang.String">overseer2</config-property>
      <config-property name="Password"
      type="java.lang.String">overseer</config-property>




      <depends
      optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss
      LocalTransaction JDBC Wrapper




      <depends optional-attribute-name="ManagedConnectionPool">


      0
      3
      5000
      15
      ByContainer



      <depends

      optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager

      <depends

      optional-attribute-name="JaasSecurityManagerService">jboss.security:name=JaasSecurityManager

      java:/TransactionManager
      jboss.jca:service=RARDeployer




      jdo-service.xml

      <?xml version="1.0" encoding="UTF-8"?>




      file:./database.xml
      jdo/mydb
      0
      false
      false
      false
      true





      Thanks in advance.

        • 1. Re: connection pooling jboss 3.0
          Douglas Campbell Newbie

          apologies if this isn't your problem but.....

          The behaviour is by design. You set the max size to three and thus when you exceed that by not calling close on one or more of the connections prior to obtaining the 4th one, the container will wait your blocking interval and then throw an exception indicating that the pool is empty.

          hope this helps
          -doug