Recently the following error is visible in Selenium tests (here social collab, when viewing the opensocial dashboard it seems)
- logout URL and seam
- theme helper concurrency with unidentified UI thread (todo add stack trace of owner thread)
- TXSQLRepositoryTestCase concurrency between fulltext and repository shutdown in tear down, test suite was frozen on error
We don't have enough information about the owner thread context. I've activated the capture of the owner start call by default in log4j.xml. Should be disabled once we solved.
- depends on
-
NXP-13165 Rework CoreSession management
- Resolved
-
NXP-12763 avoid returning connection in XA pool with wrong state
- Resolved
-
NXP-12883 Fix concurrent requests management on Seam when using Automation
- Resolved
-
NXBT-743 Isolate Concurrency errors in dedicated appender
- Closed
-
NXP-13009 shutdown work manager before closing the repository
- Resolved
-
NXP-14140 Make CoreSession thread-safe
- Resolved
- is duplicated by
-
NXP-13830 Fix selenium timeout after login
- Resolved
- is required by
-
NXP-13652 Fix tagging concurrency issue on suite-dm
- Resolved
-
NXP-13140 Fix missing conversation entry error on tests
- Resolved