-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 5.9.6-SNAPSHOT, 6.0
-
Fix Version/s: None
-
Component/s: Seam / JSF UI
-
Epic Link:
-
Backlog priority:300
-
Team:AT
-
Story Points:8
The current system allowing concurrent conversations in Seam seems to produce spurious error in logs.
The redirection mechanism on error is done in a degraded context, and Seam method do not seem to be ready for this.
- depends on
-
NXP-20403 core session should be close on rollback also
-
- Resolved
-
-
NXP-22045 Fix incorrect error management blocking Tomcat threads
-
- Resolved
-
-
VEND-20 Improve Seam Concurrency request management
-
- Closed
-
- is required by
-
NXP-16000 Random Selenium failure on addons_FT_nuxeo-platform-error-web-master: error_index.faces
-
- Open
-
-
NXP-13140 Fix missing conversation entry error on tests
-
- Resolved
-
-
NXP-15516 Fix opensocial gadgets on MSSQL/PostgreSQL
-
- Resolved
-
-
NXP-16060 Fix "concurrent request" warning message when binding template
-
- Resolved
-
-
NXP-16885 Fix random error ITModifyWorkspaceDescriptionTest.testModifyWsDescription
-
- Resolved
-
-
NXP-20233 Fix webengine template rendering when transaction is rollbackonly
-
- Resolved
-