That may very well be; There is a request out there to rework the Kryo serialization mechanism and this may be one of those things to account for. Jérôme was planning to work on that next, so he may have better updates.
Feel free to open an issue, or keep an eye on this one: https://github.com/Jasig/cas/issues/631 From: Michaël REMOND [mailto:[email protected]] Sent: Wednesday, October 22, 2014 1:13 AM To: [email protected] Subject: [cas-dev] [Memcache Ticket Registry] Buffer overflow Hello, I deployed the new CAS 4 server in our environment and I encountered a lot of warnings related to Buffer overflow while encoding the CAS ST and TGT. "org.jasig.cas.ticket.registry.support.kryo.KryoTranscoder - Buffer overflow while encoding" I looked at the KryoTranscoder and I understand how the buffer is incrementally extended to get enough space for serialization. I understand also that I have to tune the initialBufferSize parameter to avoid these warnings. However I wonder why the serialization process is implemented this way because one can use the standard Kryo ObjectBuffer class where we can directly pass the Maximum Buffer size. I think this low level work has to be done in Kryo and not in the Memcached Ticket Registry. Any comments? Thanks for your attention, Michaël -- You are currently subscribed to [email protected] <mailto:[email protected]> as: [email protected] <mailto:[email protected]> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
