Hi @evgen.efimov
We are repeatedly encountering the issue mentioned above, which is affecting the performance of our application. Is there any progress on this issue?
Hello @Vaibhavj22 ,
We apologize for the delay. At this time, we have not yet resolved the issue with missing images when converting .msg
or .eml
files to .pdf
. However, we have assigned it a high priority and will do our best to ensure that the fix is included in the Conversion 25.2 release.
Regarding the process freezing when converting documents:
- If you are converting a spreadsheet to a PDF, you can use
SpreadsheetLoadOptions.setOptimizePdfSize(true)
. This will reduce the output PDF size and speed up the conversion process. - As for converting WordProcessing documents to PDF, we have prepared some fixes that are expected to be included in the 25.2 release.
- Regarding PowerPoint to PDF conversion, we are still investigating the issue. We have tested your files but have not observed a significant increase in conversion time between the two library versions. Perhaps you could provide us with some additional files for testing?
Hi @vsevolod.orefin !
Can you say more about this working directory issue? In your investigations have you found that setting a non-root working directory resolves this issue with Groupdocs conversions hanging?
And if so, can you clarify what you mean? Our application, which is still using GroupDocs.Conversion 23.11.1, is located inside a directory (d:\MyApp), and it is hosted by Tomcat, with a <Context path="" docBase="D:\MyApp">...
. Are you suggesting that adding a workDir
attribute to our context configuration may resolve our issue?
We are under the impression we should stay on conversion 23.11.1 because it handles .msg
and .eml
files the best in our tests.
Hi @rkilgoreaquent ,
Since I tested it on the console application, I used the WORKDIR command in my Dockerfile to change the working directory. I didn’t test it for a Tomcat application. So you can try to set this workDir for the Tomcat.