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

Robert Becker (JIRA) issues at jboss.org
Thu Dec 4 05:27:39 EST 2014


    [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025102#comment-13025102 ] 

Robert Becker commented on JBSEAM-5143:
---------------------------------------

Many thanks for your insight.

> 1. Am I right that you have enabled client state saving ? This is not recommended setting.
I just had it enabled for a day or two to see if it makes any difference, which it doesn't. Currently I am using partial server side state saving which also is my preferred configuration.

> I would guess it is not a random failure, but there is some point in previous navigation or a step which prevents the continuation of using/restoring conversation - like bad conversation usage.
The strange thing is that it even happens using s:links with propagation="none" and in very different parts of the application. For example yesterday I worked on a specific view being referenced which such a link from the main menu. I used the link dozens of times where it worked fine, then suddenly the exception occurred and afterwards it worked normally again.

> Honestly I can't say anything more without seeing more application code.
If I could just narrow it down to what to show you. 

> And I would recommend to try deployment also on JBoss AS 7 or EAP 6.3.x for comparison.
I had that in mind, too. I will try that.

> Random IllegalArgumentException: Stack must not be null
> -------------------------------------------------------
>
>                 Key: JBSEAM-5143
>                 URL: https://issues.jboss.org/browse/JBSEAM-5143
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.1.Final
>            Reporter: Robert Becker
>
> Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now.
> The full stack trace is listed here: http://pastebin.com/RjLndvnE
> The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.
> I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.  Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs.
> I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.
> Besides Seam 2.3, the following libraries are used:
> - Mojarra 2.1.29
> - RF 4.5 (exception also occurred with 4.3.x)
> - Omnifaces 1.10RC1 (will upgrade to 2.0)
> - Primefaces 5.1



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)


More information about the seam-issues mailing list