In the <$SPECROOT>/tomcat/logs folder, there are various tomsawyer.<date>.log files.
Sometimes they contain severe exceptions such as memory leaks alerts.
Sep 25, 2018 8:32:31 AM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [/introscope-wssdk-consumer] appears to have started a thread named [LifecycleListenerNotifier] but has failed to stop it. This is very likely to create a memory leak.
Sep 25, 2018 8:32:32 AM org.apache.catalina.core.ApplicationContext log
INFO: Destroying Spring FrameworkServlet 'NetqosIntegrationBootstrapServlet'
Sep 25, 2018 8:35:30 AM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads
SEVERE: The web application [/spectrum] appears to have started a thread named [Thread Scheduler] but has failed to stop it. This is very likely to create a memory leak.
What creates these files and what steps should I take?
Tom Sawyer Layout is a Software Development Kit (SDK) that provides nested drawing data models and layout, labeling, and routing technology for applications that have their own graphical framework.
Tom Sawyer Layout is intended for applications that already have graphics facilities in place, and that still need automatic layout capabilities.
Tom Sawyer Layout provides a variety of high-quality layout algorithms with superior performance and scalability.
The tomsawyer logs in Spectrum need not be opened unless requested by support.
Their contents are benign and not useful unless specific debug is enabled.
They are created by the webclient and only on Linux servers.
Tomsawyer logs are not enabled by default and basically used by webclient.
In the SPECROOT/tomcat/webapps/spectrum/WEB-INF/web.xml file we refer to the required tomsawyer libraries and hence at the tomcat startup the tomsawyer log file gets generated in Linux.
The warning messages under tomsawyer log files are benign.