CAS 5.1.6 cas/status integer overflow

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

CAS 5.1.6 cas/status integer overflow

Duane Booher
Hi, is this considered a CAS 5.1.6 cas/status bug? 

We have these settings:

cas.ticket.registry.ehcache.maxElementsInMemory=15000

cas.ticket.registry.ehcache.persistence=LOCALTEMPSWAP


curl -k https://HOST#1:8443/cas/status
Health: OK

1.MemoryMonitor: OK - 4415.62MB free (72.26%), 1695.51MB used, 6111.13MB total.

2.SessionMonitor: OK - -9223372036854775808 sessions. 463 service tickets.

Host: HOST#1
Server: XXXXXX
Version: 5.1.6

time curl -k https://HOST#2:8443/cas/status
Health: WARN

1.SessionMonitor: WARN - Session count (17052) is above threshold 10000. 456 service tickets.

2.MemoryMonitor: OK - 5078.95MB free (83.11%), 1032.18MB used, 6111.13MB total.

Host: HOST#2
Server: XXXXXX
Version: 5.1.6

real 0m11.813s
user 0m0.013s
sys 0m0.006s

Also, both of these are taking 10+ seconds to run.

Duane

--
You received this message because you are subscribed to the Google Groups "CAS Developer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
Visit this group at https://groups.google.com/a/apereo.org/group/cas-dev/.
Reply | Threaded
Open this post in threaded view
|

Re: CAS 5.1.6 cas/status integer overflow

Duane Booher
I started to look at the code in: core/cas-server-core-monitor and api/cas-server-core-api-monitor. Then I also reviewed the sequence of events. When we crossed the threshold 15000 sessions, then the integer overflow started occurring.

Along with this associated error messages:

2018-01-21 13:20:40,546 ERROR [org.springframework.boot.web.support.ErrorPageFilter] - <Cannot forward to error page for request [/status] as the response has already been committed. As a result, the response may have the wrong status code. If your application is running on WebSphere Application Server you may be able to resolve this problem by setting com.ibm.ws.webcontainer.invokeFlushAfterService to false>

I suppose I could continue increasing: cas.ticket.registry.ehcache.maxElementsInMemory

or shorten the TGT times, which we are running with the defaults (and used these settings as part of our policy for many years):

cas.ticket.tgt.maxTimeToLiveInSeconds=28800
cas.ticket.tgt.timeToKillInSeconds=7200

Does anyone have any suggests on how to generally handle a configuration situation like this?

We have been using cas/status as a monitoring agent, and with the above problems (plus some others that I'm not describing), we have stopped the cas/status runs.

Duane

On Sunday, January 21, 2018 at 3:52:46 PM UTC-7, Duane Booher wrote:
Hi, is this considered a CAS 5.1.6 cas/status bug? 

We have these settings:

cas.ticket.registry.ehcache.maxElementsInMemory=15000

cas.ticket.registry.ehcache.persistence=LOCALTEMPSWAP


curl -k <a href="https://HOST#1:8443/cas/status" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2FHOST%231%3A8443%2Fcas%2Fstatus\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG5-xKkoCzh76Jb5AJle7yuaf1jA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2FHOST%231%3A8443%2Fcas%2Fstatus\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG5-xKkoCzh76Jb5AJle7yuaf1jA&#39;;return true;">https://HOST#1:8443/cas/status
Health: OK

1.MemoryMonitor: OK - 4415.62MB free (72.26%), 1695.51MB used, 6111.13MB total.

2.SessionMonitor: OK - -9223372036854775808 sessions. 463 service tickets.

Host: HOST#1
Server: XXXXXX
Version: 5.1.6

time curl -k <a href="https://HOST#2:8443/cas/status" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2FHOST%232%3A8443%2Fcas%2Fstatus\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG876VjsrcX3IJ8LGulmwrdNUe_9g&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2FHOST%232%3A8443%2Fcas%2Fstatus\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG876VjsrcX3IJ8LGulmwrdNUe_9g&#39;;return true;">https://HOST#2:8443/cas/status
Health: WARN

1.SessionMonitor: WARN - Session count (17052) is above threshold 10000. 456 service tickets.

2.MemoryMonitor: OK - 5078.95MB free (83.11%), 1032.18MB used, 6111.13MB total.

Host: HOST#2
Server: XXXXXX
Version: 5.1.6

real 0m11.813s
user 0m0.013s
sys 0m0.006s

Also, both of these are taking 10+ seconds to run.

Duane

--
You received this message because you are subscribed to the Google Groups "CAS Developer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
Visit this group at https://groups.google.com/a/apereo.org/group/cas-dev/.