Tigase server automatically shuts down after several hours

Peter Rajcani
Added almost 4 years ago

We are runnin a Tigase server configuration in a cluster of 2 machines. We have noticed that the cluster manager is shutting servers down after several hours (the servers were restarted around 10 am this morning and they shut down automatically around 4 pm). Is there a reason for this? Is there a configuration setting that can prevent automatic shutdown? Before we started using the cluster configuration, the server was running all day and only shut down when we restarted it.

Here is our file:

--comp-class-1 = tigase.muc.MUCComponent
--virt-hosts =
--user-db-uri = jdbc:mysql://
--user-db = mysql
--admins =,,,
--comp-name-4 = message-archive
--comp-name-3 = proxy
config-type = --gen-config-def
--comp-name-2 = pubsub
--comp-name-1 = muc
--cluster-mode = true
--sm-plugins = +message-archive-xep-0136,-jabber:iq:register
--debug = server
--comp-class-4 = tigase.archive.MessageArchiveComponent
--comp-class-3 = tigase.socks5.Socks5ProxyComponent
--comp-class-2 = tigase.pubsub.PubSubComponent

I have attached a portion of the log that suggests shutdown occurred because we using the ACS component without a license (as I unsrestand it can be used for testing and evaluation purposes).

Replies (3)


Added by Artur Hefczyc TigaseTeam almost 4 years ago

Everything is correct. The ACS can be used with evaluation license but as the licensing information states, terms of running it in this development/testing mode, require that the ACS component sends some statistical information to our servers. If it cannot connect to our servers it will shutdown the server after a few attempts.

So, there are 2 solutions for you to get it working:

  1. Unblock communication between your installation and our servers (HTTP connection to our server)

  2. Purchase a full, commercial license

Added by Peter Rajcani almost 4 years ago

I see, thanks for the explanation. We are using the ACS with evaluation license, Right now Option 1 is not viable for us b/c we cannot unblock communication from our internal servers due to our security regulation. Option 2 will take some time since it has to go through several departments. Right now the severs automatically shuts down after about 2 hours. Is it possible to change this in the configuration so it stays open longer, say 10-12 hours before shutting down? Is there a time limit?


Added by Artur Hefczyc TigaseTeam almost 4 years ago

There is a third option. We can provide you with a time limited (3 months) evaluation license at no cost. This way you can run tests and develop your system without interruption, while sorting out business and legal paperwork.

If you are interested, please send us a message. Provide with your contact email, company name and address and we will generate a license for you.