From issues at jboss.org Wed Nov 12 04:45:30 2014 Content-Type: multipart/mixed; boundary="===============2564916817909247284==" MIME-Version: 1.0 From: Anonymous (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4226) + login-required="true" throws "java.lang.IllegalStateException: long-running conversation already active" after login succeeded Date: Wed, 12 Nov 2014 04:45:30 -0500 Message-ID: In-Reply-To: JIRA.12387618.1244289869000@Atlassian.JIRA --===============2564916817909247284== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-4226?page=3Dcom.atlassian.jira= .plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13019247#= comment-13019247 ] = Anonymous commented on JBSEAM-4226: ----------------------------------- http://joshadamsrealtor.com/nike/nike-men-air-max-bw_c32http://joshadamsrea= ltor.com/nike/nike-men-air-max-bw_c32 Infants U= GG Boots sale [url=3Dhttp://lucidlifestyles.com/ugg/infants-ugg-boots_c2]Infants UGG Boot= s sale[/url] > + login-required=3D"true" thr= ows "java.lang.IllegalStateException: long-running conversation already act= ive" after login succeeded > -------------------------------------------------------------------------= ---------------------------------------------------------------------------= -------------------- > > Key: JBSEAM-4226 > URL: https://issues.jboss.org/browse/JBSEAM-4226 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.1.2.CR2 > Environment: JBoss 4.2.3 Seam 2.1.2CR2 snapshot > Reporter: Gena > > Hello, > if i use and the view pointed by s:link requires login within the pag= es.xml i get an exception: " java.lang.IllegalStateException: long-running = conversation already active" after login succeeded and before redirect shou= ld occur. = > The problem is present since about 6 weeks. If i change the propagation = to "none" it works, but the request from the link above is proceessed withi= n the current long running conversation and if this conversation timed out,= i always get the conversation timeout redirect an can not simple leave the= current page with one click on the link described above. > Switch to the previous Seam build resolves the problem. > Gena -- This message was sent by Atlassian JIRA (v6.3.8#6338) --===============2564916817909247284==-- From issues at jboss.org Wed Nov 12 04:45:30 2014 Content-Type: multipart/mixed; boundary="===============2128265207137734500==" MIME-Version: 1.0 From: Anonymous (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4226) + login-required="true" throws "java.lang.IllegalStateException: long-running conversation already active" after login succeeded Date: Wed, 12 Nov 2014 04:45:30 -0500 Message-ID: In-Reply-To: JIRA.12387618.1244289869000@Atlassian.JIRA --===============2128265207137734500== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-4226?page=3Dcom.atlassian.jira= .plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13019246#= comment-13019246 ] = Anonymous commented on JBSEAM-4226: ----------------------------------- http://lucidlifestyles.com/nike/nike-blazer-woven_c88http://lucidlifestyles= .com/nike/nike-blazer-woven_c88 cheap Shox NZ [url=3Dhttp://lucidlifestyles.com/nike/shox-nz_c190]cheap Shox NZ[/url] > + login-required=3D"true" thr= ows "java.lang.IllegalStateException: long-running conversation already act= ive" after login succeeded > -------------------------------------------------------------------------= ---------------------------------------------------------------------------= -------------------- > > Key: JBSEAM-4226 > URL: https://issues.jboss.org/browse/JBSEAM-4226 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.1.2.CR2 > Environment: JBoss 4.2.3 Seam 2.1.2CR2 snapshot > Reporter: Gena > > Hello, > if i use and the view pointed by s:link requires login within the pag= es.xml i get an exception: " java.lang.IllegalStateException: long-running = conversation already active" after login succeeded and before redirect shou= ld occur. = > The problem is present since about 6 weeks. If i change the propagation = to "none" it works, but the request from the link above is proceessed withi= n the current long running conversation and if this conversation timed out,= i always get the conversation timeout redirect an can not simple leave the= current page with one click on the link described above. > Switch to the previous Seam build resolves the problem. > Gena -- This message was sent by Atlassian JIRA (v6.3.8#6338) --===============2128265207137734500==-- From issues at jboss.org Wed Nov 12 05:40:29 2014 Content-Type: multipart/mixed; boundary="===============5426345099736213882==" MIME-Version: 1.0 From: Anonymous (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-180) navigation-rules.xml to allow redirection with parameters Date: Wed, 12 Nov 2014 05:40:29 -0500 Message-ID: In-Reply-To: JIRA.12323818.1143320147000@Atlassian.JIRA --===============5426345099736213882== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-180?page=3Dcom.atlassian.jira.= plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13019273#c= omment-13019273 ] = Anonymous commented on JBSEAM-180: ---------------------------------- http://www.quangminhtrade.com/ads/mbt =D0=AC=EF=BF=BD=EF=BF=BD =EF=BF=BDu=EF=BF=BDu=D0=AC http://www.hoducoltd.com/flash/index.html > navigation-rules.xml to allow redirection with parameters > --------------------------------------------------------- > > Key: JBSEAM-180 > URL: https://issues.jboss.org/browse/JBSEAM-180 > Project: Seam 2 > Issue Type: Feature Request > Components: JSF Integration > Reporter: Gavin King > Assignee: Gavin King > Fix For: 1.1.1.GA > > > We need to enhance JSF's navigation rules facility to support the followi= ng: > > #{searchAction.search} > searchResults.jsp > > #{searchAction.searchPattern} > > > What I propose to do is introduce a navigation-rules.xml file and reprodu= ce the functionality of JSF navigation rules in Seam (yuck!). -- This message was sent by Atlassian JIRA (v6.3.8#6338) --===============5426345099736213882==-- From issues at jboss.org Wed Nov 12 06:05:29 2014 Content-Type: multipart/mixed; boundary="===============7225861209465728692==" MIME-Version: 1.0 From: Anonymous (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-180) navigation-rules.xml to allow redirection with parameters Date: Wed, 12 Nov 2014 06:05:29 -0500 Message-ID: In-Reply-To: JIRA.12323818.1143320147000@Atlassian.JIRA --===============7225861209465728692== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-180?page=3Dcom.atlassian.jira.= plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13019289#c= omment-13019289 ] = Anonymous commented on JBSEAM-180: ---------------------------------- http://www.quangminhtrade.com/fckeditor/mbtstyle.htmlmbt =EF=BF=BD=EF=BF=BD= =CA=BF=EF=BF=BD=EF=BF=BD=EF=BF=BDw=D0=AC=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF= =BD buy shoes online http://www.g8shutters.com/CSS/mbtjiage.html > navigation-rules.xml to allow redirection with parameters > --------------------------------------------------------- > > Key: JBSEAM-180 > URL: https://issues.jboss.org/browse/JBSEAM-180 > Project: Seam 2 > Issue Type: Feature Request > Components: JSF Integration > Reporter: Gavin King > Assignee: Gavin King > Fix For: 1.1.1.GA > > > We need to enhance JSF's navigation rules facility to support the followi= ng: > > #{searchAction.search} > searchResults.jsp > > #{searchAction.searchPattern} > > > What I propose to do is introduce a navigation-rules.xml file and reprodu= ce the functionality of JSF navigation rules in Seam (yuck!). -- This message was sent by Atlassian JIRA (v6.3.8#6338) --===============7225861209465728692==-- From issues at jboss.org Wed Nov 12 08:07:30 2014 Content-Type: multipart/mixed; boundary="===============6134732783271612025==" MIME-Version: 1.0 From: =?utf-8?q?Vlastimil_Eli=C3=A1=C5=A1_=28JIRA=29_=3Cissues_at_jboss=2Eorg?= =?utf-8?q?=3E?= To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4226) + login-required="true" throws "java.lang.IllegalStateException: long-running conversation already active" after login succeeded Date: Wed, 12 Nov 2014 08:07:30 -0500 Message-ID: In-Reply-To: JIRA.12387618.1244289869000@Atlassian.JIRA --===============6134732783271612025== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-4226?page=3Dcom.atlassian.jir= a.plugin.system.issuetabpanels:all-tabpanel ] Vlastimil Eli=C3=A1=C5=A1 updated JBSEAM-4226: ------------------------------------ Comment: was deleted (was: http://joshadamsrealtor.com/nike/nike-men-air-max-bw_c32http://joshad= amsrealtor.com/nike/nike-men-air-max-bw_c32 Infants U= GG Boots sale [url=3Dhttp://lucidlifestyles.com/ugg/infants-ugg-boots_c2]Infants UGG Boot= s sale[/url]) > + login-required=3D"true" thr= ows "java.lang.IllegalStateException: long-running conversation already act= ive" after login succeeded > -------------------------------------------------------------------------= ---------------------------------------------------------------------------= -------------------- > > Key: JBSEAM-4226 > URL: https://issues.jboss.org/browse/JBSEAM-4226 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.1.2.CR2 > Environment: JBoss 4.2.3 Seam 2.1.2CR2 snapshot > Reporter: Gena > > Hello, > if i use and the view pointed by s:link requires login within the pag= es.xml i get an exception: " java.lang.IllegalStateException: long-running = conversation already active" after login succeeded and before redirect shou= ld occur. = > The problem is present since about 6 weeks. If i change the propagation = to "none" it works, but the request from the link above is proceessed withi= n the current long running conversation and if this conversation timed out,= i always get the conversation timeout redirect an can not simple leave the= current page with one click on the link described above. > Switch to the previous Seam build resolves the problem. > Gena -- This message was sent by Atlassian JIRA (v6.3.8#6338) --===============6134732783271612025==-- From issues at jboss.org Wed Nov 12 08:07:30 2014 Content-Type: multipart/mixed; boundary="===============1758315512185999059==" MIME-Version: 1.0 From: =?utf-8?q?Vlastimil_Eli=C3=A1=C5=A1_=28JIRA=29_=3Cissues_at_jboss=2Eorg?= =?utf-8?q?=3E?= To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-180) navigation-rules.xml to allow redirection with parameters Date: Wed, 12 Nov 2014 08:07:29 -0500 Message-ID: In-Reply-To: JIRA.12323818.1143320147000@Atlassian.JIRA --===============1758315512185999059== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-180?page=3Dcom.atlassian.jira= .plugin.system.issuetabpanels:all-tabpanel ] Vlastimil Eli=C3=A1=C5=A1 updated JBSEAM-180: ----------------------------------- Comment: was deleted (was: http://www.quangminhtrade.com/fckeditor/mbtstyle.htmlmbt =EF=BF=BD=EF= =BF=BD=CA=BF=EF=BF=BD=EF=BF=BD=EF=BF=BDw=D0=AC=EF=BF=BD=EF=BF=BD=EF=BF=BD= =EF=BF=BD buy shoes online http://www.g8shutters.com/CSS/mbtjiage.html) > navigation-rules.xml to allow redirection with parameters > --------------------------------------------------------- > > Key: JBSEAM-180 > URL: https://issues.jboss.org/browse/JBSEAM-180 > Project: Seam 2 > Issue Type: Feature Request > Components: JSF Integration > Reporter: Gavin King > Assignee: Gavin King > Fix For: 1.1.1.GA > > > We need to enhance JSF's navigation rules facility to support the followi= ng: > > #{searchAction.search} > searchResults.jsp > > #{searchAction.searchPattern} > > > What I propose to do is introduce a navigation-rules.xml file and reprodu= ce the functionality of JSF navigation rules in Seam (yuck!). -- This message was sent by Atlassian JIRA (v6.3.8#6338) --===============1758315512185999059==-- From issues at jboss.org Wed Nov 12 08:07:30 2014 Content-Type: multipart/mixed; boundary="===============9158371898666070259==" MIME-Version: 1.0 From: =?utf-8?q?Vlastimil_Eli=C3=A1=C5=A1_=28JIRA=29_=3Cissues_at_jboss=2Eorg?= =?utf-8?q?=3E?= To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-180) navigation-rules.xml to allow redirection with parameters Date: Wed, 12 Nov 2014 08:07:30 -0500 Message-ID: In-Reply-To: JIRA.12323818.1143320147000@Atlassian.JIRA --===============9158371898666070259== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-180?page=3Dcom.atlassian.jira= .plugin.system.issuetabpanels:all-tabpanel ] Vlastimil Eli=C3=A1=C5=A1 updated JBSEAM-180: ----------------------------------- Comment: was deleted (was: http://www.quangminhtrade.com/ads/mbt =D0=AC=EF=BF=BD=EF=BF=BD =EF=BF=BDu=EF=BF=BDu=D0=AC http://www.hoducoltd.com/flash/index.html) > navigation-rules.xml to allow redirection with parameters > --------------------------------------------------------- > > Key: JBSEAM-180 > URL: https://issues.jboss.org/browse/JBSEAM-180 > Project: Seam 2 > Issue Type: Feature Request > Components: JSF Integration > Reporter: Gavin King > Assignee: Gavin King > Fix For: 1.1.1.GA > > > We need to enhance JSF's navigation rules facility to support the followi= ng: > > #{searchAction.search} > searchResults.jsp > > #{searchAction.searchPattern} > > > What I propose to do is introduce a navigation-rules.xml file and reprodu= ce the functionality of JSF navigation rules in Seam (yuck!). -- This message was sent by Atlassian JIRA (v6.3.8#6338) --===============9158371898666070259==-- From issues at jboss.org Wed Nov 12 08:07:30 2014 Content-Type: multipart/mixed; boundary="===============3638444385163192550==" MIME-Version: 1.0 From: =?utf-8?q?Vlastimil_Eli=C3=A1=C5=A1_=28JIRA=29_=3Cissues_at_jboss=2Eorg?= =?utf-8?q?=3E?= To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4226) + login-required="true" throws "java.lang.IllegalStateException: long-running conversation already active" after login succeeded Date: Wed, 12 Nov 2014 08:07:30 -0500 Message-ID: In-Reply-To: JIRA.12387618.1244289869000@Atlassian.JIRA --===============3638444385163192550== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-4226?page=3Dcom.atlassian.jir= a.plugin.system.issuetabpanels:all-tabpanel ] Vlastimil Eli=C3=A1=C5=A1 updated JBSEAM-4226: ------------------------------------ Comment: was deleted (was: http://lucidlifestyles.com/nike/nike-blazer-woven_c88http://lucidlife= styles.com/nike/nike-blazer-woven_c88 cheap Shox NZ [url=3Dhttp://lucidlifestyles.com/nike/shox-nz_c190]cheap Shox NZ[/url]) > + login-required=3D"true" thr= ows "java.lang.IllegalStateException: long-running conversation already act= ive" after login succeeded > -------------------------------------------------------------------------= ---------------------------------------------------------------------------= -------------------- > > Key: JBSEAM-4226 > URL: https://issues.jboss.org/browse/JBSEAM-4226 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.1.2.CR2 > Environment: JBoss 4.2.3 Seam 2.1.2CR2 snapshot > Reporter: Gena > > Hello, > if i use and the view pointed by s:link requires login within the pag= es.xml i get an exception: " java.lang.IllegalStateException: long-running = conversation already active" after login succeeded and before redirect shou= ld occur. = > The problem is present since about 6 weeks. If i change the propagation = to "none" it works, but the request from the link above is proceessed withi= n the current long running conversation and if this conversation timed out,= i always get the conversation timeout redirect an can not simple leave the= current page with one click on the link described above. > Switch to the previous Seam build resolves the problem. > Gena -- This message was sent by Atlassian JIRA (v6.3.8#6338) --===============3638444385163192550==-- From issues at jboss.org Mon Nov 17 14:03:39 2014 Content-Type: multipart/mixed; boundary="===============4998520007103790535==" MIME-Version: 1.0 From: Daniel Coughlin (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org - Seam Date: Mon, 17 Nov 2014 14:03:39 -0500 Message-ID: In-Reply-To: JIRA.12557570.1416250974000@Atlassian.JIRA --===============4998520007103790535== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Daniel Coughlin created JBSEAM-5141: --------------------------------------- Summary: 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 The following broken link is currently listed against this project on www.j= boss.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 re= flected 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) --===============4998520007103790535==-- From issues at jboss.org Tue Nov 18 04:22:39 2014 Content-Type: multipart/mixed; boundary="===============6318431830342684674==" MIME-Version: 1.0 From: Marek Novotny (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org - Seam Date: Tue, 18 Nov 2014 04:22:39 -0500 Message-ID: In-Reply-To: JIRA.12557570.1416250974000@Atlassian.JIRA --===============6318431830342684674== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-5141?page=3Dcom.atlassian.jira= .plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13020678#= comment-13020678 ] = Marek Novotny commented on JBSEAM-5141: --------------------------------------- The links was changed after seamframework.org was restored from backup to n= ew static web (that web doesn't use Magnolia AFAIK), so new links are: http://www.seamframework.org/Seam2/Documentation.html - Documentation http://www.seamframework.org/Documentation/KnowledgeBase.html - Community https://developer.jboss.org/en/seam - User Forum http://www.seamframework.org/Downloads.html - Download > 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 > > 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.or= g 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 proje= ct's Magnolia page. -- This message was sent by Atlassian JIRA (v6.3.8#6338) --===============6318431830342684674==-- From issues at jboss.org Tue Nov 18 04:23:39 2014 Content-Type: multipart/mixed; boundary="===============2033423967361682742==" MIME-Version: 1.0 From: Marek Novotny (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org - Seam Date: Tue, 18 Nov 2014 04:23:39 -0500 Message-ID: In-Reply-To: JIRA.12557570.1416250974000@Atlassian.JIRA --===============2033423967361682742== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-5141?page=3Dcom.atlassian.jira= .plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13020678#= comment-13020678 ] = Marek Novotny edited comment on JBSEAM-5141 at 11/18/14 4:23 AM: ----------------------------------------------------------------- The links was changed after seamframework.org was restored from backup to n= ew static web (that web doesn't use Magnolia AFAIK), so new links are: http://www.seamframework.org/Seam2/Documentation.html - Documentation http://www.seamframework.org/Documentation/KnowledgeBase.html - Community https://developer.jboss.org/en/seam - User Forum http://www.seamframework.org/Seam2/Downloads.html - Download was (Author: manarh): The links was changed after seamframework.org was restored from backup to n= ew static web (that web doesn't use Magnolia AFAIK), so new links are: http://www.seamframework.org/Seam2/Documentation.html - Documentation http://www.seamframework.org/Documentation/KnowledgeBase.html - Community https://developer.jboss.org/en/seam - User Forum http://www.seamframework.org/Downloads.html - Download > 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 > > 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.or= g 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 proje= ct's Magnolia page. -- This message was sent by Atlassian JIRA (v6.3.8#6338) --===============2033423967361682742==-- From issues at jboss.org Tue Nov 18 04:23:40 2014 Content-Type: multipart/mixed; boundary="===============8488389802513121833==" MIME-Version: 1.0 From: Marek Novotny (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org - Seam Date: Tue, 18 Nov 2014 04:23:39 -0500 Message-ID: In-Reply-To: JIRA.12557570.1416250974000@Atlassian.JIRA --===============8488389802513121833== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-5141?page=3Dcom.atlassian.jir= a.plugin.system.issuetabpanels:all-tabpanel ] Marek Novotny reassigned JBSEAM-5141: ------------------------------------- Assignee: Marek Novotny > 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.or= g 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 proje= ct's Magnolia page. -- This message was sent by Atlassian JIRA (v6.3.8#6338) --===============8488389802513121833==-- From issues at jboss.org Wed Nov 19 05:19:39 2014 Content-Type: multipart/mixed; boundary="===============6325182947984218421==" MIME-Version: 1.0 From: Robert Becker (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5142) s:link fragment parameter ignored Date: Wed, 19 Nov 2014 05:19:39 -0500 Message-ID: In-Reply-To: JIRA.12557668.1416392323000@Atlassian.JIRA --===============6325182947984218421== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-5142?page=3Dcom.atlassian.jir= a.plugin.system.issuetabpanels:all-tabpanel ] Robert Becker updated JBSEAM-5142: ---------------------------------- Description: = Since upgrading to Seam 2.3.x (from 2.2.2), the s:link fragment attribute i= s ignored. = Code example: {code:xml} {code} Produces the following href attribute: https://[...]/cms/home.xhtml?samsArt= icleComponent.page=3D0 I noticed changes in org.jboss.seam.ui.util.ViewUrlBuilder.java since 2.2.2: {code:title=3DSeam 2.2.2} @Override public String getEncodedUrl() { return FacesContext.getCurrentInstance().getExternalContext().encod= eActionURL(super.getEncodedUrl()); } {code} {code:title=3DSeam 2.3.1} @Override public String getEncodedUrl() = { FacesContext facesContext =3D FacesContext.getCurrentInstance(); return facesContext.getApplication().getViewHandler().getBookmarkabl= eURL(facesContext, this.viewId, getParametersAsMap(getParameters()), false); } {code} In Seam 2.2.2, super.getEncodedUrl() took care of including the fragment. I= guess this got lost when switching to the new method. was: Since upgrading to Seam 2.3.x (from 2.2.2), the s:link fragment attribute i= s ignored. = Code example: {code:xml} {code} Produces the following href attribute: https://[...]/cms/home.xhtml?samsArt= icleComponent.page=3D0 I noticed changes in org.jboss.seam.ui.util.ViewUrlBuilder.java since 2.2.2: {code:title=3DSeam 2.2.2} @Override public String getEncodedUrl() { return FacesContext.getCurrentInstance().getExternalContext().encod= eActionURL(super.getEncodedUrl()); } {code} {code:title=3DSeam 2.3.1} @Override public String getEncodedUrl() = { FacesContext facesContext =3D FacesContext.getCurrentInstance(); return facesContext.getApplication().getViewHandler().getBookmarkabl= eURL(facesContext, this.viewId, getParametersAsMap(getParameters()), false); } {code} In Seam 2.2.2, super.getEncodedUrl() took care of including the fragment. I= guess this got lost when switching to the new method. > s:link fragment parameter ignored > --------------------------------- > > Key: JBSEAM-5142 > URL: https://issues.jboss.org/browse/JBSEAM-5142 > Project: Seam 2 > Issue Type: Bug > Components: JSF Controls > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3.x (from 2.2.2), the s:link fragment attribute= is ignored. = > Code example: > {code:xml} > > > > {code} > Produces the following href attribute: https://[...]/cms/home.xhtml?samsA= rticleComponent.page=3D0 > I noticed changes in org.jboss.seam.ui.util.ViewUrlBuilder.java since 2.2= .2: > {code:title=3DSeam 2.2.2} > @Override > public String getEncodedUrl() { > return FacesContext.getCurrentInstance().getExternalContext().enc= odeActionURL(super.getEncodedUrl()); > } > {code} > {code:title=3DSeam 2.3.1} > @Override > public String getEncodedUrl() = > { > FacesContext facesContext =3D FacesContext.getCurrentInstance(); > return facesContext.getApplication().getViewHandler().getBookmarka= bleURL(facesContext, this.viewId, getParametersAsMap(getParameters()), fals= e); > } > {code} > In Seam 2.2.2, super.getEncodedUrl() took care of including the fragment.= I guess this got lost when switching to the new method. -- This message was sent by Atlassian JIRA (v6.3.8#6338) --===============6325182947984218421==-- From issues at jboss.org Wed Nov 19 05:19:39 2014 Content-Type: multipart/mixed; boundary="===============1418017217922102510==" MIME-Version: 1.0 From: Robert Becker (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5142) s:link fragment parameter ignored Date: Wed, 19 Nov 2014 05:19:39 -0500 Message-ID: In-Reply-To: JIRA.12557668.1416392323000@Atlassian.JIRA --===============1418017217922102510== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Robert Becker created JBSEAM-5142: ------------------------------------- Summary: s:link fragment parameter ignored Key: JBSEAM-5142 URL: https://issues.jboss.org/browse/JBSEAM-5142 Project: Seam 2 Issue Type: Bug Components: JSF Controls Affects Versions: 2.3.1.Final Reporter: Robert Becker Since upgrading to Seam 2.3.x (from 2.2.2), the s:link fragment attribute i= s ignored. = Code example: {code:xml} {code} Produces the following href attribute: https://[...]/cms/home.xhtml?samsArt= icleComponent.page=3D0 I noticed changes in org.jboss.seam.ui.util.ViewUrlBuilder.java since 2.2.2: {code:title=3DSeam 2.2.2} @Override public String getEncodedUrl() { return FacesContext.getCurrentInstance().getExternalContext().encod= eActionURL(super.getEncodedUrl()); } {code} {code:title=3DSeam 2.3.1} @Override public String getEncodedUrl() = { FacesContext facesContext =3D FacesContext.getCurrentInstance(); return facesContext.getApplication().getViewHandler().getBookmarkabl= eURL(facesContext, this.viewId, getParametersAsMap(getParameters()), false); } {code} In Seam 2.2.2, super.getEncodedUrl() took care of including the fragment. I= guess this got lost when switching to the new method. -- This message was sent by Atlassian JIRA (v6.3.8#6338) --===============1418017217922102510==-- From issues at jboss.org Wed Nov 19 05:31:40 2014 Content-Type: multipart/mixed; boundary="===============1273991560604778485==" MIME-Version: 1.0 From: Robert Becker (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5142) s:link fragment parameter ignored Date: Wed, 19 Nov 2014 05:31:40 -0500 Message-ID: In-Reply-To: JIRA.12557668.1416392323000@Atlassian.JIRA --===============1273991560604778485== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-5142?page=3Dcom.atlassian.jira= .plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13021068#= comment-13021068 ] = Robert Becker commented on JBSEAM-5142: --------------------------------------- I just switched to the new h:link tag which also supports the fragment attr= ibute and works as expected. > s:link fragment parameter ignored > --------------------------------- > > Key: JBSEAM-5142 > URL: https://issues.jboss.org/browse/JBSEAM-5142 > Project: Seam 2 > Issue Type: Bug > Components: JSF Controls > Affects Versions: 2.3.1.Final > Reporter: Robert Becker > > Since upgrading to Seam 2.3.x (from 2.2.2), the s:link fragment attribute= is ignored. = > Code example: > {code:xml} > > > > {code} > Produces the following href attribute: https://[...]/cms/home.xhtml?samsA= rticleComponent.page=3D0 > I noticed changes in org.jboss.seam.ui.util.ViewUrlBuilder.java since 2.2= .2: > {code:title=3DSeam 2.2.2} > @Override > public String getEncodedUrl() { > return FacesContext.getCurrentInstance().getExternalContext().enc= odeActionURL(super.getEncodedUrl()); > } > {code} > {code:title=3DSeam 2.3.1} > @Override > public String getEncodedUrl() = > { > FacesContext facesContext =3D FacesContext.getCurrentInstance(); > return facesContext.getApplication().getViewHandler().getBookmarka= bleURL(facesContext, this.viewId, getParametersAsMap(getParameters()), fals= e); > } > {code} > In Seam 2.2.2, super.getEncodedUrl() took care of including the fragment.= I guess this got lost when switching to the new method. -- This message was sent by Atlassian JIRA (v6.3.8#6338) --===============1273991560604778485==-- From issues at jboss.org Wed Nov 26 04:31:39 2014 Content-Type: multipart/mixed; boundary="===============5401737662711678031==" MIME-Version: 1.0 From: Robert Becker (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null Date: Wed, 26 Nov 2014 04:31:39 -0500 Message-ID: In-Reply-To: JIRA.12558207.1416994274000@Atlassian.JIRA --===============5401737662711678031== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Robert Becker created JBSEAM-5143: ------------------------------------- Summary: Random IllegalArgumentException: Stack must not be nu= ll 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 -- This message was sent by Atlassian JIRA (v6.3.8#6338) --===============5401737662711678031==-- From issues at jboss.org Wed Nov 26 04:38:39 2014 Content-Type: multipart/mixed; boundary="===============5131210560866333360==" MIME-Version: 1.0 From: Robert Becker (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null Date: Wed, 26 Nov 2014 04:38:39 -0500 Message-ID: In-Reply-To: JIRA.12558207.1416994274000@Atlassian.JIRA --===============5131210560866333360== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-5143?page=3Dcom.atlassian.jir= a.plugin.system.issuetabpanels:all-tabpanel ] Robert Becker updated JBSEAM-5143: ---------------------------------- Description: = 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 n= ot be null". Perhaps this is related to No long-running conversations - Ill= egalArgumentException: Stack must not be null, but I really don't know what= I am doing wrong. 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 100 requests) when navigating= between pages, submitting forms, switching (RichFaces) tabs and so on. I believe restarting glassfish and/or enabling client side state saving red= uces the frequency of the issue whereas it seems to happen more often after= multiple successive redeployments during development. I have also posted this on stackoverflow (http://stackoverflow.com/question= s/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but ha= ve 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 > 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". Perhaps this is related to No long-running conversations - I= llegalArgumentException: Stack must not be null, but I really don't know wh= at I am doing wrong. The application worked fine for several years until no= w. > The full stack trace is listed here: http://pastebin.com/RjLndvnE > The exception randomly happens (in about 1 of 100 requests) when navigati= ng between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving r= educes the frequency of the issue whereas it seems to happen more often aft= er multiple successive redeployments during development. > I have also posted this on stackoverflow (http://stackoverflow.com/questi= ons/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) --===============5131210560866333360==-- From issues at jboss.org Wed Nov 26 04:38:39 2014 Content-Type: multipart/mixed; boundary="===============0241749247190964955==" MIME-Version: 1.0 From: Robert Becker (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null Date: Wed, 26 Nov 2014 04:38:39 -0500 Message-ID: In-Reply-To: JIRA.12558207.1416994274000@Atlassian.JIRA --===============0241749247190964955== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-5143?page=3Dcom.atlassian.jir= a.plugin.system.issuetabpanels:all-tabpanel ] Robert Becker updated JBSEAM-5143: ---------------------------------- Description: = 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 n= ot 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 100 requests) when navigating= between pages, submitting forms, switching (RichFaces) tabs and so on. I believe restarting glassfish and/or enabling client side state saving red= uces the frequency of the issue whereas it seems to happen more often after= multiple successive redeployments during development. I have also posted this on stackoverflow (http://stackoverflow.com/question= s/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but ha= ve 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 was: 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 n= ot be null". Perhaps this is related to No long-running conversations - Ill= egalArgumentException: Stack must not be null, but I really don't know what= I am doing wrong. 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 100 requests) when navigating= between pages, submitting forms, switching (RichFaces) tabs and so on. I believe restarting glassfish and/or enabling client side state saving red= uces the frequency of the issue whereas it seems to happen more often after= multiple successive redeployments during development. I have also posted this on stackoverflow (http://stackoverflow.com/question= s/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but ha= ve 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 > 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 100 requests) when navigati= ng between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving r= educes the frequency of the issue whereas it seems to happen more often aft= er multiple successive redeployments during development. > I have also posted this on stackoverflow (http://stackoverflow.com/questi= ons/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) --===============0241749247190964955==-- From issues at jboss.org Wed Nov 26 04:42:39 2014 Content-Type: multipart/mixed; boundary="===============7623688893228166631==" MIME-Version: 1.0 From: Robert Becker (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null Date: Wed, 26 Nov 2014 04:42:39 -0500 Message-ID: In-Reply-To: JIRA.12558207.1416994274000@Atlassian.JIRA --===============7623688893228166631== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-5143?page=3Dcom.atlassian.jir= a.plugin.system.issuetabpanels:all-tabpanel ] Robert Becker updated JBSEAM-5143: ---------------------------------- Description: = 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 n= ot 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 red= uces the frequency of the issue whereas it seems to happen more often after= multiple successive redeployments during development. Sadly, due to sever= al dependencies this is already in production but happens far less often th= ere, but it still happens daily according to the server logs. I have also posted this on stackoverflow (http://stackoverflow.com/question= s/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but ha= ve 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 was: 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 n= ot 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 100 requests) when navigating= between pages, submitting forms, switching (RichFaces) tabs and so on. I believe restarting glassfish and/or enabling client side state saving red= uces the frequency of the issue whereas it seems to happen more often after= multiple successive redeployments during development. I have also posted this on stackoverflow (http://stackoverflow.com/question= s/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but ha= ve 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 > 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 navigati= ng between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving r= educes the frequency of the issue whereas it seems to happen more often aft= er multiple successive redeployments during development. Sadly, due to sev= eral 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/questi= ons/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) --===============7623688893228166631==-- From issues at jboss.org Wed Nov 26 12:25:39 2014 Content-Type: multipart/mixed; boundary="===============7399426754169646001==" MIME-Version: 1.0 From: Robert Becker (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null Date: Wed, 26 Nov 2014 12:25:39 -0500 Message-ID: In-Reply-To: JIRA.12558207.1416994274000@Atlassian.JIRA --===============7399426754169646001== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-5143?page=3Dcom.atlassian.jira= .plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13023363#= comment-13023363 ] = Robert Becker commented on JBSEAM-5143: --------------------------------------- After adding some more detailed information to the exception reports (esp. = request parameters) I have noticed that in at least one case the conversati= on id parameter was definitely present in the list of request parameters. E= ven though, the conversation stack was null. Could it be that the conversat= ion is accessed before the seam manager is properly initialized? Here is the stack trace belonging to said exception: http://pastebin.com/3k= w1W49Z > 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 navigati= ng between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving r= educes the frequency of the issue whereas it seems to happen more often aft= er multiple successive redeployments during development. Sadly, due to sev= eral 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/questi= ons/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) --===============7399426754169646001==-- From issues at jboss.org Fri Nov 28 05:12:39 2014 Content-Type: multipart/mixed; boundary="===============3511871754325255087==" MIME-Version: 1.0 From: Robert Becker (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null Date: Fri, 28 Nov 2014 05:12:39 -0500 Message-ID: In-Reply-To: JIRA.12558207.1416994274000@Atlassian.JIRA --===============3511871754325255087== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-5143?page=3Dcom.atlassian.jira= .plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13023795#= comment-13023795 ] = Robert Becker commented on JBSEAM-5143: --------------------------------------- I set the seam log level to debug and perhaps found a clue. This is a reque= st on a page which lead to said exception: Information: 2014-11-28 10:54:46,270 DEBUG - >>> Begin JSF request for /SAM= S/ma/index.xhtml Information: 2014-11-28 10:41:31,149 DEBUG - beginning transaction prior to= phase: RESTORE_VIEW 1 Information: 2014-11-28 10:41:31,149 DEBUG - beginning JTA transaction Information: 2014-11-28 10:41:31,150 DEBUG - committing transaction after p= hase: RESTORE_VIEW 1 Information: 2014-11-28 10:41:31,150 DEBUG - committing JTA transaction Information: 2014-11-28 10:41:31,150 DEBUG - beginning transaction prior to= phase: RENDER_RESPONSE 6 Information: 2014-11-28 10:41:31,150 DEBUG - beginning JTA transaction Information: 2014-11-28 10:41:31,150 DEBUG - trying to inject with hierarch= ical context search: samsDatabase Information: 2014-11-28 10:41:31,151 DEBUG - created seam managed persisten= ce context from EntityManagerFactory Information: 2014-11-28 10:41:31,151 DEBUG - trying to inject with hierarch= ical context search: identity Information: 2014-11-28 10:41:31,151 DEBUG - trying to inject with hierarch= ical context search: identity Information: Hibernate: /* SELECT [...] Information: 2014-11-28 10:41:31,154 DEBUG - Beginning long-running convers= ation Information: 2014-11-28 10:41:31,158 DEBUG - reading exception mappings fro= m /WEB-INF/pages.xml Information: 2014-11-28 10:41:31,161 ERROR - swallowing exception javax.el.ELException: java.lang.IllegalArgumentException: Stack must not be= null And this is a request for the same page which was processed without error: Information: 2014-11-28 10:54:46,271 DEBUG - beginning transaction prior to= phase: RESTORE_VIEW 1 Information: 2014-11-28 10:54:46,271 DEBUG - beginning JTA transaction Information: 2014-11-28 10:54:46,273 DEBUG - isPageContextActive is null Information: 2014-11-28 10:54:46,273 DEBUG - Page Context will be lazilly c= reated Information: 2014-11-28 10:54:46,274 DEBUG - No stored conversation Information: 2014-11-28 10:54:46,274 DEBUG - committing transaction after p= hase: RESTORE_VIEW 1 Information: 2014-11-28 10:54:46,274 DEBUG - committing JTA transaction Information: 2014-11-28 10:54:46,275 DEBUG - beginning transaction prior to= phase: RENDER_RESPONSE 6 Information: 2014-11-28 10:54:46,275 DEBUG - beginning JTA transaction Information: 2014-11-28 10:54:46,369 DEBUG - trying to inject with hierarch= ical context search: samsDatabase Information: 2014-11-28 10:54:46,371 DEBUG - created seam managed persisten= ce context from EntityManagerFactory Information: 2014-11-28 10:54:46,371 DEBUG - trying to inject with hierarch= ical context search: identity Information: Hibernate: /* SELECT [...] Information: 2014-11-28 10:54:46,546 DEBUG - trying to inject with hierarch= ical context search: samsDatabase Information: 2014-11-28 10:54:46,546 DEBUG - trying to inject with hierarch= ical context search: identity ... and so on and later: "Beginning long-running conversation" (as expected) The main difference in the latter request is that "isPageContextActive is n= ull" is printed out by Contexts.isPageContextActive(). The method is commen= ted with "Is PageContext set? If not, it is lazily created in case of RESTO= RE_VIEW is processing. This is a requirement for starting CONVERSATION - JS= F2 change". Could it be that one condition here is not applied correctly? > 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 navigati= ng between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving r= educes the frequency of the issue whereas it seems to happen more often aft= er multiple successive redeployments during development. Sadly, due to sev= eral 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/questi= ons/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) --===============3511871754325255087==-- From issues at jboss.org Fri Nov 28 05:19:39 2014 Content-Type: multipart/mixed; boundary="===============5540847232715813750==" MIME-Version: 1.0 From: Robert Becker (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null Date: Fri, 28 Nov 2014 05:19:39 -0500 Message-ID: In-Reply-To: JIRA.12558207.1416994274000@Atlassian.JIRA --===============5540847232715813750== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-5143?page=3Dcom.atlassian.jira= .plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13023797#= comment-13023797 ] = Robert Becker commented on JBSEAM-5143: --------------------------------------- I am currently running the latest 2.3. nightly build which did not bring an= y improvement for this issue. I also removed Omnifaces completely to reduce the pool of possible causes w= hich also changed nothing. > 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 navigati= ng between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving r= educes the frequency of the issue whereas it seems to happen more often aft= er multiple successive redeployments during development. Sadly, due to sev= eral 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/questi= ons/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) --===============5540847232715813750==-- From issues at jboss.org Fri Nov 28 07:55:39 2014 Content-Type: multipart/mixed; boundary="===============2371325984120670919==" MIME-Version: 1.0 From: Robert Becker (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null Date: Fri, 28 Nov 2014 07:55:39 -0500 Message-ID: In-Reply-To: JIRA.12558207.1416994274000@Atlassian.JIRA --===============2371325984120670919== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-5143?page=3Dcom.atlassian.jira= .plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13023836#= comment-13023836 ] = Robert Becker commented on JBSEAM-5143: --------------------------------------- I noticed something else being quirky: I have an issue with a certain bean = which worked fine with Seam 2.2.x and has a prepare method annotated with: @Create @Begin(nested =3D true, flushMode =3D FlushModeType.MANUAL) public void prepare() { ... } The bean is initialized simply by being referenced in the view (which is li= nked via s:link from the main conversation view). The problem here is that = the new conversation id it not propagated properly when submitting a form w= ithin the view using an h:commandButton. Instead, the parent conversation i= d is propagated and the bean with its child conversation is recreated in th= e next request. I tested the same action with an s:button, which works, tho= ugh. Perhaps this is related to the main issue above. > 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 navigati= ng between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving r= educes the frequency of the issue whereas it seems to happen more often aft= er multiple successive redeployments during development. Sadly, due to sev= eral 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/questi= ons/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) --===============2371325984120670919==-- From issues at jboss.org Fri Nov 28 08:06:39 2014 Content-Type: multipart/mixed; boundary="===============8341920896998615145==" MIME-Version: 1.0 From: Robert Becker (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null Date: Fri, 28 Nov 2014 08:06:39 -0500 Message-ID: In-Reply-To: JIRA.12558207.1416994274000@Atlassian.JIRA --===============8341920896998615145== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-5143?page=3Dcom.atlassian.jira= .plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13023837#= comment-13023837 ] = Robert Becker commented on JBSEAM-5143: --------------------------------------- Disabling partial state saving does not prevent the IllegalArgumentExceptio= n to occur. > 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 navigati= ng between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving r= educes the frequency of the issue whereas it seems to happen more often aft= er multiple successive redeployments during development. Sadly, due to sev= eral 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/questi= ons/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) --===============8341920896998615145==-- From issues at jboss.org Fri Nov 28 08:19:39 2014 Content-Type: multipart/mixed; boundary="===============5283202505584467579==" MIME-Version: 1.0 From: Robert Becker (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null Date: Fri, 28 Nov 2014 08:19:39 -0500 Message-ID: In-Reply-To: JIRA.12558207.1416994274000@Atlassian.JIRA --===============5283202505584467579== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-5143?page=3Dcom.atlassian.jira= .plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13023836#= comment-13023836 ] = Robert Becker edited comment on JBSEAM-5143 at 11/28/14 8:19 AM: ----------------------------------------------------------------- I noticed something else being quirky: I have an issue with a certain bean = which worked fine with Seam 2.2.x and has a prepare method annotated with: @Create @Begin(nested =3D true, flushMode =3D FlushModeType.MANUAL) public void prepare() { ... } The bean is initialized simply by being referenced in the view (which is li= nked via s:link from the main conversation view). The problem here is that = the new conversation id it not propagated properly when submitting a form w= ithin the view using an h:commandButton. Instead, the parent conversation i= d is propagated and the bean with its child conversation is recreated in th= e next request. I tested the same action with an s:button, which works, tho= ugh. Perhaps this is related to the main issue above. The generated html form has an action parameter containing the original (pa= rent) id which got (correctly) appended to the url when redirect to the new= view. Normally it should have been removed from the form action and the co= rrect one should be added as hidden input field. = was (Author: r0b3n): I noticed something else being quirky: I have an issue with a certain bean = which worked fine with Seam 2.2.x and has a prepare method annotated with: @Create @Begin(nested =3D true, flushMode =3D FlushModeType.MANUAL) public void prepare() { ... } The bean is initialized simply by being referenced in the view (which is li= nked via s:link from the main conversation view). The problem here is that = the new conversation id it not propagated properly when submitting a form w= ithin the view using an h:commandButton. Instead, the parent conversation i= d is propagated and the bean with its child conversation is recreated in th= e next request. I tested the same action with an s:button, which works, tho= ugh. Perhaps this is related to the main issue above. > 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 navigati= ng between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving r= educes the frequency of the issue whereas it seems to happen more often aft= er multiple successive redeployments during development. Sadly, due to sev= eral 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/questi= ons/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) --===============5283202505584467579==-- From issues at jboss.org Sun Nov 30 07:01:39 2014 Content-Type: multipart/mixed; boundary="===============6653760741026149327==" MIME-Version: 1.0 From: Robert Becker (JIRA) To: seam-issues at lists.jboss.org Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random IllegalArgumentException: Stack must not be null Date: Sun, 30 Nov 2014 07:01:39 -0500 Message-ID: In-Reply-To: JIRA.12558207.1416994274000@Atlassian.JIRA --===============6653760741026149327== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/JBSEAM-5143?page=3Dcom.atlassian.jira= .plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13023936#= comment-13023936 ] = Robert Becker commented on JBSEAM-5143: --------------------------------------- The whole problem seems strongly related to https://issues.jboss.org/browse= /JBSEAM-4898. Could it be that changes to Mojarra 2.1.x caused some regress= ion? > 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 navigati= ng between pages, submitting forms, switching (RichFaces) tabs and so on. > I believe restarting glassfish and/or enabling client side state saving r= educes the frequency of the issue whereas it seems to happen more often aft= er multiple successive redeployments during development. Sadly, due to sev= eral 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/questi= ons/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) --===============6653760741026149327==--