Issues when converting Excel Files

Ola,


i got some troubles on our server (JBoss EAP). Some Threads take about 10 mins until they where killed by Transaction Reaper - please see Screenshot + Threaddump Files attached.

i use a developer oem licence - but i did not have access to Priority Support - i thought this was included?

Joerg

Hi,


Thanks for your posting and using Aspose.Cells.

For license or purchase related questions (like, you don’t have access to Priority Support forums), please post your question in Aspose.Purchase forum.

Since, your issue is related to Aspose.Cells and not Aspose.Total, we have moved your thread to Aspose.Cells forum. Moving thread from one forum to another forum often makes the attachments lost, so we have reattached your files in our post.

We will look into your issue and help you asap.

Hi,


Thanks for your posting and considering Aspose.Cells.

We are afraid, we could not replicate this issue with simple excel file in multiple threads. So please provide us your source excel file which is causing this exception.

We need your source excel file that threw this exception because it seems, this is not a thread related issue and your thread was blocked because something went wrong in Aspose.Cells API because of your excel file. This issue may also be replicable in console application.

Exception
at java.text.DecimalFormat.format(DecimalFormat.java:596)
- waiting to lock <0x000000050f56c488> (a java.text.DigitList)
at java.text.DecimalFormat.format(DecimalFormat.java:525)
at java.text.NumberFormat.format(NumberFormat.java:286)
at com.aspose.cells.a.c.zp.a(Unknown Source)
at com.aspose.cells.a.c.zp.a(Unknown Source)
at com.aspose.cells.a.d.zfi.a(Unknown Source)
at com.aspose.cells.a.d.zfi.a(Unknown Source)
at com.aspose.cells.a.d.zet.b(Unknown Source)
at com.aspose.cells.a.d.zet.a(Unknown Source)
at com.aspose.cells.a.d.zer.a(Unknown Source)
at com.aspose.cells.a.d.zew.a(Unknown Source)
at com.aspose.cells.a.d.zu.a(Unknown Source)
at com.aspose.cells.a.d.zd.a(Unknown Source)
at com.aspose.cells.a.d.zq.a(Unknown Source)
at com.aspose.cells.a.d.zd.a(Unknown Source)
at com.aspose.cells.a.d.zp.a(Unknown Source)
at com.aspose.cells.a.d.zd.a(Unknown Source)
at com.aspose.cells.a.d.zb.a(Unknown Source)
at com.aspose.cells.a.d.zd.a(Unknown Source)
at com.aspose.cells.a.d.zb.a(Unknown Source)
at com.aspose.cells.a.d.zd.a(Unknown Source)
at com.aspose.cells.a.d.zb.a(Unknown Source)
at com.aspose.cells.a.d.zd.a(Unknown Source)
at com.aspose.cells.a.d.zo.a(Unknown Source)
at com.aspose.cells.zap.a(Unknown Source)
at com.aspose.cells.a.d.zew.a(Unknown Source)
at com.aspose.cells.zbwl.a(Unknown Source)
at com.aspose.cells.zbwl.a(Unknown Source)
at com.aspose.cells.zbwl.a(Unknown Source)
at com.aspose.cells.Workbook.a(Unknown Source)
at com.aspose.cells.Workbook.save(Unknown Source)
at com.aspose.cells.Workbook.save(Unknown Source)


Hey there - its not a specific File - but we added one to test.


Important steps may be:
- convert first file
- start conversion of second file in parallel thread

in 5 out of 10 Thread Dumps we saw the mentioned stack.

by the way - we are using these versions:
com.aspose
aspose-words</artifactId>
16.8.0
jdk16
com.aspose
aspose-cells</artifactId>
9.0.0
com.aspose
aspose-slides</artifactId>
16.7.0

Jörg

Hi,


Thanks for your posting and considering Aspose.Cells.

I have tested this issue with latest version by converting your excel file into pdf via the following code in parallel threads and it was OK.

Latest Version Link:


Please try the latest version and check if it could fix your issue. If the issue still occurs, then please share your sample code (console application with multiple threads causing the issue). We will look into it and help you asap.

Java
//This code was run inside multiple threads.
Workbook wb = new Workbook(dirPath + “Mkw-50.xlsx”);
wb.calculateFormula();
wb.save(dirPath + threadName + i + “out.pdf”);

Hey there, thanks for your reply.


We did the Test with your Version 17.03.3. We were able to create Blocks.

Please see thread dumps and testproject attached.

Jörg

Hi,


Thanks for your posting and using Aspose.Cells.

We executed your provided code and it did not give any error. We tested this issue with Aspose.Cells for Java v17.3.3. Please see the attached screenshots and console output for your reference.


Console Output
Starting task : Task 0
Starting task : Task 2
Starting task : Task 1
Starting task : Task 3
Finished task : Task 0
Starting task : Task 4
Finished task : Task 1
Starting task : Task 5
Finished task : Task 3
Starting task : Task 6
Finished task : Task 2
Starting task : Task 7
Finished task : Task 4
Starting task : Task 8
Finished task : Task 5
Starting task : Task 9
Finished task : Task 6
Starting task : Task 10
Finished task : Task 7
Finished task : Task 9
Finished task : Task 8
Finished task : Task 10
Finished all threads

Hi,


Besides, our product team also has tested your case and found, it works fine with our latest version. After making further investigation with the stack trace in your dump data, we found, the result was still generated with old cells version such as 9.0. Please make sure you are testing the case with our latest version.

Latest Version Link:


Hey,


we retested and made sure we used the newest version. We also compared stack and saw changes to old version.

I think we’re testing in different ways. It’s NOT about not ending / closing threads. Every thread is closed in the end.

It’s about what happens while the test project runs. It should take about 2-3 minutes to complete. while it runs we take up to 10 thread dumps. In these dumps we see blocking threads.

So there must be shared objects which cannot be accessed in parallel.

Please find screenshot attached showing how we do the test (see version info in maven left hand side, see repeating thread dumps on lower left side, and the active and running testprogram)

Thanks for your support,

Jörg

Hi,


Thanks for your posting and using Aspose.Cells.

Yes, from the new dump data, we can see that you are using the new version of cells component now. Please confirm that, the current issue you are facing is about performance and not about application crashing or incorrect rendered result.

Since your template file is large, it does need certain time to get the rendered result. Anyways, for the performance issue with multi-threading environment, we have logged a ticket for it and we will make further investigation and try to improve it if possible.

The ticket has been logged as

  • CELLSJAVA-42236 - Performance issue with multi-threading environment

Hey there,


any news on this issue? How can you keep us posted to it?

Thanks,

Jörg

Hi,


Thanks for your posting and using Aspose.Cells.

We are afraid, there is no update for you regarding this issue at this moment. Once, there is some news for you, we will update you by posting in this thread. However, if you do not get any update within a week or more, then please feel free to ask us for the update by posting in this thread, then we will re-check your ticket status and update you.

Hi,

Thanks for using Aspose.Cells.

We have made optimizations for the performance of such multi-threads environments. Please check whether it can solve your issue.

Please download and try the following latest fix: Aspose.Cells for Java v17.3.8 and let us know your feedback.

The issues you have found earlier (filed as CELLSJAVA-42236) have been fixed in Aspose.Cells for Java 17.4.0.


This message was posted using Notification2Forum from Downloads module by Aspose Notifier.