It's probably an issue with PGTs. Can you log into a non-proxied app?

> -----Original Message-----
> From: Vincent Bonamy [mailto:vincent.bon...@univ-rouen.fr]
> Sent: Thursday, October 22, 2015 7:04 AM
> To: cas-user@lists.jasig.org
> Subject: [cas-user] CAS 4.1.1 and KryoTranscoder ?
>
> Hi All,
>
> Today we tried to update our production CAS server on 4.1.1 version.
> But we failed and we went back to our 3.5.2.1
>
> After starting, the CAS answered correctly and I logged in to my webmail
> (proxy cas) successfully for example.
>
> But the CPU charge was 100% and we had errors like this (we don't have the
> stack trace, I don't know why ...) :
> org.jasig.cas.ticket.registry.MemCacheTicketRegistry] - <Failed fetching
> [PGT-************************************************cEQOZjuIUV-cas.univ-
> rouen.fr,
> java.lang.RuntimeException: Exception waiting for v alue] >
>
> We also got a crash of the JVM (!) :
> """
> # Problematic frame:
> # J
> com.esotericsoftware.kryo.serializers.ObjectField.write(Lcom/esotericsoftware
> /kryo/io/Output;Ljava/lang/Object;)V
> """"
>
> We enabled some features on this CAS 4.1.1 - we set up memcached like
> described on the doc - so we used kryoTranscoder :
> http://jasig.github.io/cas/4.1.x/installation/Memcached-Ticket-
> Registry.html#object-serialization
>
> So I think we will retry to update our CAS on 4.1.1 in production but 
> without
> using this kryoTranscoder (on our 3.5.2.1 we're using memcached without
> kryoTranscoder)
>
> Thanks for any ideas/advices about that.
> --
> Vincent Bonamy
> Pôle SI
> Direction de l'informatique &
> des systèmes d'information
> Université de ROUEN
>
> --
> You are currently subscribed to cas-user@lists.jasig.org as:
> mmoay...@unicon.net To unsubscribe, change settings or access archives, 
> see
> http://www.ja-sig.org/wiki/display/JSG/cas-user

-- 
You are currently subscribed to cas-user@lists.jasig.org as: 
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to