2 Replies Latest reply on Sep 22, 2006 2:33 AM by O?uz Da?

    InUseConnectionCount continously increasing...

    O?uz Da? Newbie


      I am watching one of my connection pool (most used) using JMX-Console for a while... Eveything goes fine except InUseConnectionCount is increasing nearly by 1 per hour...

      I know it should be increased and decreased according to the usage of system... I can see that movement... But per hour the lower limit of InUseConnectionCount is increasing by 1... I mean graph goes upper and upper slowly (imagine x-axis time, y-axis InUseConnectionCount)... It should not be normal...

      Can Quartz cause this problem? coz I am using Quartz for my batch jobs... Can I see the details of this connections?

      Thank you...

        • 1. Re: InUseConnectionCount continously increasing...
          Weston M. Price Master

          JBoss version?
          DB version?
          *-ds.xml file?
          log files/traces?

          • 2. Re: InUseConnectionCount continously increasing...
            O?uz Da? Newbie

            JBoss version : JBoss 4.0.3
            DB Version : Oracle 10g

            Datasource :

            <xa-datasource-property name="URL">jdbc:oracle:thin:@[IP]:[SID]</xa-datasource-property>
            <!-- Uses the pingDatabase method to check a connection is still valid before handing it out from the pool -->
            <!-- Checks the Oracle error codes and messages for fatal errors -->
            <!-- Oracles XA datasource cannot reuse a connection outside a transaction once enlisted in a global transaction and vice-versa -->

            <!-- this will be run before a managed connection is removed from the pool for use by a client-->
            <check-valid-connection-sql>select * from DUAL</check-valid-connection-sql>

            <!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use -->

            <!-- The maximum connections in a pool/sub-pool -->

            <!-- Use the security domain defined in conf/login-config.xml -->

            <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->



            There is no log file for this case, I was just watching the mbean...