myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Kieselhorst (JIRA)" <>
Subject [jira] [Created] (MYFACES-3932) FacesConfigurator causes IllegalStateException
Date Wed, 15 Oct 2014 12:39:34 GMT
Dennis Kieselhorst created MYFACES-3932:

             Summary: FacesConfigurator causes IllegalStateException
                 Key: MYFACES-3932
             Project: MyFaces Core
          Issue Type: Bug
    Affects Versions: 2.2.5
            Reporter: Dennis Kieselhorst

This issue was originally reported on the mailinglist:

I am still able to reproduce it if I build the application in UTC+1 timezone and run it with
-Duser.timezone=UTC. It doesn't occur with project stage production.

The exception is raised multiple times:
java.lang.IllegalStateException: setStateManager may not be executed after a lifecycle request
has been completed
	at org.apache.myfaces.application.ApplicationImpl.setStateManager(
	at org.apache.myfaces.config.FacesConfigurator.configureApplication(
	at org.apache.myfaces.config.FacesConfigurator.configure(
	at org.apache.myfaces.config.FacesConfigurator.update(
	at org.apache.myfaces.lifecycle.LifecycleImpl.execute(
	at javax.faces.webapp.FacesServlet.service(
	at org.eclipse.jetty.servlet.ServletHolder.handle(
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(

This message was sent by Atlassian JIRA

View raw message