1 Reply Latest reply on Apr 5, 2003 1:23 PM by deepak3000

    Running out of connections

    deepak3000 Newbie

      Hi,

      I am performing scalability tests for my project where a huge number of simultaneous inserts/updates happen. The total number of records considering all the tables together are more than a million records. Though all the these records are not simultaneously being updated/inserted. I set the connection pool size to 500 and I still get errors related to running out of connections. Below is a stack trace.

      2003-04-04 23:21:44,821 INFO [org.jboss.resource.connectionmanager.LocalTxConnectionManager$LocalConnectionEventListener] Could not enlist XAResource!

      javax.transaction.RollbackException: Already marked for rollback

      at org.jboss.tm.TxCapsule.enlistResource(TxCapsule.java:670)

      at org.jboss.tm.TransactionImpl.enlistResource(TransactionImpl.java:102)

      at org.jboss.resource.connectionmanager.LocalTxConnectionManager$LocalConnectionEventListener.enlist(LocalTxConnectionManager.java:320)

      at org.jboss.resource.connectionmanager.LocalTxConnectionManager.managedConnectionReconnected(LocalTxConnectionManager.java:255)

      at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:534)

      at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:822)

      at org.jboss.resource.adapter.jdbc.local.LocalDataSource.getConnection(LocalDataSource.java:102)


      This is turining out to be a show stopper. Any way of getting out of this?

      regards
      Naveen

        • 1. Re: Running out of connections
          deepak3000 Newbie

          I wrote some multi threaded test programs to access
          a whole lot of connections on the server side and jboss
          didn't give any errors. While going through the jboss source code according to the stack trace, I noticed that I got this error because of an earlier transaction time out. I guess I will have to play around with the transaction attributes to fix this.