Symantec Access Management

  • Private Community
 View Only
Back to discussions
Expand all | Collapse all

Tech Tip : CA Single Sign-On : OneView Monitor write tons of logs lines permanently in Tomcat stdout logs

  • 1.  Tech Tip : CA Single Sign-On : OneView Monitor write tons of logs lines permanently in Tomcat stdout logs

    Broadcom Employee
    Posted Nov 10, 2017 03:49 AM

    Issue:


    We run OneView Monitor on Tomcat, and unfortunatly we see the logs are filling up quickly and because there's no log rotation on Tomcat. The logs fill up the file system partition. We've found no way to configure the OneView monitoring logs. So permanently the OneView Monitor writes lines in the Tomcat stdout log until we restart the server.

     

    Here's a sample :

     

    tomcat-stdout.2017-06-23.log

     

    2017-06-23 14:12:20 Commons Daemon procrun stdout initialized

    MenuModel i18n=com.netegrity.mon.gui.I18N@65a60d, urlBase=

    indexPres percent=33%,33%,*

    framestr=

    framestr=

    framestr=

    Trace: at least on of nete.ps.root or nete.wa.root has to be defined.

    Trace: failed to load trace settings.

    component ComponentSpec path=/SmRoot/10.243.9.163/PolicyServer/PolicyServer;1908, index=1

    component ComponentSpec path=/SmRoot/10.243.9.163/PolicyServer/PolicyServer;1908, index=1

    getComponents returns /SmRoot/10.243.9.163/PolicyServer/PolicyServer;1908

    component ComponentSpec path=/SmRoot/10.243.9.163/PolicyServer/PolicyServer;1908, index=1

     

    [...]

     

    Environment:

     

    Policy Server 12.52SP2CR01 on Windows 2012 R2; OneView Monitor on Tomcat 7.0.77 with JDK 8u131.

     

    Resolution:

     

    The fix for this issue is expected in 12.52SP1CR09 and in a next CR of 12.7.

     

    KB : TEC1317386