[
https://issues.apache.org/jira/browse/WW-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096856#comment-15096856
]
Lauri Lehtinen edited comment on WW-4587 at 1/13/16 7:42 PM:
-------------------------------------------------------------
It does indeed. Looks like the issue I'm running into was introduced by changes
to LocalizedTextUtil.findResourceBundle in
c826d97cafafc9ce54e15745b23cd211e233c2fa
Thanks!
was (Author: lehtinen):
It does indeed. The issue I'm running into was introduced by changes to
LocalizedTextUtil.findResourceBundle in 2.3.19. Thanks!
> LocalizedTextUtil not caching negative ResourceBundle.getBundle results
> -----------------------------------------------------------------------
>
> Key: WW-4587
> URL: https://issues.apache.org/jira/browse/WW-4587
> Project: Struts 2
> Issue Type: Improvement
> Components: Core Actions
> Affects Versions: 2.3.24
> Reporter: Lauri Lehtinen
> Fix For: 2.3.25
>
> Attachments: struts2_issue.jstack1, struts2_issue.jstack2
>
>
> I have a few websites running under a single Tomcat packaged as separate war
> files. Recently, I have started to run into issues with thread starvation,
> which seems to stem from Struts 2. Specifically, calls to
> ResourceBundle.getBundle via LocalizedTextUtil.findResourceBundle end up
> contending on the lock for WebAppClassLoader.
> When testing things locally, it looks like the findResourceBundle is called
> numerous times for each <s:text> tag, with various bundle names being tried,
> many resulting in a MissingResourceException which does not get cached.
> I will attach a couple of thread dumps that exemplify the situation.
> If you suspect this is caused by something I am doing wrong on my end, please
> do let me know!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
