[ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBSEAM-5143: --------------------------------------- I have got a few points. 1. Am I right that you have enabled client state saving ? This is not recommended setting. 2. The debug message "isPageContextActive is null" is a helper for signalling that page context doesn't exist and then it would be lazy initiated and that is only in case you are in RESTORE_VIEW phase, but your second stack trace implies it happens in RENDER phase too, so your application fails in both JSF phases and you should find out what exact steps lead to the failure. I would guess it is not a random failure, but there is some point in previous navigation or a step which prevents the continuation of using/restoring conversation - like bad conversation usage. 3. More or less I think, the main issue is missing conversation Id or not restored conversation completely, because if you are not in long running conversation, the id is automatically created, so it seems that conversation which seems is long conversation is somehow crippled. That CRUD method prepare is trying to create nested conversation in parent conversation, but it is not restored properly the parent conversation id, why that is the question? If you see conversation id in request parameters it should be restored - that is the only way how to pass the conversation id now on JSF 2. We changed that due new partial view processing. Honestly I can't say anything more without seeing more application code. And I would recommend to try deployment also on JBoss AS 7 or EAP 6.3.x for comparison. -- This message was sent by Atlassian JIRA (v6.3.8#6338)