13 Replies Latest reply on Jan 24, 2012 9:56 AM by Scott Marlow

    TransactionReaper - timeout problem

    prinzm Newbie

      Hi!

       

      We have a web-project deployed on JBoss AS 7.1 Beta 1. Unfortunately from time to time we get the following warnings:

       

      15:14:17,369 WARN  [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA12117: TransactionReaper::check timeout for TX 0:ffff7f000001:-1a36cbee:4ee73908:6450 in state  RUN

      15:14:17,371 WARN  [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA12095: Abort of action id 0:ffff7f000001:-1a36cbee:4ee73908:6450 invoked while multiple threads active within it.

      15:14:17,371 WARN  [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA12108: CheckedAction::check - atomic action 0:ffff7f000001:-1a36cbee:4ee73908:6450 aborting with 1 threads active!

      15:14:17,371 WARN  [com.arjuna.ats.jta] (Transaction Reaper Worker 0) ARJUNA16029: SynchronizationImple.afterCompletion - failed for org.jboss.as.jpa.transaction.TransactionUtil$SessionSynchronization@12ba9d4 with exception: java.lang.Il

      legalStateException

              at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple.getTransactionImple(TransactionSynchronizationRegistryImple.java:225) [jbossjts-4.15.3.Final.jar:]

              at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple.putResource(TransactionSynchronizationRegistryImple.java:103) [jbossjts-4.15.3.Final.jar:]

              at org.jboss.as.jpa.transaction.TransactionUtil.putEntityManagerInTransactionRegistry(TransactionUtil.java:196)

              at org.jboss.as.jpa.transaction.TransactionUtil.access$100(TransactionUtil.java:49)

              at org.jboss.as.jpa.transaction.TransactionUtil$SessionSynchronization.afterCompletion(TransactionUtil.java:221)

              at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:117) [jbossjts-4.15.3.Final.jar:]

              at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:403) [jbossjts-4.15.3.Final.jar:]

              at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:335) [jbossjts-4.15.3.Final.jar:]

              at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:121) [jbossjts-4.15.3.Final.jar:]

              at com.arjuna.ats.arjuna.AtomicAction.cancel(AtomicAction.java:212) [jbossjts-4.15.3.Final.jar:]

              at com.arjuna.ats.arjuna.coordinator.TransactionReaper.doCancellations(TransactionReaper.java:367) [jbossjts-4.15.3.Final.jar:]

              at com.arjuna.ats.internal.arjuna.coordinator.ReaperWorkerThread.run(ReaperWorkerThread.java:79) [jbossjts-4.15.3.Final.jar:]

       

      15:14:17,373 WARN  [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA12127: TwoPhaseCoordinator.afterCompletion - returned failure for SynchronizationImple< 0:ffff7f000001:-1a36cbee:4ee73908:6451, org.jboss.as.jpa.transaction.T

      ransactionUtil$SessionSynchronization@12ba9d4 >

      15:14:17,373 WARN  [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA12121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffff7f000001:-1a36cbee:4ee73908:6450

       

      Is it too soon to use AS 7.1 Beta 1 or does this problem come from our code? Is there any configuration to prevent this?

       

      Thank you!

        • 1. Re: TransactionReaper - timeout problem
          prinzm Newbie

          I don't know if it has something to do with this problem, but we also get sometimes the following exception:

           

          15:25:41,295 WARN  [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-10.99.0.10-10.99.0.10-8080-17) SQL Error: 0, SQLState: null

          15:25:41,295 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (http-10.99.0.10-10.99.0.10-8080-17) javax.resource.ResourceException: Error checking for a transaction

          15:25:41,295 INFO  [org.hibernate.event.internal.DefaultLoadEventListener] (http-10.99.0.10-10.99.0.10-8080-17) HHH000327: Error performing load command : org.hibernate.exception.GenericJDBCException: Could not open connection

          15:25:41,296 WARN  [com.arjuna.ats.arjuna] (http-10.99.0.10-10.99.0.10-8080-17) ARJUNA12077: Abort called on already aborted atomic action 0:ffff7f000001:-1a36cbee:4ee73908:6450

          15:25:41,297 ERROR [com.hji.compound.service.stock.VehicleExitBean] (http-10.99.0.10-10.99.0.10-8080-17) SaveSelectedOrderPosition failed!: com.hji.exceptions.UserTransactionSupportException: UserTransactionSupport-Error: commit failed!

                  at com.hji.common.utils.UserTransactionSupport.run(UserTransactionSupport.java:40) [green-ejb.jar:]

                  at com.hji.compound.service.stock.VehicleExitBean.saveSelectedOrderPosition(VehicleExitBean.java:184) [green-ejb.jar:]

                  at sun.reflect.GeneratedMethodAccessor1196.invoke(Unknown Source) [:1.6.0_23]

                  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_23]

                  at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_23]

                  at org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72) [jboss-as-ee-7.1.0.Beta1.jar:]

                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:374) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:122) [jboss-as-weld-7.1.0.Beta1.jar:]

                  at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:130) [jboss-as-weld-7.1.0.Beta1.jar:]

                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:45) [jboss-as-jpa-7.1.0.Beta1.jar:]

                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation(StatefulSessionSynchronizationInterceptor.java:127) [jboss-as-ejb3-7.1.0.Beta1.jar:]

                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.as.ejb3.tx.StatefulBMTInterceptor.handleInvocation(StatefulBMTInterceptor.java:102) [jboss-as-ejb3-7.1.0.Beta1.jar:]

                  at org.jboss.as.ejb3.tx.BMTInterceptor.processInvocation(BMTInterceptor.java:56) [jboss-as-ejb3-7.1.0.Beta1.jar:]

                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.0.Beta1.jar:]

                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-7.1.0.Beta1.jar:]

                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.as.jpa.interceptor.SFSBInvocationInterceptor.processInvocation(SFSBInvocationInterceptor.java:60) [jboss-as-jpa-7.1.0.Beta1.jar:]

                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:76) [jboss-as-ejb3-7.1.0.Beta1.jar:]

                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.1.0.Beta1.jar:]

                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:]

                  at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:44) [jboss-as-ee-7.1.0.Beta1.jar:]

          ...

          Caused by: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Could not open connection

                  at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1353) [hibernate-entitymanager-4.0.0.CR6.jar:]

                  at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:810) [hibernate-entitymanager-4.0.0.CR6.jar:]

                  at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:764) [hibernate-entitymanager-4.0.0.CR6.jar:]

                  at org.jboss.as.jpa.container.AbstractEntityManager.find(AbstractEntityManager.java:219) [jboss-as-jpa-7.1.0.Beta1.jar:]

                  at com.hji.entity.Entity.exists(Entity.java:45) [green-ejb.jar:]

                  at com.hji.entity.Entity.save(Entity.java:91) [green-ejb.jar:]

                  at com.hji.entity.Entity.save(Entity.java:60) [green-ejb.jar:]

                  at com.hji.compound.service.stock.VehicleExitBean$1.run(VehicleExitBean.java:190) [green-ejb.jar:]

                  at com.hji.common.utils.UserTransactionSupport.run(UserTransactionSupport.java:31) [green-ejb.jar:]

                  ... 95 more

          Caused by: org.hibernate.exception.GenericJDBCException: Could not open connection

                  at org.hibernate.exception.internal.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:148) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.exception.internal.SQLStateConverter.convert(SQLStateConverter.java:136) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:125) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:110) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.obtainConnection(LogicalConnectionImpl.java:306) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.getConnection(LogicalConnectionImpl.java:169) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.engine.jdbc.internal.proxy.ConnectionProxyHandler.extractPhysicalConnection(ConnectionProxyHandler.java:82) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.engine.jdbc.internal.proxy.ConnectionProxyHandler.continueInvocation(ConnectionProxyHandler.java:138) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.engine.jdbc.internal.proxy.AbstractProxyHandler.invoke(AbstractProxyHandler.java:81) [hibernate-core-4.0.0.CR6.jar:]

                  at $Proxy98.prepareStatement(Unknown Source)    at org.hibernate.engine.jdbc.internal.StatementPreparerImpl$5.doPrepare(StatementPreparerImpl.java:149) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.engine.jdbc.internal.StatementPreparerImpl$StatementPreparationTemplate.prepareStatement(StatementPreparerImpl.java:178) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.engine.jdbc.internal.StatementPreparerImpl.prepareQueryStatement(StatementPreparerImpl.java:147) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1739) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.loader.Loader.doQuery(Loader.java:828) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:289) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.loader.Loader.loadEntity(Loader.java:2058) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:82) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:72) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3697) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.event.internal.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:439) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.event.internal.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:420) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.event.internal.DefaultLoadEventListener.load(DefaultLoadEventListener.java:204) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.event.internal.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:251) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.event.internal.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:148) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.ejb.DelegatingLoadEventListener.onLoad(DelegatingLoadEventListener.java:24) [hibernate-entitymanager-4.0.0.CR6.jar:]

                  at org.hibernate.internal.SessionImpl.fireLoad(SessionImpl.java:956) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.internal.SessionImpl.get(SessionImpl.java:872) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.internal.SessionImpl.get(SessionImpl.java:865) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:789) [hibernate-entitymanager-4.0.0.CR6.jar:]

                  ... 102 more

          Caused by: java.sql.SQLException: javax.resource.ResourceException: Error checking for a transaction

                  at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:137)

                  at org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider.getConnection(InjectedDataSourceConnectionProvider.java:67) [hibernate-entitymanager-4.0.0.CR6.jar:]

                  at org.hibernate.internal.AbstractSessionImpl$NonContextualJdbcConnectionAccess.obtainConnection(AbstractSessionImpl.java:276) [hibernate-core-4.0.0.CR6.jar:]

                  at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.obtainConnection(LogicalConnectionImpl.java:299) [hibernate-core-4.0.0.CR6.jar:]

                  ... 128 more

          Caused by: javax.resource.ResourceException: Error checking for a transaction

                  at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:361)

                  at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:448)

                  at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:129)

                  ... 131 more

          Caused by: javax.resource.ResourceException: IJ000459: Transaction is not active: tx=TransactionImple < ac, BasicAction: 0:ffff7f000001:-1a36cbee:4ee73908:6450 status: ActionStatus.ABORTED >

                  at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:351)

                  ... 133 more

          • 2. Re: TransactionReaper - timeout problem
            Nicklas Karlsson Master

            do you have any timeout settings for the datasource?

            • 3. Re: TransactionReaper - timeout problem
              prinzm Newbie

              No we have no timeout settings in our datasource in the standalone.xml

              • 4. Re: TransactionReaper - timeout problem
                Stephen Coy Master

                Is this under load?

                 

                Is it possible that transactions are stalled because you're running out of database connections?

                 

                Do you have long running (> 60s) transactions?

                • 5. Re: TransactionReaper - timeout problem
                  prinzm Newbie

                  1. Yes it is under load

                  2. How can I be sure, that I am running out of database connections? Should there be any additional message in the log?

                  3. Yes in some special cases transactions can take longer than 60s

                  • 6. Re: TransactionReaper - timeout problem
                    Stephen Coy Master

                    When a container runs out of connections, normal behaviour is for it to block until a connection becomes available. If it has to wait too long it's encompassing transaction can time out.

                     

                    The database connection pool size is configured as part of the datasource in your standalone.xml.

                     

                    One way to tell how many connections are in use is to use the netstat command and count the number of TCP connections to your database.

                     

                    If you're using postgresql on linux for example (which listens on port 5432):

                     

                    $ netstat -tn | grep 5432 | wc -l
                    

                    will give you the number of connections times 2 - (one for each half of the TCP connection). On Windows you can use the same netstat command and count the connections yourself.

                     

                    The fact that you can have long running connections makes this a likely scenario.

                     

                    You might find some more useful tips here (from googling "jboss 7 connection pool)

                    • 7. Re: TransactionReaper - timeout problem
                      prinzm Newbie

                      Netstat returned several hundred connections (most of them waiting).

                      I've now made some changes in the datasource settings  (min/max pool-size, added valid-connection-checker), but none of the changes helped.

                      I also had a look at the CLI output:

                       

                      "outcome" => "success",

                          "result" => {

                              "ActiveCount" => "1",

                              "AvailableCount" => "98",

                              "AverageBlockingTime" => "0",

                              "AverageCreationTime" => "175",

                              "CreatedCount" => "919629",

                              "DestroyedCount" => "919628",

                              "MaxCreationTime" => "25942",

                              "MaxUsedCount" => "5",

                              "MaxWaitCount" => "0",

                              "MaxWaitTime" => "1",

                              "PreparedStatementCacheAccessCount" => "8535",

                              "PreparedStatementCacheAddCount" => "7421",

                              "PreparedStatementCacheCurrentSize" => "8",

                              "PreparedStatementCacheDeleteCount" => "0",

                              "PreparedStatementCacheHitCount" => "1114",

                              "PreparedStatementCacheMissCount" => "0",

                              "TimedOut" => "919628",

                              "TotalBlockingTime" => "1032",

                              "TotalCreationTime" => "161785200",

                              "allocation-retry" => undefined,

                              "allocation-retry-wait-millis" => undefined,

                              "background-validation" => true,

                              "background-validation-millis" => undefined,

                              "blocking-timeout-wait-millis" => undefined,

                              "check-valid-connection-sql" => undefined,

                              "connection-properties" => undefined,

                              "connection-url" => "jdbc:as400://<our host>",

                              "datasource-class" => undefined,

                              "driver-class" => "com.ibm.as400.access.AS400JDBCDriver",

                              "driver-name" => "jt400",

                              "enabled" => true,

                              "exception-sorter-class-name" => "org.jboss.jca.adapters.jdbc.extensions.db2.DB2ExceptionSorter",

                              "exception-sorter-properties" => undefined,

                              "flush-strategy" => undefined,

                              "idle-timeout-minutes" => 20L,

                              "jndi-name" => "java:jboss/datasources/green-at-prod",

                              "jta" => true,

                              "max-pool-size" => 100,

                              "min-pool-size" => 5,

                              "new-connection-sql" => undefined,

                              "password" => "jboss",

                              "pool-name" => "AS400",

                              "pool-prefill" => true,

                              "pool-use-strict-min" => undefined,

                              "prepared-statements-cache-size" => 100L,

                              "query-timeout" => undefined,

                              "reauth-plugin-class-name" => undefined,

                              "reauth-plugin-properties" => undefined,

                              "security-domain" => undefined,

                              "set-tx-query-timeout" => "false",

                              "share-prepared-statements" => "false",

                              "spy" => false,

                              "stale-connection-checker-class-name" => "org.jboss.jca.adapters.jdbc.extensions.db2.DB2StaleConnectionChecker",

                              "stale-connection-checker-properties" => undefined,

                              "track-statements" => "\"NOWARN\"",

                              "transaction-isolation" => "TRANSACTION_READ_COMMITTED",

                              "url-delimiter" => undefined,

                              "url-selector-strategy-class-name" => undefined,

                              "use-ccm" => true,

                              "use-fast-fail" => "false",

                              "use-java-context" => true,

                              "use-try-lock" => undefined,

                              "user-name" => "jboss_at",

                              "valid-connection-checker-class-name" => "org.jboss.jca.adapters.jdbc.extensions.db2.DB2ValidConnectionChecker",

                              "valid-connection-checker-properties" => undefined,

                              "validate-on-match" => "false"

                          }

                       

                      Maybe some of the settings are incorrect respectively not optimized?

                      • 8. Re: TransactionReaper - timeout problem
                        Stephen Coy Master

                        How many concurrent connections does DB2 on your AS400 permit?

                         

                        Sometimes these things are limited by the kind of licence that you have.

                        • 9. Re: TransactionReaper - timeout problem
                          Stephen Coy Master

                          prinzm wrote:

                           

                          Netstat returned several hundred connections (most of them waiting).

                           

                          What does that mean? In what state are these connections? ESTABLISHED, CLOSED, SYN_SENT, etc?

                          • 10. Re: TransactionReaper - timeout problem
                            pushpak1981 Novice

                            Were you able to fix this issue bacause we are also facing the same one ?

                            • 11. Re: TransactionReaper - timeout problem
                              prinzm Newbie

                              Unfortunately not.

                               

                              The problem is that we have a mixture of container- and bean-managed transactions and the problem only occurs some time after the bean-managed transactions have been used.

                              I tried several datasource settings, but until now nothing helped.

                               

                              If you find a solution, could you please share it?

                              • 12. Re: TransactionReaper - timeout problem
                                pushpak1981 Novice

                                Not yet. We tried to increase the transaction timeout in standalone-full.xml file. But after that the server was up for around 45 minutes and then it shows up the error message. Earlier the error message used to appear in around 5 minutes.

                                We are still looking into it. Will let you know if we are able to fix this issue.

                                • 13. Re: TransactionReaper - timeout problem
                                  Scott Marlow Master

                                  I just responded to the similar issue on https://community.jboss.org/message/648386.  It might be useful to do the same for this situation also (look at previous activity for the timed out transaction and also look at thread dumps to see which operations are taking longer than expected).

                                   

                                  It might be good to also try the latest AS7 nightly build, downloadable from this link.