OpenJDK Runtime Environment 18.9 (build 11.0.6+10-LTS) OS is not relevant as the problem occurs in every environment but I am attaching the OS info that we are using in our docker container regardless and for clarity. Our solution with time outing threads seems more like a hack than a proper fix. This is especially concerning because we plan to use Aspose on the server and we cannot guarantee that all documents will contain only available fonts.ĭo you have any advice on how to proceed and properly handle this problem? However, a few documents have fatal effects. Either with substituted fonts or with missing characters. The majority of documents with missing fonts will be converted. If all fonts are available we haven’t observed this behavior. If the conversion process (load document and save it as PDF) does not happen during a certain time period, we kill the thread and the underlying Aspose process with it. We mitigate this issue by spinning a new thread for each Document instance. No exception is thrown, Aspose utilizes the CPU at 100% without a possibility to recover. This happens when we try to instantiate the Document class by providing a certain Word docx document that uses fonts, which have not been previously loaded by FontSettings. We’ve been heavily testing Aspose Java Word for documents to PDF conversion and we found a few documents that cause the underlying Aspose process to stuck.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |