Databases
StackOverflow2013
Postsdbo
PO
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The same problem has been reported on the IceFaces forums:</p> <ul> <li><a href="http://www.icefaces.org/JForum/posts/list/7752.page" rel="nofollow">http://www.icefaces.org/JForum/posts/list/7752.page</a></li> <li><a href="http://www.icefaces.org/JForum/posts/list/18154.page" rel="nofollow">http://www.icefaces.org/JForum/posts/list/18154.page</a></li> </ul> <p>The proposed solutions were:</p> <blockquote> <p>This was happening for us once we set the asynchronous mode off</p> <pre><code>&lt;!-- Specifies to the ICEfaces framework that synchronous update mode is to be used. By default, ICEfaces uses asynchronous update mode to support server-initiated updates (AJAX push). Setting to true will enable synchronous update mode and disable AJAX push features. --&gt; &lt;context-param&gt; &lt;param-name&gt;com.icesoft.faces.synchronousUpdate&lt;/param-name&gt; &lt;param-value&gt;true&lt;/param-value&gt; &lt;/context-param&gt; </code></pre> <p>When this was false we got the nice little session timed out message. When this was true, session timeout behaviour was stack trace.</p> </blockquote> <p>and</p> <blockquote> <p>In the meantime I've switched from ICEfaces 1.8.2 to what's in the svn repository at the moment (1.8.3+). And the behavior has changed. There is no crash anymore. </p> </blockquote> <p>As to your statement that you aren't using the session anywhere, the stacktrace tells that it is attempting to create a session scoped managed bean when this exception was thrown. So you are definitely using the session :)</p> <hr> <p><strong>Update</strong> as per the comments: You should indeed definitely not assign the (request based!!) <code>FacesContext</code> as a <code>static</code> variable. Also, injecting of other beans needs to be taken place by <code>&lt;managed-property&gt;</code> in <code>faces-config.xml</code>. Otherwise it isn't "injecting" at all, but just <em>manually</em> accessing the other bean. With injecting, you're letting JSF do the work to set the other bean as a property of the current bean. An example can be found <a href="http://balusc.blogspot.com/2006/06/communication-in-jsf.html#InjectingManagedBeansInEachOther" rel="nofollow">here</a>.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload