When trying to import a rather large amount of Translation Unit content into a server-based Translation Memory, the import task (not the upload of the file that is getting imported) is cancelled always after ~30-35 minutes which is displayed in the Background Tasks view.

Example:

Workaround/Solution

Option 1: Steps to adjust the timeout value:

1. On the server where RabbitMQ is installed go to: C:\Users\[USER FOLDER]\AppData\Roaming\RabbitMQ
   Note: The correct user folder is the one which was logged in to install RabbitMQ Server.

2. Open the rabbitmq.conf in a text/xml the file.
   Note: If the rabbitmq.conf does not exist create a text file and rename it (including the file type extension) to rabbitmq.conf
3. Add the following content:

   # 24 hours in milliseconds consumer_timeout = 86400000

4. Save the changes and restart the RabbitMQ Server service and GroupShare Services via the Trados GroupShare Console or Services Console (services.msc).

 

Option 2: Steps to disable the timeout value (NOT recommended):

1. On the server where RabbitMQ is installed go to: C:\Users\[USAER FOLDER]\AppData\Roaming\RabbitMQ
   Note: The correct user folder is the one which was logged in to install RabbitMQ Server.
2. Open the config in a text/xml the file.
3. Add the following content:

   [ {rabbit, [ {consumer_timeout, undefined} ]} ].

4. Save the changes and restart the RabbitMQ Server service and GroupShare Services via the Trados GroupShare Console or Services Console (services.msc).

Examples of configuration files can be found in the attachment.

As of RabbitMQ versions 3.8.17 or higher, a timeout is enforced on consumer delivery acknowledgement. If a consumer does not acknowledge its delivery for more than the timeout value (30 minutes by default), its channel will be closed with a PRECONDITION_FAILED channel exception. The error will be logged in the RabbitMQ log file located by default in C:\Users\[user folder]\AppData\Roaming\RabbitMQ\log.

The timeout value is configurable in the rabbitmq.conf (in milliseconds).
Alternatively, the timeout can be completely disabled by configuring the advanced.config (not recommended).