openwebbeans-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Andraschko <>
Subject Re: How OWB stores @SessionScoped beans in Web app?
Date Fri, 18 Feb 2011 19:34:12 GMT

I also tried it without msm/clustering but with activated OWB failover.
 AFAICS the ViewExpiredException only occurs with activated OWB failover and msm (Maybe it
also occurs with default tomcat clustering?)

Also note: The ViewExpiredException occurs on the first request without any failover or loadbalacing!

Here is the exception:

javax.faces.application.ViewExpiredException: /test.xhtmlNo saved view state could be found
for the view identifier: /test.xhtml
    at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(
    at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(
    at org.apache.myfaces.lifecycle.LifecycleImpl.execute(
    at javax.faces.webapp.FacesServlet.service(
    at org.apache.myfaces.webapp.MyFacesServlet.service(
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(
    at org.apache.catalina.core.StandardWrapperValve.invoke(
    at org.apache.catalina.core.StandardContextValve.invoke(
    at de.javakaffee.web.msm.SessionTrackerValve.invoke(
    at org.apache.catalina.core.StandardHostValve.invoke(
    at org.apache.catalina.valves.ErrorReportValve.invoke(
    at org.apache.catalina.core.StandardEngineValve.invoke(
    at org.apache.catalina.connector.CoyoteAdapter.service(
    at org.apache.coyote.http11.Http11Processor.process(
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
    at java.util.concurrent.ThreadPoolExecutor$

--- Martin Grotzke <> schrieb am Fr, 18.2.2011:

Von: Martin Grotzke <>
Betreff: Re: How OWB stores @SessionScoped beans in Web app?
Datum: Freitag, 18. Februar, 2011 18:17 Uhr

Hi Thomas,
can you clear cookies and try again? If you're still getting the exception, can you post the
stacktrace / log output?

On Fri, Feb 18, 2011 at 5:44 PM, Thomas Andraschko <> wrote:


Thanks for your answers!

I tried to activate the failover but now i get a ViewExpiredException from Myfaces.

I use: MyFaces 2.0.4, OWB 1.0.0, Tomcat 7.0.8 with the memcached manager.

There was no ViewExpiredException before i activated the failover.

Any ideas?

--- Gurkan Erdogdu <> schrieb am Fr, 18.2.2011:

Von: Gurkan Erdogdu <>
Betreff: Re: How OWB stores @SessionScoped beans in Web app?

Datum: Freitag, 18. Februar, 2011 16:59 Uhr


FailOverService is disabled on default OWB configuration. You have to enable it.

Create in META-INF/openwebbeans/ and add it
into classpath

Write those contents into it




From: Joseph Bergmark <>

Sent: Wed, February 16, 2011 7:56:38 PM
Subject: Re: How OWB stores @SessionScoped beans in Web app?

 OWB stores @SessionScoped beans in an in-memory map of SessionContext's that is keyed off
the session id.

I believe the FailOverService will later store those SessionContext's as a session attribute
in the session as part of the FailOverBagWrapper at
 the end of each request.  It should then serialize/restore as appropriate when the session
is serialized.


On Wed, Feb 16, 2011 at 11:03 AM, Thomas Andraschko <> wrote:


I successfully use Tomcat + Memcached Session Manager to replicate my session and JSF @SessionScoped

Now i tried to use OWB + Memcached SessionManager and it does not working.

So my questions are:

How OWB stores CDI @SessionScoped beans in a Web/JSF app?

Can a OWB application be clustered?



Martin Grotzke

View raw message