From issues at jboss.org Tue Dec 2 09:10:39 2014 From: issues at jboss.org (Daniel Coughlin (JIRA)) Date: Tue, 2 Dec 2014 09:10:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5144) Broken Links on the JBoss.org Projects Page In-Reply-To: References: Message-ID: Daniel Coughlin created JBSEAM-5144: --------------------------------------- Summary: Broken Links on the JBoss.org Projects Page Key: JBSEAM-5144 URL: https://issues.jboss.org/browse/JBSEAM-5144 Project: Seam 2 Issue Type: Bug Reporter: Daniel Coughlin The following broken links are currently listed against this project on www.jboss.org/projects. http://www.jboss.org/projects/ - http://www.seamframework.org/Download - http://www.seamframework.org/Community/SeamUsers - http://www.seamframework.org/Documentation/KnowledgeBase - http://www.seamframework.org/Seam2/Documentation If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Tue Dec 2 10:11:39 2014 From: issues at jboss.org (Daniel Coughlin (JIRA)) Date: Tue, 2 Dec 2014 10:11:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5144) Broken Links on the JBoss.org Projects Page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Coughlin resolved JBSEAM-5144. ------------------------------------- Resolution: Duplicate Issue JBSEAM-5141 - Duplicate Issue. > Broken Links on the JBoss.org Projects Page > ------------------------------------------- > > Key: JBSEAM-5144 > URL: https://issues.jboss.org/browse/JBSEAM-5144 > Project: Seam 2 > Issue Type: Bug > Reporter: Daniel Coughlin > > The following broken links are currently listed against this project on www.jboss.org/projects. > http://www.jboss.org/projects/ > - http://www.seamframework.org/Download > - http://www.seamframework.org/Community/SeamUsers > - http://www.seamframework.org/Documentation/KnowledgeBase > - http://www.seamframework.org/Seam2/Documentation > If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Dec 3 08:32:39 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Wed, 3 Dec 2014 08:32:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024719#comment-13024719 ] Marek Novotny commented on JBSEAM-5143: --------------------------------------- [~r0b3n] not sure, it should be fixed since Mojarra 2.1.19. Are you able to develop a test case like we have for JBSEAM-5002? see https://github.com/seam2/jboss-seam/blob/Seam_2_3/seam-integration-tests/src/test/java/org/jboss/seam/test/integration/faces/PageScopedUIIncludeTest.java > Random IllegalArgumentException: Stack must not be null > ------------------------------------------------------- > > Key: JBSEAM-5143 > URL: https://issues.jboss.org/browse/JBSEAM-5143 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development. Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs. > I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet. > Besides Seam 2.3, the following libraries are used: > - Mojarra 2.1.29 > - RF 4.5 (exception also occurred with 4.3.x) > - Omnifaces 1.10RC1 (will upgrade to 2.0) > - Primefaces 5.1 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Dec 3 09:12:39 2014 From: issues at jboss.org (Robert Becker (JIRA)) Date: Wed, 3 Dec 2014 09:12:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024741#comment-13024741 ] Robert Becker commented on JBSEAM-5143: --------------------------------------- Sadly not, because the whole problem is highly non-deterministic. On the production machine today this exception occurred 14 times while a total of 144 users logged in. It happens on POST and GET requests. I think the best clue is "isPageContextActive is null" (see Contexts.isPageContextActive()) being never printed when this exception occurs. Do you know in wich cases the page context can not be lazily initialized? I tried to dig further into the Lifecycle but it gets somehow fuzzy from this point on. I am currently running Mojarra 2.1.29 (confirmed via startup log message), so the said fix should be available. > Random IllegalArgumentException: Stack must not be null > ------------------------------------------------------- > > Key: JBSEAM-5143 > URL: https://issues.jboss.org/browse/JBSEAM-5143 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development. Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs. > I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet. > Besides Seam 2.3, the following libraries are used: > - Mojarra 2.1.29 > - RF 4.5 (exception also occurred with 4.3.x) > - Omnifaces 1.10RC1 (will upgrade to 2.0) > - Primefaces 5.1 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Dec 3 09:14:39 2014 From: issues at jboss.org (Robert Becker (JIRA)) Date: Wed, 3 Dec 2014 09:14:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024741#comment-13024741 ] Robert Becker edited comment on JBSEAM-5143 at 12/3/14 9:13 AM: ---------------------------------------------------------------- Sadly not, because the whole problem is highly non-deterministic. On the production machine today this exception occurred 4 times while a total of 144 users logged in. It happens on POST and GET requests. I think the best clue is "isPageContextActive is null" (see Contexts.isPageContextActive()) being never printed when this exception occurs. Do you know in wich cases the page context can not be lazily initialized? I tried to dig further into the Lifecycle but it gets somehow fuzzy from this point on. I am currently running Mojarra 2.1.29 (confirmed via startup log message), so the said fix should be available. was (Author: r0b3n): Sadly not, because the whole problem is highly non-deterministic. On the production machine today this exception occurred 14 times while a total of 144 users logged in. It happens on POST and GET requests. I think the best clue is "isPageContextActive is null" (see Contexts.isPageContextActive()) being never printed when this exception occurs. Do you know in wich cases the page context can not be lazily initialized? I tried to dig further into the Lifecycle but it gets somehow fuzzy from this point on. I am currently running Mojarra 2.1.29 (confirmed via startup log message), so the said fix should be available. > Random IllegalArgumentException: Stack must not be null > ------------------------------------------------------- > > Key: JBSEAM-5143 > URL: https://issues.jboss.org/browse/JBSEAM-5143 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development. Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs. > I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet. > Besides Seam 2.3, the following libraries are used: > - Mojarra 2.1.29 > - RF 4.5 (exception also occurred with 4.3.x) > - Omnifaces 1.10RC1 (will upgrade to 2.0) > - Primefaces 5.1 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Dec 3 09:24:39 2014 From: issues at jboss.org (Robert Becker (JIRA)) Date: Wed, 3 Dec 2014 09:24:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024754#comment-13024754 ] Robert Becker commented on JBSEAM-5143: --------------------------------------- Hm, the message is only logged if {{pageContext.get() == null}}, so a page context gets retrieved from the ThreadLocal. So the stored page context is missing its conversation stack. > Random IllegalArgumentException: Stack must not be null > ------------------------------------------------------- > > Key: JBSEAM-5143 > URL: https://issues.jboss.org/browse/JBSEAM-5143 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development. Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs. > I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet. > Besides Seam 2.3, the following libraries are used: > - Mojarra 2.1.29 > - RF 4.5 (exception also occurred with 4.3.x) > - Omnifaces 1.10RC1 (will upgrade to 2.0) > - Primefaces 5.1 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Dec 3 09:25:39 2014 From: issues at jboss.org (Robert Becker (JIRA)) Date: Wed, 3 Dec 2014 09:25:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024754#comment-13024754 ] Robert Becker edited comment on JBSEAM-5143 at 12/3/14 9:25 AM: ---------------------------------------------------------------- Hm, the message is only logged if {{pageContext.get() == null}}, so a page context gets retrieved from the ThreadLocal. This means that the current page context is missing its conversation stack for some reason. was (Author: r0b3n): Hm, the message is only logged if {{pageContext.get() == null}}, so a page context gets retrieved from the ThreadLocal. So the stored page context is missing its conversation stack. > Random IllegalArgumentException: Stack must not be null > ------------------------------------------------------- > > Key: JBSEAM-5143 > URL: https://issues.jboss.org/browse/JBSEAM-5143 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development. Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs. > I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet. > Besides Seam 2.3, the following libraries are used: > - Mojarra 2.1.29 > - RF 4.5 (exception also occurred with 4.3.x) > - Omnifaces 1.10RC1 (will upgrade to 2.0) > - Primefaces 5.1 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Dec 3 09:53:39 2014 From: issues at jboss.org (Robert Becker (JIRA)) Date: Wed, 3 Dec 2014 09:53:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024798#comment-13024798 ] Robert Becker commented on JBSEAM-5143: --------------------------------------- Sorry, these are all assumptions and perhaps I am completely on the wrong path here. One thing for sure is: The stack trace implies that {{Manager.getCurrentConversationEntry()}} returns null, because {{createConversationEntry}} is called in {{beforeRedirect}}: {code} public ConversationEntry getCurrentConversationEntry() { if (currentConversationEntry==null) { currentConversationEntry = ConversationEntries.instance().getConversationEntry( getCurrentConversationId() ); } return currentConversationEntry; } ... /** * Temporarily promote a temporary conversation to * a long running conversation for the duration of * a browser redirect. After the redirect, the * conversation will be demoted back to a temporary * conversation. */ public void beforeRedirect() { //DONT BREAK, icefaces uses this if (!destroyBeforeRedirect) { ConversationEntry ce = getCurrentConversationEntry(); if (ce==null) { ce = createConversationEntry(); } //ups, we don't really want to destroy it on this request after all! ce.setRemoveAfterRedirect( !isLongRunningConversation() ); setLongRunningConversation(true); } } {code} > Random IllegalArgumentException: Stack must not be null > ------------------------------------------------------- > > Key: JBSEAM-5143 > URL: https://issues.jboss.org/browse/JBSEAM-5143 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development. Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs. > I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet. > Besides Seam 2.3, the following libraries are used: > - Mojarra 2.1.29 > - RF 4.5 (exception also occurred with 4.3.x) > - Omnifaces 1.10RC1 (will upgrade to 2.0) > - Primefaces 5.1 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Wed Dec 3 10:07:39 2014 From: issues at jboss.org (Robert Becker (JIRA)) Date: Wed, 3 Dec 2014 10:07:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024805#comment-13024805 ] Robert Becker commented on JBSEAM-5143: --------------------------------------- I noticed the posted stack trace containing a manual redirect using `Redirect.instance()`. This here is a different stack trace of a GET request without redirecting: http://pastebin.com/RJyMP5nk Here, of course, beforeRedirect() is not called but the stack trace falls together with the other one in {{Manager.createConversationEntry()}}. > Random IllegalArgumentException: Stack must not be null > ------------------------------------------------------- > > Key: JBSEAM-5143 > URL: https://issues.jboss.org/browse/JBSEAM-5143 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development. Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs. > I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet. > Besides Seam 2.3, the following libraries are used: > - Mojarra 2.1.29 > - RF 4.5 (exception also occurred with 4.3.x) > - Omnifaces 1.10RC1 (will upgrade to 2.0) > - Primefaces 5.1 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Dec 4 05:08:40 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Thu, 4 Dec 2014 05:08:40 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025083#comment-13025083 ] 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. > Random IllegalArgumentException: Stack must not be null > ------------------------------------------------------- > > Key: JBSEAM-5143 > URL: https://issues.jboss.org/browse/JBSEAM-5143 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development. Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs. > I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet. > Besides Seam 2.3, the following libraries are used: > - Mojarra 2.1.29 > - RF 4.5 (exception also occurred with 4.3.x) > - Omnifaces 1.10RC1 (will upgrade to 2.0) > - Primefaces 5.1 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Dec 4 05:27:39 2014 From: issues at jboss.org (Robert Becker (JIRA)) Date: Thu, 4 Dec 2014 05:27:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025102#comment-13025102 ] Robert Becker commented on JBSEAM-5143: --------------------------------------- Many thanks for your insight. > 1. Am I right that you have enabled client state saving ? This is not recommended setting. I just had it enabled for a day or two to see if it makes any difference, which it doesn't. Currently I am using partial server side state saving which also is my preferred configuration. > 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. The strange thing is that it even happens using s:links with propagation="none" and in very different parts of the application. For example yesterday I worked on a specific view being referenced which such a link from the main menu. I used the link dozens of times where it worked fine, then suddenly the exception occurred and afterwards it worked normally again. > Honestly I can't say anything more without seeing more application code. If I could just narrow it down to what to show you. > And I would recommend to try deployment also on JBoss AS 7 or EAP 6.3.x for comparison. I had that in mind, too. I will try that. > Random IllegalArgumentException: Stack must not be null > ------------------------------------------------------- > > Key: JBSEAM-5143 > URL: https://issues.jboss.org/browse/JBSEAM-5143 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development. Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs. > I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet. > Besides Seam 2.3, the following libraries are used: > - Mojarra 2.1.29 > - RF 4.5 (exception also occurred with 4.3.x) > - Omnifaces 1.10RC1 (will upgrade to 2.0) > - Primefaces 5.1 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Dec 4 05:28:39 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Thu, 4 Dec 2014 05:28:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org - Seam In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny resolved JBSEAM-5141. ----------------------------------- Resolution: Done > Broken Links on JBoss.org - Seam > -------------------------------- > > Key: JBSEAM-5141 > URL: https://issues.jboss.org/browse/JBSEAM-5141 > Project: Seam 2 > Issue Type: Bug > Reporter: Daniel Coughlin > Assignee: Marek Novotny > > The following broken link is currently listed against this project on www.jboss.org/projects. > http://www.seamframework.org/Seam2/Documentation - Documentation > http://www.seamframework.org/Documentation/KnowledgeBase - Community > http://www.seamframework.org/Community/SeamUsers - User Forum > http://www.seamframework.org/Download - Download (Forbidden) > If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Dec 4 05:29:39 2014 From: issues at jboss.org (David Hladky (JIRA)) Date: Thu, 4 Dec 2014 05:29:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org - Seam In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025104#comment-13025104 ] David Hladky commented on JBSEAM-5141: -------------------------------------- Links updated in Magnolia, now we need to wait for [~lvlcek] to reindex DCP. > Broken Links on JBoss.org - Seam > -------------------------------- > > Key: JBSEAM-5141 > URL: https://issues.jboss.org/browse/JBSEAM-5141 > Project: Seam 2 > Issue Type: Bug > Reporter: Daniel Coughlin > Assignee: Marek Novotny > > The following broken link is currently listed against this project on www.jboss.org/projects. > http://www.seamframework.org/Seam2/Documentation - Documentation > http://www.seamframework.org/Documentation/KnowledgeBase - Community > http://www.seamframework.org/Community/SeamUsers - User Forum > http://www.seamframework.org/Download - Download (Forbidden) > If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Dec 4 05:43:39 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Thu, 4 Dec 2014 05:43:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025109#comment-13025109 ] Marek Novotny commented on JBSEAM-5143: --------------------------------------- >The strange thing is that it even happens using s:links with propagation="none" That is what it meant by bad usage of conversation, propagation=none means it will not send the conversation Id and if there is long running conversation from previous state, it will be reset /set to null/ Look in org.jboss.seam.core.ConversationPropagation.restoreConversationId(Map) for deep details. Anyway try to insert debug/trace logs in org.jboss.seam.core.Manager.restoreConversation() and org.jboss.seam.core.Manager.restoreAndLockConversation(ConversationEntry) and org.jboss.seam.core.ConversationInterceptor.beginConversation(boolean, String) for imagination what is set and how. org.jboss.seam.core.ConversationPropagation.restorePageContextConversationId() > Random IllegalArgumentException: Stack must not be null > ------------------------------------------------------- > > Key: JBSEAM-5143 > URL: https://issues.jboss.org/browse/JBSEAM-5143 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development. Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs. > I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet. > Besides Seam 2.3, the following libraries are used: > - Mojarra 2.1.29 > - RF 4.5 (exception also occurred with 4.3.x) > - Omnifaces 1.10RC1 (will upgrade to 2.0) > - Primefaces 5.1 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Dec 4 05:44:39 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Thu, 4 Dec 2014 05:44:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025109#comment-13025109 ] Marek Novotny edited comment on JBSEAM-5143 at 12/4/14 5:43 AM: ---------------------------------------------------------------- >The strange thing is that it even happens using s:links with propagation="none" That is what I meant by bad usage of conversation, propagation=none means it will not send the conversation Id and if there is long running conversation from previous state, it will be reset /set to null/ Look in org.jboss.seam.core.ConversationPropagation.restoreConversationId(Map) for deep details. Anyway try to insert debug/trace logs in org.jboss.seam.core.Manager.restoreConversation() and org.jboss.seam.core.Manager.restoreAndLockConversation(ConversationEntry) and org.jboss.seam.core.ConversationInterceptor.beginConversation(boolean, String) for imagination what is set and how. org.jboss.seam.core.ConversationPropagation.restorePageContextConversationId() was (Author: manarh): >The strange thing is that it even happens using s:links with propagation="none" That is what it meant by bad usage of conversation, propagation=none means it will not send the conversation Id and if there is long running conversation from previous state, it will be reset /set to null/ Look in org.jboss.seam.core.ConversationPropagation.restoreConversationId(Map) for deep details. Anyway try to insert debug/trace logs in org.jboss.seam.core.Manager.restoreConversation() and org.jboss.seam.core.Manager.restoreAndLockConversation(ConversationEntry) and org.jboss.seam.core.ConversationInterceptor.beginConversation(boolean, String) for imagination what is set and how. org.jboss.seam.core.ConversationPropagation.restorePageContextConversationId() > Random IllegalArgumentException: Stack must not be null > ------------------------------------------------------- > > Key: JBSEAM-5143 > URL: https://issues.jboss.org/browse/JBSEAM-5143 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development. Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs. > I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet. > Besides Seam 2.3, the following libraries are used: > - Mojarra 2.1.29 > - RF 4.5 (exception also occurred with 4.3.x) > - Omnifaces 1.10RC1 (will upgrade to 2.0) > - Primefaces 5.1 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Dec 4 05:54:39 2014 From: issues at jboss.org (Lukas Vlcek (JIRA)) Date: Thu, 4 Dec 2014 05:54:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org - Seam In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025116#comment-13025116 ] Lukas Vlcek commented on JBSEAM-5141: ------------------------------------- [~manaRH] Reindexed. > Broken Links on JBoss.org - Seam > -------------------------------- > > Key: JBSEAM-5141 > URL: https://issues.jboss.org/browse/JBSEAM-5141 > Project: Seam 2 > Issue Type: Bug > Reporter: Daniel Coughlin > Assignee: Marek Novotny > > The following broken link is currently listed against this project on www.jboss.org/projects. > http://www.seamframework.org/Seam2/Documentation - Documentation > http://www.seamframework.org/Documentation/KnowledgeBase - Community > http://www.seamframework.org/Community/SeamUsers - User Forum > http://www.seamframework.org/Download - Download (Forbidden) > If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Dec 4 06:16:39 2014 From: issues at jboss.org (Robert Becker (JIRA)) Date: Thu, 4 Dec 2014 06:16:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025129#comment-13025129 ] Robert Becker commented on JBSEAM-5143: --------------------------------------- > That is what I meant by bad usage of conversation, propagation=none means it will not send the conversation Id and if there is long running conversation from previous state, it will be reset /set to null/ Look in org.jboss.seam.core.ConversationPropagation.restoreConversationId(Map) for deep details. In this case that is desired: Navigation links from the main navigation menu should never propagate any conversation state. New conversations are started if required on the pages linked by the main menu using @Begin/@Create annotations. But again, the exception also occurs when the conversation id parameter is present during form posts and so on and even on views where no long running conversation is used at all. I will try to debug/trace the methods you mentioned and report back any findings. > Random IllegalArgumentException: Stack must not be null > ------------------------------------------------------- > > Key: JBSEAM-5143 > URL: https://issues.jboss.org/browse/JBSEAM-5143 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development. Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs. > I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet. > Besides Seam 2.3, the following libraries are used: > - Mojarra 2.1.29 > - RF 4.5 (exception also occurred with 4.3.x) > - Omnifaces 1.10RC1 (will upgrade to 2.0) > - Primefaces 5.1 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Dec 4 17:10:39 2014 From: issues at jboss.org (Daniel Coughlin (JIRA)) Date: Thu, 4 Dec 2014 17:10:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org - Seam In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025321#comment-13025321 ] Daniel Coughlin commented on JBSEAM-5141: ----------------------------------------- Everything looks good. Thank you all! > Broken Links on JBoss.org - Seam > -------------------------------- > > Key: JBSEAM-5141 > URL: https://issues.jboss.org/browse/JBSEAM-5141 > Project: Seam 2 > Issue Type: Bug > Reporter: Daniel Coughlin > Assignee: Marek Novotny > > The following broken link is currently listed against this project on www.jboss.org/projects. > http://www.seamframework.org/Seam2/Documentation - Documentation > http://www.seamframework.org/Documentation/KnowledgeBase - Community > http://www.seamframework.org/Community/SeamUsers - User Forum > http://www.seamframework.org/Download - Download (Forbidden) > If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Fri Dec 5 04:58:39 2014 From: issues at jboss.org (Marek Novotny (JIRA)) Date: Fri, 5 Dec 2014 04:58:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org - Seam In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny closed JBSEAM-5141. --------------------------------- all looks working > Broken Links on JBoss.org - Seam > -------------------------------- > > Key: JBSEAM-5141 > URL: https://issues.jboss.org/browse/JBSEAM-5141 > Project: Seam 2 > Issue Type: Bug > Reporter: Daniel Coughlin > Assignee: Marek Novotny > > The following broken link is currently listed against this project on www.jboss.org/projects. > http://www.seamframework.org/Seam2/Documentation - Documentation > http://www.seamframework.org/Documentation/KnowledgeBase - Community > http://www.seamframework.org/Community/SeamUsers - User Forum > http://www.seamframework.org/Download - Download (Forbidden) > If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 8 08:23:39 2014 From: issues at jboss.org (Robert Becker (JIRA)) Date: Mon, 8 Dec 2014 08:23:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025866#comment-13025866 ] Robert Becker commented on JBSEAM-5143: --------------------------------------- I migrated the application to run on JBoss AS 7.1.3 (also with Mojarra 2.1.29) and so far did not encounter the exception or anything related - Fingers crossed that this was not only by chance. I will change the production deployment this evening to JBoss AS and hopefully can confirm that this "fixed" the issue. Perhaps the latest Mojarra caused some issue together with glassfish, but fixes so many things on the other side, that I do not want to revert to older versions. > Random IllegalArgumentException: Stack must not be null > ------------------------------------------------------- > > Key: JBSEAM-5143 > URL: https://issues.jboss.org/browse/JBSEAM-5143 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development. Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs. > I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet. > Besides Seam 2.3, the following libraries are used: > - Mojarra 2.1.29 > - RF 4.5 (exception also occurred with 4.3.x) > - Omnifaces 1.10RC1 (will upgrade to 2.0) > - Primefaces 5.1 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Mon Dec 8 08:24:39 2014 From: issues at jboss.org (Robert Becker (JIRA)) Date: Mon, 8 Dec 2014 08:24:39 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025866#comment-13025866 ] Robert Becker edited comment on JBSEAM-5143 at 12/8/14 8:24 AM: ---------------------------------------------------------------- I migrated the application to run on JBoss AS 7.1.3 (also with Mojarra 2.1.29) and so far did not encounter the exception or anything related - Fingers crossed that this was not only by chance. I will change the production deployment this evening to JBoss AS and hopefully can confirm that this "fixed" the issue. Perhaps the latest Mojarra caused some issue together with glassfish, but it also fixes so many things on the other side, that I do not want to revert to older versions. was (Author: r0b3n): I migrated the application to run on JBoss AS 7.1.3 (also with Mojarra 2.1.29) and so far did not encounter the exception or anything related - Fingers crossed that this was not only by chance. I will change the production deployment this evening to JBoss AS and hopefully can confirm that this "fixed" the issue. Perhaps the latest Mojarra caused some issue together with glassfish, but fixes so many things on the other side, that I do not want to revert to older versions. > Random IllegalArgumentException: Stack must not be null > ------------------------------------------------------- > > Key: JBSEAM-5143 > URL: https://issues.jboss.org/browse/JBSEAM-5143 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development. Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs. > I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet. > Besides Seam 2.3, the following libraries are used: > - Mojarra 2.1.29 > - RF 4.5 (exception also occurred with 4.3.x) > - Omnifaces 1.10RC1 (will upgrade to 2.0) > - Primefaces 5.1 -- This message was sent by Atlassian JIRA (v6.3.8#6338) From issues at jboss.org Thu Dec 11 09:47:29 2014 From: issues at jboss.org (Robert Becker (JIRA)) Date: Thu, 11 Dec 2014 09:47:29 -0500 (EST) Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027097#comment-13027097 ] Robert Becker commented on JBSEAM-5143: --------------------------------------- Sadly, there are still "Stack must not be null" exceptions being logged by JBoss. As I am out of the office for the next couple of days I can not investigate this further for now. I will try some more debugging when I am back. Also, I just noticed this in logs: https://developer.jboss.org/thread/229275?tstart=0 > Random IllegalArgumentException: Stack must not be null > ------------------------------------------------------- > > Key: JBSEAM-5143 > URL: https://issues.jboss.org/browse/JBSEAM-5143 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development. Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs. > I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet. > Besides Seam 2.3, the following libraries are used: > - Mojarra 2.1.29 > - RF 4.5 (exception also occurred with 4.3.x) > - Omnifaces 1.10RC1 (will upgrade to 2.0) > - Primefaces 5.1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)