Hi Yves, On Wed, Jun 1, 2011 at 3:13 PM, Yves Dorfsman <[email protected]> wrote: > On 11-06-01 04:40 AM, Adam Tauno Williams wrote: >> >> +1 OpenFire; it really is painless, simple to setup, feature-complete, >> and reliable. Other than being Java container application [Blech!] >> which makes setting up SSL/TLS a pain there really aren't any downsides. >> > > Yes, adding the certificate is a real pain and not well documented.
Stick it in front of a load balancer / apache / nginx and strip the ssl off there? We do this with Openfire and it makes life much happier. In fact, this si what I do for pretty much any java app. May fleas of a thousand camels infest the armpits of the author of java's keytool. > Also, I have found the latest version not as stable as the previous one. It > looks like there's a memory leak in it somewhere. I have "solved" this by > cron'ing a re-start in the early morning when it is the less likely that > anybody's chatting. We hit a similar problem as well after upgrading to the most recent release whereby every 3 days it would crash, regardless of how much memory we set the java heap size to or how big we made various OpenFire caches. Disabling PEP seemed to solve this issue for us, YMMV: * http://community.igniterealtime.org/thread/44006 * http://community.igniterealtime.org/thread/41468 That all said, now that we have it stable, OpenFire is mostly just working. HTH, -n -- ------------------------------------------- nathan hruby <[email protected]> metaphysically wrinkle-free ------------------------------------------- _______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
