[ http://jira.jboss.com/jira/browse/JBSEAM-2591?page=all ] Samuel Mendenhall updated JBSEAM-2591: -------------------------------------- Attachment: seamjsfaction.jmx -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2591?page=all ] Samuel Mendenhall updated JBSEAM-2591: -------------------------------------- Attachment: pageactionssucceed.png -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2591?page=comments#action_12398922 ] Samuel Mendenhall commented on JBSEAM-2591: ------------------------------------------- Need documentation specifically warning users when attempting to load test their application with seam debug on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2591?page=all ] Pete Muir updated JBSEAM-2591: ------------------------------ Issue Type: Task (was: Bug) Component/s: Documentation Fix Version/s: 2.0.2.GA 2.1.0.GA Description: Document pitfalls of using development mode in production. (was: Page actions fail to be invoked when load testing multiple requests simultaneously. Pages actions do correctly get processed when those requests are given an interval between executions, thus not concurrent. Code for reproduction: <page view-id="/home.xhtml" login-required="false"> <action execute="#{someComponent.someMethod}"/> </page> @Name("someComponent") public class SomeComponent { @Logger private Log log; @In FacesMessages facesMessages; public void someMethod() { log.info("someComponent:someMethod invoked at " + Calendar.getInstance().getTime()); facesMessages.add("someComponent:someMethod invoked at " + Calendar.getInstance().getTime()); } } There is on average of between 1-3 failed actions per 20 concurrent requests from initial analysis. The failed action presents absolutely no exception, the method is just not called, no log message in the console, and no FacesMessage added. jMeter script and screens attached.) Priority: Minor (was: Critical) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2591?page=all ] Pete Muir updated JBSEAM-2591: ------------------------------ Fix Version/s: 2.1.0.GA (was: 2.1.0.BETA1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira