Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Handle coversation timeout
See original GitHub issueIn 3.1 we uses conversation context for all forms. This is better than session scope because it allows to open few tabs to do few independent updates simultaneously. Example: Tab 1: https://u144.gluu.info/identity/person/update/@!FE7B.148F.D760.2436!0001!A0D4.6821!0000!51BE.EDED.A372.2CA8?cid=3 Tab 2: https://u144.gluu.info/identity/person/update/@!FE7B.148F.D760.2436!0001!A0D4.6821!0000!FE57.BF9D.DF9D.0760?cid=4
The default conversation timeout is 10 minutes. After this time application cleans expired conversations. When user access to open such expired session Weld throws:
javax.faces.FacesException: WELD-000321: No conversation found to restore for id XYZ
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Added catch of this exception and specify added message for this case