I should clarify, this has been seen in v4.2.5, as that was the latest
version of CAS at the time. 4.2.6 doesn't seem to have any commits
targeting this issue specifically. I'm definitely gunning for v5 when it
drops in GA.
For now, I think I'm going to turn on max debug in production to see if
4.2.2, right? One other suggestion would be to get on the latest release in the
4.2.x series, that is 4.2.6 ... or even get on the v5 bandwagon
Cheers,
D.
On Nov 1, 2016, 21:24 -0400, Jeffrey Wong , wrote:
> This issue occurred again tonight. Nothing of note in the logs again, with
> plenty of
This issue occurred again tonight. Nothing of note in the logs again, with
plenty of jvm memory + disk space left. It just will start redirecting
users to the login page as if a failed login occurred, but without
displaying any error messages.
Typing in an incorrect password is caught and the e
On suggestions from another user with similar issues using JPA, I have
changed and deployed CAS using a hazelcast ticketing database.
I'll let you know if I have any success with this configuration.
On Thursday, September 22, 2016 at 11:55:16 AM UTC-7, Jeffrey Wong wrote:
>
> Hi again,
>
> It's
Hi again,
It's been about a month and have regularly screened the JVM memory - it
looks fine since the memory bumps, running CAS v4.2.4.
However, the server fell over again (using the JPA ticket registry), with
the same behavior: upon entering correct credentials, a user is redirected
back to
Ah, JVM stats. Thanks for that tip: I really wasn't looking at my memory
closely enough, and I still had a -Xmx128m set (tomcat7 default in ubuntu). I
bumped it to 1g (actually this time, confirmed via /status this time) so I'm
hoping this helps resolve.
Ah! That should do it. I am surprised yo
emoved as
>> part of those TGTs which you see the removal in the logs but not in the
>> final count of them.
>>
>> Do file a bug please.
>>
>> Back to the original issue; the cleanup process seems all correct. The
>> issue lies somewhere else.
>>
where else.
--
Misagh
From: Jeffrey Wong
Reply: Jeffrey Wong
Date: August 24, 2016 at 2:20:36 PM
To: CAS Community
Cc: mmoa...@unicon.net
Subject: Re: [cas-user] After a month, no tickets created in 4.2.2?
I'm still getting inconsistent ST cleanup summaries using 4.2.5-SNAPSHOT with
the de
rocess seems all correct. The
> issue lies somewhere else.
>
> --
> Misagh
>
> From: Jeffrey Wong
> Reply: Jeffrey Wong
> Date: August 24, 2016 at 2:20:36 PM
> To: CAS Community
> Cc: mmoa...@unicon.net
> Subject: Re: [cas-user] After a month, no tickets created in 4
mmoay...@unicon.net
Subject: Re: [cas-user] After a month, no tickets created in 4.2.2?
I'm still getting inconsistent ST cleanup summaries using 4.2.5-SNAPSHOT with
the default in memory cleaner - See the attached log.
Note that all service tickets are found for cleanup, but only two
ch of tests against that
> baseline, and if you still see the issue, please post back.
>
> --
> Misagh
>
> From: Jeffrey Wong
> Reply: Jeffrey Wong
> Date: August 23, 2016 at 2:33:34 PM
> To: CAS Community
> Cc: mmoa...@unicon.net
> Subject: Re: [cas-use
of tests against that baseline, and if you still see
the issue, please post back.
--
Misagh
From: Jeffrey Wong
Reply: Jeffrey Wong
Date: August 23, 2016 at 2:33:34 PM
To: CAS Community
Cc: mmoay...@unicon.net
Subject: Re: [cas-user] After a month, no tickets created in 4.2.2?
Also to
exception to this rule is, proxy-tickets are
>> not removed by the clean up process when you “logout” forcefully, and this
>> something that is fixed in the next patch release, thanks to William. But
>> you’re not using PTs, so...
>>
>> --
>> Misagh
>>
blem is something else, it will
>> simply repeat and your new registry will have done nothing to fix it. I
>> would instead turn up logs, load test as much as possible and keep it
>> running under test for some time. Observe.
>>
>> --
>> Misagh
>>
Wong
Reply: Jeffrey Wong
Date: August 22, 2016 at 3:50:03 PM
To: CAS Community
Cc: mmoay...@unicon.net
Subject: Re: [cas-user] After a month, no tickets created in 4.2.2?
I am not making use of proxy granting tickets, but I'll report back if it's
still an issue once 2.2.5 drop
effrey Wong
> Date: July 20, 2016 at 3:27:17 PM
> To: CAS Community
> Cc: mmoa...@unicon.net
> Subject: Re: [cas-user] After a month, no tickets created in 4.2.2?
>
> Grepping through what I have, I can confirm that the tickets are being
> removed, as
. Observe.
--
Misagh
From: Jeffrey Wong
Reply: Jeffrey Wong
Date: July 20, 2016 at 3:27:17 PM
To: CAS Community
Cc: mmoay...@unicon.net
Subject: Re: [cas-user] After a month, no tickets created in 4.2.2?
Grepping through what I have, I can confirm that the tickets are being removed,
as
set up to allow the cleaner to expire and clean tickets
> successfully?
>
> Without logs, it’s just a guessing game. My bet is, somehow you’ve run out
> of memory.
>
> --
> Misagh
>
> From: Jeffrey Wong
> Reply: Jeffrey Wong
> Date: July 19, 2016 at 3:1
Wong
Date: July 19, 2016 at 3:10:05 PM
To: CAS Community
Subject: [cas-user] After a month, no tickets created in 4.2.2?
After about a month of working perfectly on 4.2.2 deployed to tomcat7, running
under java8, randomly the in-memory ticketing system would not create any more
tickets
After about a month of working perfectly on 4.2.2 deployed to tomcat7,
running under java8, randomly the in-memory ticketing system would not
create any more tickets. Restarting the tomcat instance fixed it, but I'm
wondering why CAS would randomly break on me after working so well! Using a
LDA
20 matches
Mail list logo