Conversions hangs with waiting on lock owned by thread

GroupDocs.Conversion Product Family
1

We have the problem at a customer installation, that conversions from docx to pdf do not complete. The threads seem to hang and never complete.

We have now organized a dump file of our service and in the dump we see many waiting threads originating a conversion, for instance:

image.jpg (166.3 KB)

or

image.jpg (177.9 KB)

The referenced thread has the following stacktrace:
image.png (7.4 KB)

Since we don’t have the source code, we have no idea, what is blocking the conversion. It seems you call internally GetFontsSources/SetFontsSources which is waiting for a lock on something.

Can you please elaborate what is causing this problems? We have dozens of threads hanging during conversion which will eventually crash our service, since they are filling up the threadpool and never complete.

We use the 23.08 conversion library

Many thanks,
Robin.

2

@Vitodata
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CONVERSIONJAVA-2294

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

3

@Vitodata

We attempted to replicate the issue using various source files but were unsuccessful. Could you kindly provide a simple console application using that issue could be reproduced at our end, along with the corresponding source file(s)?

4

updating to a newer version of the library this problem seems to be fixed. Nevertheless, we would need a fix for CONVERSIONNET-6470 because this is blocking any futher upgrade for us

5

@Vitodata

We are already working on this ticket. We’ll notify you of any progress update.

6

Hi
Did anyone got resolution for this issue as we are facing the same with 23.10 version onwards .

7

@Vitodata @sandeepsuthari

Could you please share the sample application using that issue could be reproduced?

8

Hi @atir.tahir
We can’t share that environment and it won’t be very straightforward either .
Since the logs are obsurfucated we need your dev’s help to debug this .

9

@sandeepsuthari

We still need the following details in order to reproduce or further investigate the issue:

  • The problematic/source file that is causing the issue
  • The output format type you are attempting to convert the source file to
  • A sample conversion code covering the ConverterSettings, if you are using any
10
1 Like
11

@sandeepsuthari

Would it be possible for you to share a screencast/short video, explain steps to reproduce the issue. And as per this thread, do you face this issue on production server only?
One more clarification, the other thread you are referring to is regarding Java variant of the API but in this thread, you referred you are using 23.08, that comes in .NET.

12

I am using Java only this .NET is faced by some another customers of yours it seems.

13

@sandeepsuthari

Thanks for the confirmation. We’ll continue our investigation and notify you in case of any update.

14

@sandeepsuthari

Please download, integrate this JAR and share a output of this (into the log).
Your application will need following dependencies:

<dependency>
    <groupId>org.apache.logging.log4j</groupId>
    <artifactId>log4j-api</artifactId>
    <version>2.7</version>
</dependency>
<dependency>
    <groupId>org.apache.logging.log4j</groupId>
    <artifactId>log4j-core</artifactId>
    <version>2.7</version>
</dependency>
<dependency>
    <groupId>org.apache.logging.log4j</groupId>
    <artifactId>log4j-slf4j-impl</artifactId>
    <version>2.7</version>
</dependency>
15

@Vitodata @sandeepsuthari one of the possible reasons may be that you have the working directory in the root of the container / OS filesystem.
So please try to change it, for example you can create the app directory for your jar and change the working directory:
WORKDIR “/app”