Univiewer Webconsole 6.3.xx freezes and Tomcat Server becomes unusable - "Deadlock detected"
book
Article ID: 85609
calendar_today
Updated On:
Products
CA Automic Dollar Universe
Issue/Introduction
Error Message : On the univiewer_server.log on the tomcat, this kind of error appears: ######################################## |ERROR|LockDetector-0|com.orsyp.util.LockDetector|Deadlock(s) detected involving 3 threads: ########################################
On the catalina.out of the Tomcat, these kind of messages may appear: ######################################## SEVERE: The web application [/univiewer_webconsole_6.3.21_all_os] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation. Jan 30, 2015 9:30:32 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/univiewer_webconsole_6.3.01] appears to have started a thread named [Expiring task] but has failed to stop it. This is very likely to create a memory leak. Jan 30, 2015 9:30:33 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/univiewer_webconsole_6.3.41] appears to have started a thread named [Expiring task] but has failed to stop it. This is very likely to create a memory leak. ########################################
Description :After upgrading to Univiewer Webconsole to version 6.3.xx, the users sometimes lose access to the menus and the console appears frozen. A restart of the Tomcat is necessary in order to restore the service.
Environment
OS: All
Cause
Cause type: Defect Root Cause: The Univiewer WebConsole could freeze the Tomcat server due to a memory leak and thread synchronization issue when connecting to unreachable nodes.
Resolution
Update to the fix version listed below or a newer version if available.