[
https://issues.jboss.org/browse/AS7-4048?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on AS7-4048:
---------------------------------------
Stan, thanks for much appreciated explanation. I guess the session is the same cos this is
effectively HTTP session replication in action. That's why the issue only happens when
nodes are clustered. I originally thought this was a clustering issue.
It seems to me that this problem can happen very easily. Basically, pretty much any JSF
web app out of the box that has HTTP session replication on will get the issue unless
client side state is maintained for JSF. I wonder whether the default should be the
opposite, to store JSF state in client side. Such default might be less performant than
storing in HTTP session, but at least it will be correct. WDYT?
JSF deployment failing on (clustered) domain mode with
ViewExpiredException but works in standalone
---------------------------------------------------------------------------------------------------
Key: AS7-4048
URL:
https://issues.jboss.org/browse/AS7-4048
Project: Application Server 7
Issue Type: Bug
Components: JSF
Affects Versions: 7.1.0.Final
Reporter: Galder Zamarreño
Assignee: Stan Silvert
Fix For: 7.1.2.Final-redhat1
Attachments: infinispan-as7.cli, infinispan-jboss-as7.war, server-four.log,
server-three.log, web.xml
I'm trying to run
https://github.com/galderz/infinispan-quickstart/tree/t_710final/jboss-as7 in AS
7.1.0.Final domain mode but it fails.
It does work fine in standalone mode. And it works fine domain too if you only hit one of
the nodes, but not after both have been hit.
So, in domain mode (regardless of browser, tried with Chrome and Firefox), once two
servers are up and running and the app has been deployed to both nodes, when I try to
enter a new cache entry in one of the nodes, I get:
{code}Caused by: javax.faces.application.ViewExpiredException: viewId:/home.jsf - View
/home.jsf could not be restored.
at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:205)
[jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]{code}
This is pretty cryptic. After adding some logging, I see an exception being thrown
earlier in the code:
{code}11:58:57,844 FINE [javax.enterprise.resource.webcontainer.jsf.application] (MSC
service thread 1-3) java.lang.NoSuchMethodException:
org.jboss.as.web.deployment.jsf.JandexAnnotationProvider.<init>(javax.servlet.ServletContext,
com.sun.faces.spi.AnnotationProvider): java.lang.NoSuchMethodException:
org.jboss.as.web.deployment.jsf.JandexAnnotationProvider.<init>(javax.servlet.ServletContext,
com.sun.faces.spi.AnnotationProvider)
at java.lang.Class.getConstructor0(Class.java:2706) [classes.jar:1.6.0_29]
at java.lang.Class.getDeclaredConstructor(Class.java:1985) [classes.jar:1.6.0_29]
at com.sun.faces.spi.ServiceFactoryUtils.getProviderFromEntry(ServiceFactory.java:83)
[jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
at
com.sun.faces.spi.AnnotationProviderFactory.createAnnotationProvider(AnnotationProviderFactory.java:70)
[jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
at
com.sun.faces.config.ConfigManager$AnnotationScanTask.<init>(ConfigManager.java:808)
[jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:349)
[jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:225)
[jsf-impl-2.1.5-jbossorg-1.jar:2.1.5-SNAPSHOT]
at
org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392)
[jbossweb-7.0.10.Final.jar:]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850)
[jbossweb-7.0.10.Final.jar:]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90)
[jboss-as-web-7.1.0.Final.jar:7.1.0.Final]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[classes.jar:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[classes.jar:1.6.0_29]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]{code}
I don't know whether this is relevant at all.
Please find attached a war and server.log files with TRACE on:
org.jboss.weld
org.jboss.solder
javax.enterprise.resource.webcontainer.jsf (a very "intuitive" package for
com.sun.faces, grrr)
javax.faces
org.infinispan
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira