I have a production web application running on Tomcat. The web application uses struts 2 as the MVC layer.
We had a problem when one of the web servers increased to 100% processor utilization. This question lasted more than a few hours. I took a thread dump and saw more than a hundred threads in runnable state, and dumps show the same stack trace for most threads.
TP-Processor2" daemon prio=10 tid=0x00002aab80880c00 nid=0x5b4f runnable [0x0000000043bff000..0x0000000043c05d90]
java.lang.Thread.State: RUNNABLE
at java.util.HashMap.get(HashMap.java:303)
at com.opensymphony.xwork2.util.LocalizedTextUtil.buildMessageFormat(LocalizedTextUtil.java:620)
at com.opensymphony.xwork2.util.LocalizedTextUtil.getDefaultMessage(LocalizedTextUtil.java:588)
at com.opensymphony.xwork2.util.LocalizedTextUtil.findText(LocalizedTextUtil.java:461)
at com.opensymphony.xwork2.TextProviderSupport.getText(TextProviderSupport.java:224)
at com.opensymphony.xwork2.ActionSupport.getText(ActionSupport.java:99)
at org.apache.struts2.components.Text.end(Text.java:158)
at org.apache.struts2.views.jsp.ComponentTagSupport.doEndTag(ComponentTagSupport.java:43)
at org.apache.jsp.parts.myjsp_jsp._jspx_meth_s_005ftext_005f2(myjsp_jsp.java:296)
at org.apache.jsp.parts.myjsp_jsp._jspService(myjsp_jsp.java:94)
Now the code used uses struts s: text tag and simply extracts the value from the properties file. I'm not sure why so many threads should be stuck there (threads are in runnable state).
May I get help in resolving what could go wrong.