[ https://jira.jboss.org/jira/browse/JBSEAM-4185?page=com.atlassian.jira.pl... ] Adrian Mitev updated JBSEAM-4185: --------------------------------- Affects Version/s: 2.1.2.CR2 (was: 2.1.2.CR1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-4185?page=com.atlassian.jira.pl... ] Adrian Mitev updated JBSEAM-4185: --------------------------------- Description: See exception.txt for the stacktrace. This is what i have in pages.xml <exception class="javax.faces.application.ViewExpiredException" log="false"> <redirect view-id="/common/error.xhtml"> <message>#{messages.sessionTimeout}</message> </redirect> </exception> and the redirect is performed but i still see the exception in the log Use case to reproduce: Open a page with a commandButton, restart the application server and when it's started try to submit the form. This will cause a ViewExpiredException. was: See exception.txt for the stacktrace. This is what i have in pages.xml <exception class="javax.faces.application.ViewExpiredException" log="false"> <redirect view-id="/common/error.xhtml"> <message>#{messages.sessionTimeout}</message> </redirect> </exception> and the redirect is performed but i still see the exception in the log -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-4185?page=com.atlassian.jira.pl... ] Adrian Mitev commented on JBSEAM-4185: -------------------------------------- Even tried with <context-param> <param-name>facelets.DEVELOPMENT</param-name> <param-value>false</param-value> </context-param> and <core:init debug="false" jndi-pattern="@jndiPattern@"/> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-4185?page=com.atlassian.jira.pl... ] Norman Richards commented on JBSEAM-4185: ----------------------------------------- workaround would be to lower lower the logging threshold for that category in your log4j.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-4185?page=com.atlassian.jira.pl... ] Diogo Santos commented on JBSEAM-4185: -------------------------------------- I have the same issue. Changing de log level doesn´t work. The debug message is always printed in my log. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-4185?page=com.atlassian.jira.plugi... ] Peyman Rezaei commented on JBSEAM-4185: --------------------------------------- Any new staus of this bug? -- 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