-
Bug
-
Resolution: Unresolved
-
None
-
None
-
High
-
FIX: in rare cases OKAPI fails to process projects in situations of high workload. The situation is solved by retrying the process in such cases.
-
Emptyshow more show less
Problem
When task has 300+ files occasionally there are random errors on import or export with Okapi (see related issue)
There seems to be a concurrency issue on Okapi Longhorn side, that causes this problem, when sending different files with the same bconf from different tasks (from the same task we anyway already send only the next file, when the previous returned).
The errors are:
net.sf.okapi.common.exceptions.OkapiIOException: java.io.FileNotFoundException: /var/lib/jetty/Okapi-Longhorn-Files/2/config/extensions-mapping.txt
net.sf.okapi.common.exceptions.OkapiIOException: java.nio.file.FileAlreadyExistsException: /var/lib/jetty/Okapi-Longhorn-Files/2/settings.bconf
Solution
- All OKAPI instances in the container use the same project-folder
- Fix location of "okapi-longhorn-configuration.xml" which is not respected to /var/lib/jetty
- use UUIDs for projects instead of IDs
- optional: Patch version-string in the *.war files (unzip them, change in pom.properties, pom.xml & version.properties )
- relates to
-
TRANSLATE-5070 Random errors on import/export of a large task with Okapi
- Done