Memory Leak Error when reviewing std_out files in WCC
Article ID: 14415
Updated On:
Products
Issue/Introduction
Memory Leak Error when reviewing std_out files in WCC are seen in the log
When clients are logged into the WCC and asking for std_out or _err, WCC is producing these error messages in the log:
INFO | jvm 1 | 2017/04/18 21:24:54 | 556908 | SEVERE: The web application [wcc#ui] created a ThreadLocal with key of type [org.springframework.core.NamedThreadLocal] (value [Current AOP method invocation]) and a value of type [org.springframework.aop.framework.ReflectiveMethodInvocation] (value [ReflectiveMethodInvocation: public abstract java.lang.String com.ca.wcc.config.api.remote.services.preference.GlobalPreferenceService.getPreference(java.lang.String); target is of class [com.sun.proxy.$Proxy71]]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
and
2017-04-18 20:15:42,477 @collector <alertsCleanerScheduler-1> [] ERROR #TaskUtils$LoggingErrorHandler # Unexpected error occurred in scheduled task.
org.springframework.remoting.RemoteAccessException: Could not access HTTP invoker remote service at [http://localhost:10132/wcc-configuration/cfmremote/remoteGlobalPrefService]; nested exception is com.ca.wcc.config.api.exceptions.WCCException: Read timed out
Environment
Component:
Resolution
These messages can be because of very large std or err out files.
WCC is not a very good tool to view very large std out files or err files. The files get
transferred via AFM messages from the application server which takes a longer path than
sending them directly.The larger log file means longer time for download, high CPU usage
and memory consumption on WCC machine and for really large files it’ll even fail. For this
reason the autosys team has developed a parm to limit the amount of lines retrieved:
LogMaxEndLines. This can be set in the $AUTOUSER/config.<instance> file. I would suggest
using that to read the first 1000 lines. I think once you do this, the collector should be
able to collect. You will need to add the parm change on the scheduler and restart
the autosys server and also wcc.
Feedback
