We are using Aspose Cells (ver 7.2.1) to generate and excel file (based on an excel template).
Sometimes we get the below exception and are not able to generate the excel file.
[11/19/12 9:26:16:762 EST] 0000005b SystemErr R java.lang.IllegalArgumentException: Arg_DateTimeRange [11/19/12 9:26:16:763 EST] 0000005b SystemErr R at com.aspose.cells.DateTime.(Unknown Source) [11/19/12 9:26:16:763 EST] 0000005b SystemErr R at com.aspose.cells.CellsHelper.getDoubleFromDateTime(Unknown Source) [11/19/12 9:26:16:763 EST] 0000005b SystemErr R at com.aspose.cells.pH.a(Unknown Source) [11/19/12 9:26:16:763 EST] 0000005b SystemErr R at com.aspose.cells.Cell.putValue(Unknown Source) [11/19/12 9:26:16:763 EST] 0000005b SystemErr R at com.aspose.cells.Cell.putValue(Unknown Source)
However, if we restart our application servers then the same excel starts generating properly.
The call being made through java is cell.putValue(value, true); where value is a string representing the date time.
Please let me know in case this is an issue with the Library version we are using.
Thanks in advance.
Hi,
Thanks for your posting and using Aspose.Cells for Java.
Please download and try the latest version:
Aspose.Cells
for Java v7.3.3.3
If your error still occurs, then we will need your sample code and source xls/xlsx files replicating this issue with the latest version.
We will look into it and help you asap.
Hi Shakeel,
Thanks for looking into it promptly. There is one issue with the approach you have suggested.
We are getting the error in our production environment and not in any pre production environment. As a result we cannot directly replace the Jar. Can you provide any other suggestions or work arounds that we can try out first? Is the number of users (both concurrent and otherwise) who are accessing this functionality causing any issue?
Hi,
Thanks for your input.
Aspose.Cells for Java itself is thread-safe. Means, you can use Aspose.Cells for Java in your multithreaded environment without any problem.
However, if you have shared variables or workbook objects or you have your own shared data, then you will have to make sure that your data is thread-safe and only one thread could access it at a time.
This issue is not being caused by concurrency (Aspose.Cells does not have this limitation, however in trial version it does have limitation of number of opened files) but it seems this issue is caused by some particular file only. So this could be some bug of Aspose.Cells for Java.
Please try to replicate this issue with your problematic file in your standalone application and share with us. We will look into it and fix this issue.
We have also logged this issue in our database with the issue id: CELLSJAVA-40385.
Hi Shakeel,
We are again facing thsi issue in the production environment. Can you suggest any causes why the mentioned error would appear and would go away after we restart our application servers?
Please consider this of extreme urgency and criticality.
Hi,
Thanks for your posting and using Aspose.Cells.
We are not sure about the root cause of this issue. It seems to us that in your application the calendar system settings has been changed and some static constants defined by our component have been refreshed (disposed and then instantiated again).
We will try to change the way of using those static constants and provide you a fix to check whether it can solve your problem soon.
Hi Shakeel,
Thanks again for the quick response.
Can you please let us know by when you would be able to provide this updated jar. We have to inform our business users for this.
Let me know in case you need anything else.
Hi,
Thanks for your posting and using Aspose.Cells.
Please spare us some time around 1~3 working days. We will try to provide it in this time span.
Hi Shakeel,
Thanks. Is there any way in which we can expedite this. In the meantime we have no alternative but to rollback Aspose.Cells jar to a very old version.
We do not know the version of that jar and it was long since stable. However it did not support Office 2010 and as a result of that some of our business users will face an impact.
Hi,
Thanks for your posting and using Aspose.Cells for Java.
Yes, you can escalate it by purchasing Priority Support or Enterprise Support. Once, you will purchase it, we will prioritize and push your issues.
However, these enhanced supports do not grantee a fix. It is just that we escalate your issues on the top of queue.
I will suggest you to read about Enhanced Support for your further information.
Hi,
We have made improvements to avoid such kind of exception.
Please download and try this fix: Aspose.Cells for Java v7.3.4.1 and let us know your feedback.
The issues you have found earlier (filed as CELLSJAVA-40385) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.