Tigase.org is the website of the Tigase XMPP/Jabber Server

I wonder what is the longest running XMPP service without a restart.

I watch a few servers running Tigase but then I restart them from time to time for software update with new features or bug fixes.

One of them is im.flosoft.biz which runs on quite old Celeron 1.33GHz machine with 200MB memory. Serves approximately 800 online users and works well for 75 days already without a restart. This is a development version of the Tigase 5.1.0 branch but indeed, Florian pushes me to release it as another stable version.

I have found however an absolute winner in this 'competition'. The last time I checked it earlier today the Tigase uptime time was: 657 days, 6 hours, 53 mins, 21 secs. This is a service running on MS Windows machine for online gaming website and most of the user connections are web clients connecting via Bosh. It is still running and working well!

I have also received a few other reports from people successfully running Tigase, as they say for 2 years without restart. If you have any specific data, number of days, the software version, please add a comment to this article. I would like to hear about your experience with long-running Tigase server.

The Tigase server 5.1.0 or later offers new, rewritten from scratch implementation for s2s communication which allows you to tweak it's configuration to get a better performance in your installation.

S2S (or server to server) protocol is enabled by default with setting which are optimal for the most common cases. There is however a set of configuration parameters you can adjust the server behaviour to get an optimal performance for your installation.

This documents describes following elements of the Tigase server configuration:

1. Number of concurrent connections to external servers
2. The connection throughput parameters
3. Maximum waiting time for packets addressed to external servers and the connection inactivity time
4. Custom plugins selecting connection to the remote server

This may affect the server performance so it is not enabled by default and there is a couple of things you have to set to get it function properly.

Configuration is not very complex but as the AMP is implemented as a component in the Tigase server it does needs a few settings to get it right.