Aspose Words (JAVA), returning HTML document missing content

Aspose.Words Product Family
1

Hello, we’ve run into an instance with a customer where RTF documents being sent in, get processed and returned with “shell” of a html document. The content of the document itself is missing. This shell is identical with the returned HTML always being the same 414 bytes (one way we are identifying failures with a quick database query on stored document lengths).

This is the document being returned:

  <html>
  <head>
  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
  <meta http-equiv="Content-Style-Type" content="text/css" />
  <meta name="generator" content="Aspose.Words for Java 24.1.0" />
  <title>
  </title>
  </head>
  <body style="font-family:'Times New Roman'; font-size:12pt">
  <div>
  <span style="-aw-import:ignore"> </span>
  <br/>
  </div>
  </body>
  </html>

Now here’s the odd part, the client resends the failed documents in for reprocessing and it will work… eventually. That indicates the RTF is able to be processed. This client sends in thousands of RTFs per day with very low failure rate (ie: missing content) so Aspose is working most of the time. These failed documents are critical however to their work flow.

We’ve yet to reproduce this in house, it seems to be only on a system under heavy load. Other clients dont see this issue (to our knowledge).

We are wondering if this type of behaviour has been seen before? Any anyone knows of a cause or more importantly a fix?

Dallan Christensen
Solventum Health Information Systems (previously known as 3M Health Information Systems)

2

@Dallan_Christensen

It appears you are encountering an issue where RTF documents are being processed into HTML but are missing content, resulting in a consistent “shell” of an HTML document. This problem may be related to the processing load on your system, as you noted that it occurs under heavy load and resolves when the documents are reprocessed.

Here are several suggestions to troubleshoot and potentially resolve the issue:

  1. Validate RTF Content: Ensure that the RTF documents being processed are valid and contain the expected content. Malformed RTF can lead to unexpected results during conversion.

  2. Resource Allocation: If the issue is related to system load, consider increasing the resources (CPU, memory) allocated to the application processing the documents. This may improve the handling of the documents.

  3. Implement Logging: Set up logging to capture any errors or warnings during the processing of RTF files. This can help identify specific documents or conditions that lead to the issue.

  4. Check for Updates: Ensure you are using the latest version of Aspose.Words for Java, as updates may include bug fixes or improvements that could address this issue.

  5. Simulate Load Conditions: Attempt to replicate the issue in a controlled environment by simulating heavy loads. This may help identify the specific conditions under which content is lost.

If the problem persists, consider reaching out to Aspose support with detailed logs and examples of the problematic RTF files for further assistance.

3

@Dallan_Christensen Could you please zip and attach the problematic RTF document here for testing? We will check the issue and provide you more information.