[ https://issues.jboss.org/browse/WFLY-8821?page=com.atlassian.jira.plugin.... ] Michal Jurc edited comment on WFLY-8821 at 5/24/17 1:20 AM: ------------------------------------------------------------ [~brian.stansberry]: I have noticed this when I was implementing a test in AS TS. Without [this|https://github.com/wildfly/wildfly/pull/10040/files#diff-b045ec131e9...] reload at following address, the tests invoking EJBs from client in Integration Basic module of testsuite would attempt to connect to server the old way, receiving HTTP response code 200 indicating the http upgrade response, which happens with active Elytron connector. The only test adding {{http-connector}} backed by Elytron is {{MixedSecurityAnnotationAuthorizationTestCase}}. If that reload is not present, the {{standalone-full.xml}} is clean after the test, server state is {{running}} (not {{reload-required}}), but yet the tests after it that invoke EJBs remotely are clearly connecting to Elytron connector. The tests are ran with this command: {code}mvn clean test -Dtest=org.jboss.as.test.integration.ejb.security.**.*{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)