java.lang.AssertionError: expected:<200> but was:<500>

GitHub | wildfly-ci | 1 year ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    GitHub comment 8697#184929116

    GitHub | 1 year ago | wildfly-ci
    java.lang.AssertionError: expected:<200> but was:<500>
  2. 0

    GitHub comment 8088#139365582

    GitHub | 2 years ago | wildfly-ci
    java.lang.AssertionError: expected:<13> but was:<1>
  3. 0

    GitHub comment 8227#145041717

    GitHub | 2 years ago | wildfly-ci
    java.lang.AssertionError: expected:<3> but was:<1>
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    GitHub comment 8227#145041924

    GitHub | 2 years ago | wildfly-ci
    java.lang.AssertionError: expected:<3> but was:<1>

    Root Cause Analysis

    1. java.lang.AssertionError

      expected:<200> but was:<500>

      at org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase.queryCount()
    2. org.jboss.as
      StatefulFailoverTestCase.jmsConnectionFactoryFailover
      1. org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase.queryCount(StatefulFailoverTestCase.java:319)
      2. org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase.failover(StatefulFailoverTestCase.java:190)
      3. org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase.jmsConnectionFactoryFailover(StatefulFailoverTestCase.java:169)
      3 frames