Skip to end of metadata
Go to start of metadata



Date and Time: Every Wednesday, 12:00-1:00pm ET / 11:00-12:00pm CT / 9:00-10:00am PT

  • Video Bridge 220488, Dial 812-856-7060 to connect via phone (conference number 220488#, See PolyCom Directory for connection info)
  • Xmeeting(Mac) :
  • Ekiga(Linux) :

Mailing List:


  1. Roll Call
  2. What to do about SessionDocumentService?
    • Causing performance problems at multiple schools
      • Serializes form and saves to database on every request/response
    • Do we really even need it?
      • Other solutions for session replication (i.e. Terracota web-sessions)
  3. KULRICE-8847 - Role lookups slow when there are over 200 roles (Peter Giles)
    • Can we leave role members off of roles for lookups?


  • Eric Westfall
  • Peter Giles
  • Bryan Hutchinson
  • Gayathri Athreya
  • Claus Niesen
  • Erik Meade
  • Chad Hagstrom
  • Shannon Hess
  • Jeremy Hanson
  • Larry Symms
  • Jeff Caddel
  • Jonathan Keller
  • Will Gomes
  • David Elyea
  • Chris Denne


What to do about SessionDocumentService?

  • Eric - seems to have caused performance problems for just about everyone who has ever implemented a Kuali app anywhere, ever
  • Gayathri - have had reports from Hawaii and other schools
    • have disabled it for all of KC
  • Eric - my suggestion is just to remove it from KRAD
    • does anyone think this is a bad idea?
    • Jonathan - only thing you will lose is if you are running one server but it's a very specific case when this thing even works to restore the session
      • it presumes the user does not touch their screen during the time the server is rebooting
  • Peter - do we need to do anything in Rice to enable using other session replication tools or are they magical enough
    • Jonathan as long as we put distributed in web.xml the container can handle
    • Eric - Terracotta also has the ability to handle this
    • and yes, everything in session has to be serializable
      • Kuali Rice has a NonSerializableSessionListener which is enabled only in development that raises exceptions if anything non-serializable ends up in the sessions
      • serves as a safety net from those pesky developers
  • Jonathan - wonder if we want to stub out the "NoOp" implementation as the default?
    • for any of the large KFS documents, you will have a problem
    • KC - it would be better for us if it were in 2.1.5 instead of 2.1.4 since we are pretty close
      • still unclear if there will be a 2.1.5 at this point in time
  • Eric will enter jiras for 2.1.5 and next 2.2.x version to get this removed

Jiras Created:

* KULRICE-9148 - Data cannot be retrieved due to an unexpected error
* KULRICE-9149 - Data cannot be retrieved due to an unexpected error

KULRICE-8847 - Role lookups slow when there are over 200 roles (Peter Giles)

  • just wanted to mention this to folks so that they are aware of it
  • want to make sure that making this change won't break something that I don't know about
  • no objections to the proposed change from the group

Open KULRICE JIRAs Marked for KTI Review

key summary assignee reporter fixVersion priority created updated Received fatal alert: handshake_failure

View these issues in JIRA
  • No labels