[ 
https://issues.apache.org/jira/browse/WW-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263547#comment-13263547
 ] 

nick commented on WW-3805:
--------------------------

Thats correct :) but it has become a problem in dev environment due its huge 
response time breaking most of our Ajax calls. So in context for us <constant 
name="struts.devMode" value="true" /> become useless :).

I don't know wat strategy you gonna take on this... 
If you are not going to do any fix for it then i have to inform my fellow works 
that "struts.devMode = true" is gonna cause you ;).
                
> Struts2 request-> response time  is considerably increased.
> -----------------------------------------------------------
>
>                 Key: WW-3805
>                 URL: https://issues.apache.org/jira/browse/WW-3805
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Dispatch Filter
>    Affects Versions: 2.3.3, 2.3.4
>         Environment: Jboss AS 7.1.1 Final, Struts-2.3.4, Sitemesh, EAR 
> Deployment, Windows 7
>            Reporter: nick
>            Assignee: Lukasz Lenart
>            Priority: Critical
>              Labels: issue, performance, struts2
>             Fix For: 2.3.4
>
>
> Struts2 > 2.3.1.2 is remarkably very slow when we compare it with struts2 
> 2.3.1.2
> I found struts2 application is getting slow when we use 
> {code:xml}
> <filter-class>org.apache.struts2.dispatcher.ng.filter.StrutsPrepareFilter</filter-class>
> <filter-class>org.apache.struts2.dispatcher.ng.filter.StrutsExecuteFilter</filter-class>
> {code}
> When i use StrutsPrepareAndExecuteFilter the performance is pretty good like 
> before. But it will mess up the sitemesh integration.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to