Idea Portal
Whenever additional descriptors are added to a document class that is used by the rendition-server, the rendition server has to be restarted even though that descriptor has nothing to do with the rendition configuration. This is very counter intuitive, we always forget about it and get rendition errors (see below).
From our point of view, the rendition server should be more resilient in this regard.
10.03.2023 14:54:09.416 Error Thread 201 Dxr.Dispatcher.doxis4-RenditionLocalDB.SEW_DE_Bruchsal_Produktion Commit failed for DocID SD17SEW_TECHNISCHEDOKUMENTE2444f04c13-beba-4585-af50-a452c8116af4182023-03-10T13:45:29.972Z030.3
10.03.2023 14:54:09.416 Error Thread 201 Dxr.Dispatcher.doxis4-RenditionLocalDB.SEW_DE_Bruchsal_Produktion Exception type: Dxr.Dispatch.DispatcherException
Message: Commit failed: Reason: The descriptor 'Boolscher Wert 4' is not defined in the document class 'DriveDoc'.
We will improve error handling in COM API which in turn then will improve the behavior of the rendition server dispatcher. I.e. the above mentioned scenario will not cause an error then.
This issues occurs in those situations where a descriptor is added to a document class and a document is already archived with a value for this new descriptor and then converted within the first 4 hours. This is due to caching of this type information in the COM API.
However, dispatcher of rendition server is already somehow resilient in this case as it reconnects and reloads the cache in the COM API every 4 hours by default. After that these documents are processed correctly.
We keep this idea open in order to check whether we can improve error handling in the case in the future and to get feedback whether the existing behavior affects other customers