[
https://issues.apache.org/jira/browse/WW-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500232#comment-14500232
]
Lukasz Lenart commented on WW-4491:
-----------------------------------
Without more detailed stacktrace or some JMeter or JProfiler dump it's hard to
say anything what's the real issue here. Can you use a profiler to find where
are all those calls to
{{org.apache.struts2.dispatcher.Dispatcher.getContainer(Dispatcher.java:942)}}
comes from?
> 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.12
> Environment: ava(TM) SE Runtime Environment (build 1.6.0_71-b12)
> Weblogic 10.3.6
> SLES
> JARS:
> struts2-core-2.3.12.jar
> struts2-spring-plugin-2.3.12.jar
> Reporter: Wilson Rao
> Assignee: Lukasz Lenart
> Fix For: 2.3.24
>
>
> 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.
> "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default
> (self-tuning)'" daemon prio=10 tid=0x00007f70b55f4800 nid=0x1aa waiting for
> monitor entry [0x00007f70b3916000]
> java.lang.Thread.State: BLOCKED (on object monitor)
> at
> com.opensymphony.xwork2.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:64)
> - waiting to lock <0x000000051b3214f0> (a
> com.opensymphony.xwork2.config.ConfigurationManager)
> at
> org.apache.struts2.dispatcher.Dispatcher.getContainer(Dispatcher.java:942)
> Can we you please investigate this?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
