[
https://issues.apache.org/jira/browse/WW-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilson Rao updated WW-4491:
---------------------------
Description:
This is a clone of Issue:
CLONE - Struts 2.3.8 threads BLOCKED in
com.opensymphony.xwork2.config.ConfigurationManager.getConfiguration(WW3971)
We followed the instructions in the original ticket and installed version
2.3.12, however we still see the same problem there. Under load we see several
threads hung on getConfiguration. The only alternative is to restart the app.
Can we you please investigate this?
was:
While load testing a web application on Tomcat 6 using Struts 2.3.8 version.
devMode is set to false.
Found lot of BLOCKED threads in this method:
com.opensymphony.xwork2.config.ConfigurationManager.getConfiguration()
This is causing high CPU usage for the application. also found that
com.opensymphony.xwork2.config.ConfigurationManager.conditionalRelad is taking
time which causes getconfiguration (synchronized) to queue up for processing.
This happens when concurrent users are above 100.
> CLONE - Struts 2.3.8 threads BLOCKED in
> com.opensymphony.xwork2.config.ConfigurationManager.getConfiguration(WW3971)
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WW-4491
> URL: https://issues.apache.org/jira/browse/WW-4491
> Project: Struts 2
> Issue Type: Bug
> Components: XML Configuration
> Affects Versions: 2.3.8
> Environment: apache-tomcat-6.0.32, jdk1.6.0_27, devMode set to false.
> Reporter: Wilson Rao
> Assignee: Lukasz Lenart
> Fix For: 2.3.12
>
>
> This is a clone of Issue:
> CLONE - Struts 2.3.8 threads BLOCKED in
> com.opensymphony.xwork2.config.ConfigurationManager.getConfiguration(WW3971)
> We followed the instructions in the original ticket and installed version
> 2.3.12, however we still see the same problem there. Under load we see
> several threads hung on getConfiguration. The only alternative is to restart
> the app.
> Can we you please investigate this?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
