pdm_tomcat_log is updated the "org.apache.tomcat.util.threads.ThreadPool logFull" and all feature that use tomcat do not work.

book

Article ID: 48596

calendar_today

Updated On:

Products

CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service KNOWLEDGE TOOLS CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction

Description:

The pdm_tomcat_log is updated with the following log entry and all features that use tomcat do not work.

This document explains to modify the settings in order to avoid the problem in future.

2013/08/09 9:28:38 org.apache.tomcat.util.threads.ThreadPool logFull SEVERE: All threads (150) are currently busy, waiting. Increase maxThreads(150) or check the servlet status."

Solution:

This not only applied to CA products, but any products that use Tomcat.

When this error occurs, the user needs to tune the Tomcat to avoid the problem.

As the error message says, Tomcat has reached the maximum number of threads it can process.

The default maxTreads is 150. We recommend to raise the value(i.e. 300).

Configuration file:
$NX_ROOT\bopcfg\www\CATALINA_BASE\conf\server.xml

Place:
r12.5 (Tomcat 5.5.25)

[Default]
<Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150" minSpareThreads="25" port="8080" redirectPort="8443"/>

[Modified]
<Connector acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="300" minSpareThreads="25" port="8080" redirectPort="8443"/>

r12.7 (Tomcat 7.0.23) and r12.6 (Tomcat 6.0.30)

[Default]
<Connector connectionTimeout="20000" port="8080" protocol="HTTP/1.1" redirectPort="8443" />

[Modified]
<Connector connectionTimeout="20000" port="8080" protocol="HTTP/1.1" redirectPort="8443" maxThreads="300"/>

After change the setting and saved, he needs to recycle the pdm_tomcat_nxd by the following commands.

pdm_tomcat_nxd -c stop
pdm_tomcat_nxd -c start

This issue would only appear if Tomcat is overloaded. Be sure to plan for estimated concurrent file attachment processing, estimated concurrent Web Services API transactions and concurrent user load per Tomcat instance.

Environment

Release: UAPMAC990JPP-12.6-Asset Portfolio Management-Asset Configuration
Component: