2 Replies Latest reply on Jul 30, 2002 10:39 AM by Ian Hunter

    Connection releasing to pool

    Ian Hunter Newbie

      How folks,

      I'm 2.4.4 with MySQL (non-transactional) and everytime I close a connection I simply get the log message

      '[INFO,DefaultDS] No transaction right now.'

      which makes me think we're not putting connections back into the pool correctly.

      The root problem is that we're overloading the DB pool much too easily.

      I've placed the jboss.jcml section below. Can anybody please help with this, or is more info needed?

      Many Thanks
      Ian Hunter

      =============================================




      org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl


      DefaultDS
      [THE URL]

      [USER]
      [PWORD]

      true
      60000
      true
      30
      true
      30
      0
      true
      60000
      10000



        • 1. Re: Connection releasing to pool
          Sridhar J Newbie

          Hi,
          The connection is checked for any transaction wrt this Connection instance.
          The GCMInIdle 10000 (10 secs) time what is set is ok. can be increased to 20000.
          And u can set in the DB the no of the Connections allowed and in the jboss.jcml - MaxSize can be set to 75 %.

          set the IdleTimeout to 5000 ( 5 secs ) since the already set value is too less.

          • 2. Re: Connection releasing to pool
            Ian Hunter Newbie

            Many thanks for your reply.

            Thanks for the notes on config. values.

            When I put connections back into the pool, what messages should I see? How do I know that they are put back?

            If the connection is checked for transactions when using non-transactional databases, will it prevent the connection being released - or am I paranoid here?

            Many Thanks
            Ian Hunter