[Building Sakai] Memory leak in Courier Service

[Matthew Jones]

Chat (new or old) still uses it, new presence was the one that got switched
from using it.

It's still an issue but wasn't a huge/fast leak and basically just meant
the best practice was weekly restarts for highly active instances.


On Fri, Sep 20, 2013 at 11:07 AM, Beth Kirschner <bkirschn at umich.edu> wrote:

> We're still using the old chat, though I thought that the Courier Service
> was deprecated and so not used by the old chat?
>
> - Beth
>
> On Sep 20, 2013, at 10:00 AM, "Maurer, Christopher Wayne" <chmaurer at iu.edu>
> wrote:
>
> > https://jira.sakaiproject.org/browse/SAK-21398
> >
> > We believe we've been running into this old-ish issue lately.  We
> upgraded to 2.9.0 back in May but didn't notice issues until load really
> picked up at the beginning of the fall semester a couple weeks ago.  Are
> other 2.9 people still running the "old" style chat or has everyone
> switched over to the "neo" chat (I've been out of the sakai game for pretty
> much the whole year…is it still called that?)  Trying to determine if the
> best course of action is to try and get the old one working better, or
> switch to the new.  Thoughts?
> >
> > Chris
> > _______________________________________________
> > sakai-dev mailing list
> > sakai-dev at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >
> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130920/66035cf4/attachment.html