December 2014 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null

by Robert Becker (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugi... ] 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-illegalargumentexcep...) 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null

by Robert Becker (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugi... ] 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-illegalargumentexcep...) 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null

by Robert Becker (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugi... ] 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-illegalargumentexcep...) 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org - Seam

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5141?page=com.atlassian.jira.plugi... ] 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org - Seam

by Daniel Coughlin (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5141?page=com.atlassian.jira.plugi... ] 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null

by Robert Becker (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugi... ] 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-illegalargumentexcep...) 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org - Seam

by Lukas Vlcek (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5141?page=com.atlassian.jira.plugi... ] 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugi... ] 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-illegalargumentexcep...) 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugi... ] 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-illegalargumentexcep...) 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org - Seam

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5141?page=com.atlassian.jira.plugi... ] 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)

9 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2014