Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by wildfly-ci
, 1 year ago
expected:<200> but was:<500>
via GitHub by wildfly-ci
, 1 year ago
expected:<200> but was:<500>
via GitHub by wildfly-ci
, 1 year ago
expected:<200> but was:<500>
via GitHub by wildfly-ci
, 1 year ago
expected:<200> but was:<500>
via GitHub by wildfly-ci
, 1 year ago
expected:<200> but was:<500>
java.lang.AssertionError: expected:<200> but was:<500> at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:64) at org.jboss.as.test.clustering.ClusterHttpClientUtil.establishTopology(ClusterHttpClientUtil.java:54) at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.establishTopology(ClusteredWebFailoverAbstractCase.java:256) at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.testFailover(ClusteredWebFailoverAbstractCase.java:171) at org.jboss.as.test.clustering.cluster.web.ClusteredWebFailoverAbstractCase.testGracefulSimpleFailover(ClusteredWebFailoverAbstractCase.java:83)