[ https://jira.jboss.org/jira/browse/CDITCK-108?page=com.atlassian.jira.plu... ] Pete Muir commented on CDITCK-108: ---------------------------------- org.jboss.jsr299.tck.tests.context.application.ejb.ApplicationContextSharedTest.testApplicationContextShared() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/CDITCK-108?page=com.atlassian.jira.plugin... ] David Blevins commented on CDITCK-108: -------------------------------------- I haven't had a chance to investigate how this may impact CDITCK-155 and CDITCK-156, but this test will fail for thread safety issues occasionally. Bottom line is that waiting on either {{climbed}} or {{descended}} just tests that the timeout method was entered but does not guarantee the end of the method was reached and the proper state was set in the other variables. Maybe adjust the timeout method like this so that when either climbed or descended are set to true the other variables are also in a testable state. {code} @Timeout public void timeout(Timer timer) { if (beanManager.getContext(ApplicationScoped.class).isActive()) { applicationScopeActive = true; if (beanId > 0.0) { if (beanId == simpleApplicationBeanInstance.get().getId()) { sameBean = true; } } else { beanId = simpleApplicationBeanInstance.get().getId(); } } // applicationScopeActive, beanId and sameBean have been set and are testable if (timer.getInfo().equals(CLIMB_COMMAND)) { climbed = true; } if (timer.getInfo().equals(DESCEND_COMMAND)) { descended = true; } } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira