Symantec Access Management

Expand all | Collapse all

Exception in thread "Timer-0"  IN SPS

  • 1.  Exception in thread "Timer-0"  IN SPS

    Posted 11-29-2016 11:11 AM

    Hi All,

     

       We see below errors in SPS servers, after we restart the SPS services we see these errors after 5 mins. Any suggestions why these errors might be coming and how to resolve them?

     

    [28/Nov/2016:16:10:54-640] [ERROR] - Exception in thread "Timer-0"
    [28/Nov/2016:16:10:54-640] [ERROR] - java.lang.NoClassDefFoundError: org/apache/commons/pool/impl/CursorableLinkedList$Cursor
    [28/Nov/2016:16:10:54-640] [ERROR] - at org.apache.commons.pool.impl.CursorableLinkedList.cursor(CursorableLinkedList.java:303)
    [28/Nov/2016:16:10:54-640] [ERROR] - at org.apache.commons.pool.impl.GenericObjectPool.evict(GenericObjectPool.java:1187)
    [28/Nov/2016:16:10:54-640] [ERROR] - at org.apache.commons.pool.impl.GenericObjectPool$Evictor.run(GenericObjectPool.java:1341)
    [28/Nov/2016:16:10:54-640] [ERROR] - at java.util.TimerThread.mainLoop(Timer.java:555)
    [28/Nov/2016:16:10:54-640] [ERROR] - at java.util.TimerThread.run(Timer.java:505)
    [28/Nov/2016:16:10:54-640] [ERROR] - Caused by: java.lang.ClassNotFoundException: org.apache.commons.pool.impl.CursorableLinkedList$Cursor
    [28/Nov/2016:16:10:54-640] [ERROR] - at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1720)
    [28/Nov/2016:16:10:54-640] [ERROR] - at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
    [28/Nov/2016:16:10:54-640] [ERROR] - ... 5 more
    [28/Nov/2016:16:11:23-907] [ERROR] - Exception in thread "Timer-1"
    [28/Nov/2016:16:11:23-907] [ERROR] - java.lang.NoClassDefFoundError: org/apache/commons/pool/impl/CursorableLinkedList$Cursor
    [28/Nov/2016:16:11:23-907] [ERROR] - at org.apache.commons.pool.impl.CursorableLinkedList.cursor(CursorableLinkedList.java:305)
    [28/Nov/2016:16:11:23-907] [ERROR] - at org.apache.commons.pool.impl.GenericObjectPool.evict(GenericObjectPool.java:1488)
    [28/Nov/2016:16:11:23-907] [ERROR] - at org.apache.commons.pool.impl.GenericObjectPool$Evictor.run(GenericObjectPool.java:1700)
    [28/Nov/2016:16:11:23-907] [ERROR] - at java.util.TimerThread.mainLoop(Timer.java:555)
    [28/Nov/2016:16:11:23-907] [ERROR] - at java.util.TimerThread.run(Timer.java:505)
    [28/Nov/2016:16:11:23-907] [ERROR] - Caused by: java.lang.ClassNotFoundException: org.apache.commons.pool.impl.CursorableLinkedList$Cursor
    [28/Nov/2016:16:11:23-907] [ERROR] - at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1720)
    [28/Nov/2016:16:11:23-907] [ERROR] - at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
    [28/Nov/2016:16:11:23-907] [ERROR] - ... 5 more



  • 2.  Re:  Exception in thread "Timer-0"  IN SPS

    Broadcom Employee
    Posted 11-29-2016 01:38 PM

    Hi Richard,

     

    Were your SPS and Policy server configured to support Session Assurance using Device DNA functionality?

    Do you intend to use Session Assurance feature? I think Session Assurance was shipped by default in SPS.

    What is exact version of your SPS and policy server?

     

    This error seems to be Session Assurance feature related. You may choose to ignore the error if there are no any other functional problems observed.

    If you do not use Session Assurance feature, by disabling it ("Advanced Auth" part) from SPS server.conf file should resolve it.

    If you do use it, then you need to follow the SSO documentation on Session Assurance, and have everything setup by the book.

     

    Thanks,

     

    Hongxu



  • 3.  Re:  Exception in thread "Timer-0"  IN SPS

    Posted 11-29-2016 02:17 PM

    Thanks liuho03,

     

       We are not using Session Assurance, so I disabled the feature:

     

    <Contexts>
    <Context name="Credential Handling Service">
    docBase="chs"
    path="chs"
    enable="no"
    </Context>
    <Context name="Authentication/Authorization web services">
    docBase="CA_AuthAZ"
    path="authazws"
    enable="no"
    </Context>
    <Context name="AALoginService">
    docBase="aaloginservice"
    path="aaloginservice"
    enable="no"
    </Context>
    <Context name="Advanced Auth Application">
    docBase="authapp"
    path="authapp"
    enable="no"
    </Context>

     

    Restarted the SPS services, but still getting that error. I assume this error is not due to Session Assurance service.

    I checked the server Time its in Sync with policy server.

     

    SPS Version 12.52 , Update 0102 , Label 766



  • 4.  Re:  Exception in thread "Timer-0"  IN SPS

    Broadcom Employee
    Posted 11-29-2016 02:47 PM

    You are on SPS Version 12.52 , Update 0102 , Label 766.

    There is a recent documented defect with similar error message, 

    Fix is scheduled to be released with R12.52 SP1 CR6 SPS release.

    Tech Tip - CA Single Sign-On: R12.52 SP1 CR5 Secure Proxy Server crashes 

     

    Hongxu



  • 5.  Re:  Exception in thread "Timer-0"  IN SPS

    Posted 12-12-2016 04:34 PM

    Hi liuho03, thanks for your suggestion, We used newer version of SPS and we are not seeing those error.

     

    But we found, server.log is getting filled with:

     

    [12/Dec/2016:13:30:14-911] [INFO] - Server Name: hostname
    [12/Dec/2016:13:30:14-911] [INFO] - Server Port: 80
    [12/Dec/2016:13:30:19-903] [INFO] - Server Name: hostname
    [12/Dec/2016:13:30:19-903] [INFO] - Server Port: 80
    [12/Dec/2016:13:30:24-911] [INFO] - Server Name: hostname
    [12/Dec/2016:13:30:24-911] [INFO] - Server Port: 80
    [12/Dec/2016:13:30:29-919] [INFO] - Server Name: hostname
    [12/Dec/2016:13:30:29-919] [INFO] - Server Port: 80

     

    Its not creating any issues, just curios why these messages are coming so frequently with this newer version.



  • 6.  Re:  Exception in thread "Timer-0"  IN SPS

    Broadcom Employee
    Posted 12-12-2016 05:57 PM

    The message is [INFO], so should be benign.

    However, SPS tomcat does not use 80, only apache does. You should check configuration ensure no port 80 was misconfigured in the wrong place. This could also be a webapp monitor of some kind probing the server on port 80, but not a request SPS can understand or proxy to. 

     

    Hongxu



  • 7.  Re:  Exception in thread "Timer-0"  IN SPS

    Broadcom Employee
    Posted 12-12-2016 06:24 PM

    Hi Richard

    The looks of the message is like in httpd.conf you still have the Server Name directive set to hostname and using port 80.

    That should not right. Can you check the httpd logs in sps as well as look at the configuration ?

    Also you can look up into the server.conf to make sure there is no virtual host or webservice configured to use port 80. You may as well verify with netstat -an | grep 80 who is listening there and even try to telnet or http to it to see what it comes up with