[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:
---------------------------------------
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 regression?
> 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, 5 months
[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 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 = true, flushMode = FlushModeType.MANUAL)
public void prepare() { ... }
The bean is initialized simply by being referenced in the view (which is linked 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 within the view using an h:commandButton. Instead, the parent conversation id is propagated and the bean with its child conversation is recreated in the next request. I tested the same action with an s:button, which works, though. Perhaps this is related to the main issue above.
The generated html form has an action parameter containing the original (parent) 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 correct 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 = true, flushMode = FlushModeType.MANUAL)
public void prepare() { ... }
The bean is initialized simply by being referenced in the view (which is linked 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 within the view using an h:commandButton. Instead, the parent conversation id is propagated and the bean with its child conversation is recreated in the next request. I tested the same action with an s:button, which works, though. 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 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, 5 months
[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:
---------------------------------------
Disabling partial state saving does not prevent the IllegalArgumentException 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 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, 5 months
[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 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 = true, flushMode = FlushModeType.MANUAL)
public void prepare() { ... }
The bean is initialized simply by being referenced in the view (which is linked 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 within the view using an h:commandButton. Instead, the parent conversation id is propagated and the bean with its child conversation is recreated in the next request. I tested the same action with an s:button, which works, though. 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 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, 5 months
[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 am currently running the latest 2.3. nightly build which did not bring any improvement for this issue.
I also removed Omnifaces completely to reduce the pool of possible causes which 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 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, 5 months
[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 set the seam log level to debug and perhaps found a clue. This is a request on a page which lead to said exception:
Information: 2014-11-28 10:54:46,270 DEBUG - >>> Begin JSF request for /SAMS/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 phase: 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 hierarchical context search: samsDatabase
Information: 2014-11-28 10:41:31,151 DEBUG - created seam managed persistence context from EntityManagerFactory
Information: 2014-11-28 10:41:31,151 DEBUG - trying to inject with hierarchical context search: identity
Information: 2014-11-28 10:41:31,151 DEBUG - trying to inject with hierarchical context search: identity
Information: Hibernate: /* SELECT [...]
Information: 2014-11-28 10:41:31,154 DEBUG - Beginning long-running conversation
Information: 2014-11-28 10:41:31,158 DEBUG - reading exception mappings from /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 created
Information: 2014-11-28 10:54:46,274 DEBUG - No stored conversation
Information: 2014-11-28 10:54:46,274 DEBUG - committing transaction after phase: 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 hierarchical context search: samsDatabase
Information: 2014-11-28 10:54:46,371 DEBUG - created seam managed persistence context from EntityManagerFactory
Information: 2014-11-28 10:54:46,371 DEBUG - trying to inject with hierarchical context search: identity
Information: Hibernate: /* SELECT [...]
Information: 2014-11-28 10:54:46,546 DEBUG - trying to inject with hierarchical context search: samsDatabase
Information: 2014-11-28 10:54:46,546 DEBUG - trying to inject with hierarchical 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 null" is printed out by Contexts.isPageContextActive(). The method is commented with "Is PageContext set? If not, it is lazily created in case of RESTORE_VIEW is processing. This is a requirement for starting CONVERSATION - JSF2 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 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, 5 months
[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:
---------------------------------------
After adding some more detailed information to the exception reports (esp. request parameters) I have noticed that in at least one case the conversation id parameter was definitely present in the list of request parameters. Even though, the conversation stack was null. Could it be that the conversation is accessed before the seam manager is properly initialized?
Here is the stack trace belonging to said exception: http://pastebin.com/3kw1W49Z
> 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, 5 months
[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 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 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
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 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 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.
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
> 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, 5 months
[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 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 not be null". Perhaps this is related to No long-running conversations - IllegalArgumentException: 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 reduces 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/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
> 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 - IllegalArgumentException: 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 reduces 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/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, 5 months
[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 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 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 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.
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
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 not be null". Perhaps this is related to No long-running conversations - IllegalArgumentException: 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 reduces 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/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
> 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 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.
> 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, 5 months