Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-17604

Hangs in TwoConnectorsEJBFailoverTestCase

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • None
    • Clustering, EJB
    • None
    • ---
    • ---

      We're starting to see frequent massively failed CI runs due to clustering TS problems. Looking at a couple recent ones like https://ci.wildfly.org/viewLog.html?buildId=349372&tab=buildResultsDiv&buildTypeId=WF_PullRequest_LinuxJdk17&branch_WF_PullRequest=pull%2F16508

      [19:25:07][Step 2/3] [INFO] Running org.jboss.as.test.clustering.cluster.ejb.remote.TwoConnectorsEJBFailoverTestCase
      [19:25:08][Step 2/3] org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase
      [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] affinityCommit_http
      [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] rollbackWithNoXAResourceEnlistment
      [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] rollback_http
      [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] affinityCommit_remoteHttp
      [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] rollback_wildflyConfig
      [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] rollback_remoteHttp
      [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] directLookupFailure
      [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] affinityNodeFailure
      [19:25:08][org.jboss.as.test.clustering.cluster.ejb.remote.TransactionalRemoteStatelessTestCase] affinityCommit_wildflyConfig
      [20:44:53][Step 2/3] [INFO] 
      [20:44:53][Step 2/3] [INFO] Results:
      [20:44:53][Step 2/3] [INFO] 
      [20:44:53][Step 2/3] [WARNING] Tests run: 35, Failures: 0, Errors: 0, Skipped: 5
      [20:44:53][Step 2/3] [INFO] 
      [20:44:53][Step 2/3] [ERROR] There was a timeout or other error in the fork
      

            pferraro@redhat.com Paul Ferraro
            bstansbe@redhat.com Brian Stansberry
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: