ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

UVC Webconsole: Tomcat Threads leak

book

Article ID: 186490

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

Since the Univiewer Webconsole upgrade from version 6.8.x to 6.9.x or 6.10.x, the Tomcat thread count do not cease to increase until freeze the Tomcat connector ( default maximum thread count being 200).

Example of the excessively long threads visible in the Server Status in Tomcat Administration page:

"http-bio-8080"
Max threads: 200 Current thread count: 143 Current thread busy: 143
Max processing time: 4581728 ms Processing time: 46645.496 s Request count: 8513 Error count: 103 Bytes received: 23.44 MB Bytes sent: 24.46 MB

Stage Time B Sent B Recv Client (Forwarded) Client (Actual) VHost Request
S 5844118 ms 0 KB 0 KB xx.xx.xx.xx xx.xx.xx.xx server.domain.com POST /univiewer_webconsole_6.10.11/servlet/proxyServlet/ HTTP/1.1

Cause

Univiewer Webconsole did not release both sides of the communication when a read error occurred.

Environment

Release : 6.9 and 6.10
Component : DOLLAR UNIVERSE
Subcomponent: Univiewer Webconsole

Resolution

Workaround:
a. Use Univiewer Webconsole 6.8.x or inferior
b. Increase Tomcat Connector maximum threads to 5000 instead of 200 (parameter maxThreads) and schedule a restart when it reaches the maximum

Solution:
Upgrade to Univiewer Webconsole 6.10.31 - available 22nd April 2020