-
Type: Improvement
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 5.8
-
Component/s: Seam / JSF UI
In some cases, Seam page rendering can fail because of the Conversation locking system and a ConcurrentRequetsTimeout exception is visible in logs.
See : http://doc.nuxeo.com/display/NXDOC/I+get+an+error+when+I+click+on+two+links+quickly
The root of the problem is that the way Seam handles the conversation concurrency is not ideal.
We can surely do better :
- try to choose the victim : kill the old request and not the new one
or - create a temporary conversation that has a change to run : re-init a minimal context
or - reduce critical section size
...
- depends on
-
NXDOC-242 Update Seam concurrent request timeout issue explanation
- Resolved
-
NXP-12883 Fix concurrent requests management on Seam when using Automation
- Resolved
- is required by
-
NXP-11968 Make Seam conversation locking more granular and efficient
- Resolved
-
NXP-4701 Fix thread blocked by seam conversation handling
- Resolved
-
NXP-13140 Fix missing conversation entry error on tests
- Resolved
-
VEND-1 Reapply nx patches on Seam 2.3
- Resolved
-
VEND-10 Release Seam patched version 2.1.0.SP1-NX1
- Resolved
-
VEND-20 Improve Seam Concurrency request management
- Closed
-
NXP-12500 As a user of DM, I no more have "ConcurrentRequestTimeout" errors when clicking twice in a row on an action
- Resolved