09-17-2015 06:32 AM
09-19-2015 02:36 PM
10-06-2015 04:33 AM
10-06-2015 07:28 AM
10-07-2015 05:03 AM
10-07-2015 05:24 AM
10-07-2015 06:32 AM
11-23-2015 09:02 AM
01-29-2017 07:35 PM
old topic, but just got the same Problem with 32 cores on latest version 201701.
soffice.bin got stuck converting using 1 core (99%) and the upload runs into the timeout. seems like the socket is blocked.
01-30-2017 01:56 AM
That soffice process being stuck on 1 core is actually not a bug / issue. The default OOoDirect subsystem that connects to OpenOffice / LibreOffice for conversion can only support one transformation at a time - the Enterprise Edition of Alfresco provides an alternative JODConverter subsystem that can handle multiple transformations at a time. So for Community Edition soffice will always only use at most one core because there is just one single transformation in a single process.
Unfortunately, soffice has a habit of choking on complex MS Office documents leading to constant 100% core usage. This is a know issue and the reason why Enterprise Edition JODConverter has a timeout and active process restart handling. On Community Edition, you have to use some kind of watchdog to monitor the soffice process and restart it yourself when it gets stuck. There are various post on this topic in the Alfresco community, e.g. from Zylk or Contentreich. I have recently created my own, slightly more elaborate watchdog as a small Java library for a customer that performs the same kind of transformations as Alfresco would to test process viability.
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.