Just another Jabber server

Just in case you haven’t noticed: We’re experiencing quite a nasty bug (maybe, not proven yet) inside ejabberd which leads to a) ejabberd eating all of the available memory and b) afterwards having one thread run at 100% CPU. At this time, ejabberd stops forwarding packets and accepting new connections.

Just to keep you informed.

P.S.: We do have a Twitter account that might (!) have more up-to-date information than you can find in this blog: @jabberccc.de

Since these downtimes started, I noticed an additional phenomenon – if I write a message to an offline buddy from my contact list (using Pidgin 2.10.7 on Ubuntu 12.04), I get the following error message (but only if his account is also a jabber.ccc.de one):

Yeah, so since a few days (week?) jabber.ccc.de is no usable for me. Failures to connect and if connections work failures to deliver messages. Do you have any news on that bug? Otherwise I have to switch the jabber provider.

Verified. Stopped working last night. Also I got 15+ messages that a message could not be delivered after my login (why? I was offline).

This is a free project, maintained by someone in his free time. I know how it feels. If it works, you won’t get any thanks. If it not works, all people will start writing bad things about you or the project. That’s the bad side about FLOSS. But IMHO many people are using jabber.ccc.de and some of them might have an idea how to fix it. A little bit more communication might help.

I use jabber.ccc.de with the recent pidgin Version Pidgin 2.10.9 (libpurple 2.10.9) under linux 64bit. I cannot send messages to offline users of jabber.ccc.de. Other jabber server work. Everytime I get Error code 503. This happens since a short while 2-3 weeks or so. Tryed Web jabber over ssl port 443 193.110.90.42 and normal jabber over port 5222. Plz fix this its really annoying.