[cas-user] Re: Thread count keeps growing at tomcat 8.5 with CAS 5.1
I haven't found a solution to this issue. It seems to be related to SAML2 services. Any time one of them creates a service ticket, the thread count increases and never decreases. I checked the 5.3 RC2 and it doesn't seem to have the same issue. Once that release is a stable version, I'll be testing that out for our deployment. On Monday, August 28, 2017 at 9:02:48 AM UTC-5, Song, Doe-Hyun wrote: > > Good Morning All, > > > > Since we go to production with CAS 5.1, we keep having growing Thread > counts. > > > > We use ehcache for HA implementation and ldap for authentication. > > > Two types of threads – Timer and pool-3-thread – keep growing as time > goes. > > > > Any suggestion to debug this issue? > > > > Thread dump : > > > > > > Full thread dump OpenJDK 64-Bit Server VM (25.101-b13 mixed mode): > > > > "Timer-73" #512 daemon prio=5 os_prio=0 tid=0x7f0520033000 nid=0x8041 > in Object.wait() [0x7f0509b5c000] > >java.lang.Thread.State: TIMED_WAITING (on object monitor) > > at java.lang.Object.wait(Native Method) > > at java.util.TimerThread.mainLoop(Timer.java:552) > > - locked <0xafb48f10> (a java.util.TaskQueue) > > at java.util.TimerThread.run(Timer.java:505) > > > > "Timer-72" #509 daemon prio=5 os_prio=0 tid=0x7f0520019800 nid=0x7fbc > in Object.wait() [0x7f050a469000] > >java.lang.Thread.State: TIMED_WAITING (on object monitor) > > at java.lang.Object.wait(Native Method) > > at java.util.TimerThread.mainLoop(Timer.java:552) > > - locked <0xafa333a0> (a java.util.TaskQueue) > > at java.util.TimerThread.run(Timer.java:505) > > > > "pool-3-thread-23" #508 prio=5 os_prio=0 tid=0x7f05180b3000 nid=0x7f36 > waiting on condition [0x7f0509d6] > >java.lang.Thread.State: WAITING (parking) > > at sun.misc.Unsafe.park(Native Method) > > - parking to wait for <0xa7f17930> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > > at > java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > > at > java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > > at java.lang.Thread.run(Thread.java:745) > > > > "Timer-71" #507 daemon prio=5 os_prio=0 tid=0x7f05180b8800 nid=0x7f35 > in Object.wait() [0x7f0509f62000] > >java.lang.Thread.State: TIMED_WAITING (on object monitor) > > at java.lang.Object.wait(Native Method) > > at java.util.TimerThread.mainLoop(Timer.java:552) > > - locked <0xaf974c00> (a java.util.TaskQueue) > > at java.util.TimerThread.run(Timer.java:505) > > > > "Timer-70" #506 daemon prio=5 os_prio=0 tid=0x7f05506ba000 nid=0x7eb4 > in Object.wait() [0x7f0509e61000] > >java.lang.Thread.State: TIMED_WAITING (on object monitor) > > at java.lang.Object.wait(Native Method) > > at java.util.TimerThread.mainLoop(Timer.java:552) > > - locked <0xaf8cf808> (a java.util.TaskQueue) > > at java.util.TimerThread.run(Timer.java:505) > > > > "pool-3-thread-22" #496 prio=5 os_prio=0 tid=0x7f05180b7800 nid=0x79dd > waiting on condition [0x7f050a063000] > >java.lang.Thread.State: WAITING (parking) > > at sun.misc.Unsafe.park(Native Method) > > - parking to wait for <0xa7f17930> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > > at > java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > > at > java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > > > > Thanks, > > Doe > > > > The information contained in this e-mail and any attachments is confidential > and > intended only for the recipient. If you are not the intended recipient, the > information contained in this message may not be used, copied, or forwarded to > third parties or otherwise distributed for any other purpose. Please notify > the > sender if you received this e-mail in error and delete the e-mail and its > attachments promptly. Nothing in this e-mail may be used or deemed to form > the > basis of a contractual or any other
[cas-user] Re: Thread count keeps growing at tomcat 8.5 with CAS 5.1
We are seeing this same issue. Did you ever find a solution for it? Dan On Monday, August 28, 2017 at 9:02:48 AM UTC-5, Song, Doe-Hyun wrote: > > Good Morning All, > > > > Since we go to production with CAS 5.1, we keep having growing Thread > counts. > > > > We use ehcache for HA implementation and ldap for authentication. > > > Two types of threads – Timer and pool-3-thread – keep growing as time > goes. > > > > Any suggestion to debug this issue? > > > > Thread dump : > > > > > > Full thread dump OpenJDK 64-Bit Server VM (25.101-b13 mixed mode): > > > > "Timer-73" #512 daemon prio=5 os_prio=0 tid=0x7f0520033000 nid=0x8041 > in Object.wait() [0x7f0509b5c000] > >java.lang.Thread.State: TIMED_WAITING (on object monitor) > > at java.lang.Object.wait(Native Method) > > at java.util.TimerThread.mainLoop(Timer.java:552) > > - locked <0xafb48f10> (a java.util.TaskQueue) > > at java.util.TimerThread.run(Timer.java:505) > > > > "Timer-72" #509 daemon prio=5 os_prio=0 tid=0x7f0520019800 nid=0x7fbc > in Object.wait() [0x7f050a469000] > >java.lang.Thread.State: TIMED_WAITING (on object monitor) > > at java.lang.Object.wait(Native Method) > > at java.util.TimerThread.mainLoop(Timer.java:552) > > - locked <0xafa333a0> (a java.util.TaskQueue) > > at java.util.TimerThread.run(Timer.java:505) > > > > "pool-3-thread-23" #508 prio=5 os_prio=0 tid=0x7f05180b3000 nid=0x7f36 > waiting on condition [0x7f0509d6] > >java.lang.Thread.State: WAITING (parking) > > at sun.misc.Unsafe.park(Native Method) > > - parking to wait for <0xa7f17930> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > > at > java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > > at > java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > > at java.lang.Thread.run(Thread.java:745) > > > > "Timer-71" #507 daemon prio=5 os_prio=0 tid=0x7f05180b8800 nid=0x7f35 > in Object.wait() [0x7f0509f62000] > >java.lang.Thread.State: TIMED_WAITING (on object monitor) > > at java.lang.Object.wait(Native Method) > > at java.util.TimerThread.mainLoop(Timer.java:552) > > - locked <0xaf974c00> (a java.util.TaskQueue) > > at java.util.TimerThread.run(Timer.java:505) > > > > "Timer-70" #506 daemon prio=5 os_prio=0 tid=0x7f05506ba000 nid=0x7eb4 > in Object.wait() [0x7f0509e61000] > >java.lang.Thread.State: TIMED_WAITING (on object monitor) > > at java.lang.Object.wait(Native Method) > > at java.util.TimerThread.mainLoop(Timer.java:552) > > - locked <0xaf8cf808> (a java.util.TaskQueue) > > at java.util.TimerThread.run(Timer.java:505) > > > > "pool-3-thread-22" #496 prio=5 os_prio=0 tid=0x7f05180b7800 nid=0x79dd > waiting on condition [0x7f050a063000] > >java.lang.Thread.State: WAITING (parking) > > at sun.misc.Unsafe.park(Native Method) > > - parking to wait for <0xa7f17930> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > > at > java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > > at > java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442) > > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067) > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127) > > > > Thanks, > > Doe > > > > The information contained in this e-mail and any attachments is confidential > and > intended only for the recipient. If you are not the intended recipient, the > information contained in this message may not be used, copied, or forwarded to > third parties or otherwise distributed for any other purpose. Please notify > the > sender if you received this e-mail in error and delete the e-mail and its > attachments promptly. Nothing in this e-mail may be used or deemed to form > the > basis of a contractual or any other legally binding obligation unless > separately > confirmed in writing by an authorized representative of ARMADA. > > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 -
[cas-user] CAS 5.2 - SAML2 SLO
I am trying to use SAML2 with CAS 5.2. I have it setup as the idp and I have two services connected to it. Everything works as expected with one service - but the second service does not receive a POST to its logout url when signing out of CAS. Steps: Sign in to both applications. Only first requires sign in to CAS. Hit cas logout url. One app receives a POST to its sign out url - /saml/SingleLogout. The other app doesn't receive any logout signal. I have debug turned on for opensaml but I am not seeing anything with the logout activity. Not sure where to look next. Any help would be appreciated. Dan -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/16021ea6-f941-4e19-bd2e-9ce9b3a1df53%40apereo.org.
[cas-user] Re: Logout Redirect Issue
I have some more information after testing yesterday. I thought it was specific to the logout sent from my app but it's not. If I go to cas/login I can see all my information. If I use the logout link there with no redirect, it logs out of cas. I If I enter cas/logout with a service redirect url in the browser, it goes to a blank screen. If I press enter on the url again while on the blank screen - it works. The only difference I can see in debug is that it recognizes that there is no cas session to terminate and it continues on to the service redirect. The debug for the first entry appears to work correctly -- the only part that seems to be missing is the last line that indicates it redirected to the external url. If I use the cas.logout.redirect-url= parameter, the logout link on the page doesn't work. It just goes to the blank page. I can tell that cas has been logged out. It definitely doesn't continue to the redirect url or correctly show the cas logout page. I am using a delegated login. In testing today, I am planning to enable to regular login and see if logout works with that. Dan On Tuesday, June 14, 2022 at 10:30:42 AM UTC-5 Dan S wrote: > I am working on upgrading our CAS instance from 6.1 to 6.5. I have been > able to get everything working as expected except the logout redirect. > > I am using the parameter: > cas.logout.follow-service-redirects=true > > I have tried using the parameter for a redirect and setting the global > redirect. > > If you enter the logout url directly in the browser, it correctly sends > back a 302 and the browser is redirected. > > If we have an app that sends the browser to the cas logout url, cas sends > back a 200 response with a blank screen. > > Anyone have any ideas? > > Thanks, > > Dan > > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/76af157d-8a07-4a4f-ba54-1ad54ce3a695n%40apereo.org.
