Details
-
Bug
-
Resolution: Unresolved
-
None
-
None
-
High
-
There was a seldom problem where a task was not marked to have termcollections although there where some associated.
-
Empty show more show less
Description
problem
In a task no terminology was tagged, although the task had some term-collections associated.
workaround
remove the associated term-collection and associated it again.
reason
The "terminologie" field in the task was set to 0, due an error coming from the termtagger on opening the TBX file:
level: ERROR ecode: E1117 domain: editor.terminology.analysis message: editor_Plugins_TermTagger_Exception_Open: Could not load TBX into TermTagger: TermTagger HTTP result was not successful!
with the following termtagger result:
Zend_Http_Response Object ( [version:protected] => 1.1 [code:protected] => 400 [message:protected] => Bad Request [headers:protected] => Array ( [Date] => Wed, 23 Feb 2022 16:31:51 GMT [Content-type] => application/json [Content-length] => 54 ) [body:protected] => { "error": "NO_TBX_FILE", "uuid": "", "added": false } )
reason in the termtagger
It seems that multiple termtagger instances on the same working dir have received the same file in the same time:
t5-termtagger-9002.log.2:0/23.2.2022 17:31:51,749/simpleCopyStringToFile|1595|de.folt.util.OpenTMSSupportFunctions|/ Copy string to file: "./e8500dea6fc157d6283a3fbb74dee21a.tbx" with length content = 608708 t5-termtagger-9003.log.2:0/23.2.2022 17:31:51,689/simpleCopyStringToFile|1595|de.folt.util.OpenTMSSupportFunctions|/ Copy string to file: "./e8500dea6fc157d6283a3fbb74dee21a.tbx" with length content = 608708
Since the different instances are running in the same working dir it seems the one file upload has deleted the intermediate disk save of the file. At least the following exceptions suggest that:
(java.lang.NullPointerException at de.folt.models.applicationmodel.termtagger.TermTaggerTbxFile.createInstance(TermTaggerTbxFile.java:214
Which is then leading the above HTTP 400 of the termtagger.
Long Term solution
One java termtagger per node
improvement in translate5
If the terminologie flag is set to 0, the associated termcollections should be removed from the task. So that its clear for the user why there are no terms tagged.