1 Reply Latest reply on Aug 10, 2005 5:16 PM by marioarias

    Problem whit many connections  DB in SQL Server 2000

    marioarias

      We have a set of applications and , each app connect with 3 different DB, two DB are shared for all app, and the others are only use for each app

      Example

      app db
      ------------------------------------
      XXXX att
      XXXX
      des
      -----------------------------------
      YYYY att
      YYYY
      des
      -----------------------------------
      ZZZZ att
      ZZZZ
      des

      If run only one app, all work nice, but when run many app's the Shared DB (att,des) work nice, but the others work randomly(some times update the db, sometimes not, but ever read nicely).

      This app's run over JBoss 4.0.2 whit MS SQL server 2000 (Microsoft's Driver).

      this is the mssql-ds.xml

      .....
      <local-tx-datasource>
      <jndi-name>des</jndi-name> <connection-url>jdbc:microsoft:sqlserver://PROGRAMACION\\DESARROLLO:1433;DatabaseName=des</connection-url> <driver-class>com.microsoft.jdbc.sqlserver.SQLServerDriver</driver-class>
      <user-name>sa</user-name>
      XXXX
      <prepared-statement-cache-size>50</prepared-statement-cache-size>
      <min-pool-size>5</min-pool-size>
      <max-pool-size>50</max-pool-size>
      <idle-timeout-minutes>15</idle-timeout-minutes>
      <track-statements>false</track-statements>

      <type-mapping>MS SQLSERVER2000</type-mapping>

      .... many other's here

      How we can do?

      Many thank's for your answers... and sorry for my english, I'm latin

        • 1. Re: Problem whit many connections  DB in SQL Server 2000
          marioarias

          The problem was very silly,
          the problem was in the ejb-jar.xml; some app's have the same configuration


          <ejb-name>XXX</ejb-name>
          com.m4minter..componentes.XXXHome
          com.m4minter..componentes.XXX
          <ejb-class>com.m4minter..componentes.XXXEJB</ejb-class>
          ..... more configuration here

          the solution was very simple, adding a package and changing the ejb-jar for every app