[ https://issues.jboss.org/browse/GTNPORTAL-3283?page=com.atlassian.jira.pl... ] Marko Strukelj commented on GTNPORTAL-3283: ------------------------------------------- This happens as a result of deploying a .war marked <distributable /> into a container that's not currently in clustered configuration, but a standalone one. You need archives marked <distributable /> when running in clustered mode otherwise session replication will not work across cluster. <distributable /> marks a web application as _being capable_ of properly running in clustered mode, not _requesting to be run_ in clustered mode. It should not IMHO result in a WARN by jboss-web container. Removing <distributable /> is IMHO not an option, as it would require special manual steps to modify packaged GateIn wars - e.g. portal.war/WEB-INF/web.xml for deploying in cluster mode, and most of the people would probably forget that step, and have to deal with troubleshooting why session replication doesn't work. Either there is something in web subsystem configuration to turn these WARN logs off, or we can add a logging filter that would mute org.jboss.web WARN level which would be a big hack, and is not really a serious proposition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira