-
Bug
-
Resolution: Unresolved
-
None
-
None
problem
When termtagger is on fire the following error might happen:
E1117: Could not load TBX into TermTagger: TermTagger HTTP result was not successful!
Most likely this is the case when the request taking over the TBX data is taking to long. Since mutiple requests are doing that anyway (sending that TBX) chances are good that TBX exist in the termtagger a few seconds later.
The body of the answer must be JSON with a field error containing the string "TBX_ID_ERROR" - example dump from the logs::
"plainServerResponse":"Zend_Http_Response Object\n(\n [version:protected] => 1.1\n [code:protected] => 400\n [message:protected] => Bad Request\n [headers:protected] => Array\n (\n [Date] => Wed, 15 Jan 2025 14:38:52 GMT\n [Content-type] => application\/json\n [Content-length] => 54\n )\n\n [body:protected] => { "error": "TBX_ID_ERROR", "uuid": "", "added": true }\n)\n"
solution
In case of exactly that error we should wait some seconds round about 4 seconds then do just the same call again. We should do that only once - since problem should be gone after a few seconds.
Addition by Marc: I would not do that only once, but several times (configurable). Because we want to avoid the error on high load and only get to know if really something is wrong.