4 Replies Latest reply on May 14, 2004 12:53 AM by juha

    connection pool and JCA

    yangju

      I have a question that confuses me. I am using JSQL database drivers. I defined a datasource in _ds.xml with a JSQL's jdbc driver without connection pooling. But appearantly, JBoss provides the connection pool. So, does JBoss uses its own connection pool regardless if the underlying datasource's jdbc driver has connection pool or not?
      The same thing for XA. If the driver does not support XA, can JBoss's JTA manager still support XA?

      How does JBoss's connection pool and JCA work with the underlying database driver?

      Thanks.

        • 1. Re: connection pool and JCA
          darranl

          You need to configure JBoss to use its own connection pool.

          See Chapter 8 of the getting started guide.

          • 2. Re: connection pool and JCA

            Or read the WIKI

            J2EE has special pooling requirements that the xadatasource or jdbc driver
            will not understand.

            • 3. Re: connection pool and JCA
              yangju

              Thanks. I am sorry but after I read chap.8 of the get started guide again and wiki page, I still have got the point. I think I know how to config the -ds.xml. What I was asking is:
              Jboss does not care if the driver that is provided in datasource can do pooling or XA, JBoss just simply wrap this driver up and use JBoss's own connection pooling mechanism and XA? Therefore I should only need provide a basic jdbc driver without any pooling capability for the datasource?

              If this is true, what if I provide a XA-compliant driver? Does it have any difference to JBoss?

              Thanks again.

              • 4. Re: connection pool and JCA

                You will still want an XA driver for the database to correctly participate in two phase commit protocol. JBoss won't be able to do that if the driver does not support it.