Jabber.co.nz » Jabber.org

By: Jabber  06-Dec-2011

This is the jabber.org service notice for Tuesday, January 26, 2010.

The team feels that it turned the corner yesterday and that we are on the path to a very stable and full-featured IM service. Some of the changes we’ve made are “behind the scenes” (better work processes for monitoring the service in real time, rotating logs to prevent a full disk on our server machine, etc.) so you won’t immediately notice them, but they are definitely improving reliability. In addition, the Isode team is hunting down some elusive bugs (e.g., regarding DIGEST-MD5 authentication, which is notoriously confusing for developers and has a lot of interoperability problems).

Our primary open issues are:

1. Memory usage. For reasons that we and Isode still don’t fully understand, memory usage slowly increases after a restart, causing the server run out of memory on the machine. We now have automated processes in place to restart the server when memory usage approaches the limit. This means that we’re having a few restarts every day, but they are controlled (even if not announced ahead of time). Fixing this problem is the top priority right now.

2. Google Talk connectivity. Some messages get lost from Google Talk to jabber.org. We’re working to figure out the conditions that cause this problem, because it is intermittent and might depend on which client you use.

3. vCards. Currently birthday and home page are not saved in user vCards. Isode is working to fix this relatively minor bug.

Other products and services from Jabber


Jabber.co.nz » Jabber NZ - jabber nz

Today I hit the move button to move jabber.co.nz to its’ new serverI’ve changed transports from py-transports to spectrum, so hopefully things will work a bit better, plus the server is bigger better fast. Downtime should be limited to DNS ttl. Let me know if anything is awry.


Jabber.co.nz » Jabber.org - jabberorg

We will continue to encourage developers of those clients to add STARTTLS support and we reserve the right to turn off port 5223 at some point in the future, but we probably won’t do so until platforms like OS X Tiger and KDE 3 have been end-of-lifed. Second, the old legacy SSL port 5223 is working again, enabling you to connect using most older clients as well as various “crippled” clients that still don’t support STARTTLS on port 5222.


Jabber.co.nz » Jabber NZ

I discovered I was “mixing and matching” storage options on the jabber service. With my current config I should be able to support 000?s of concurrent users.. I went through and cleaned up my config and haven’t had a complaint so far. I had some memory issues with only 5 online users ….