We are encountering the following error in a customer environment while using aspose-email-23.4-jdk16.jar to load an .msg file.
We are unable to reproduce the issue in our internal environment using the same library version. Due to data confidentiality restrictions, we are not permitted to obtain or share the original MSG file from the customer environment.
Below is the complete stack trace:
java.lang.ExceptionInInitializerError: java.lang.ExceptionInInitializerError:
java.lang.NullPointerException: Cannot invoke "com.aspose.email.system.Array.deepClone()"
because the return value of "com.aspose.email.system.Array.boxing(Object)" is null
za.a:-1
zd$zb.a:-1
zd.a:-1
zc.a:-1
zc.o:-1
zl.d:-1
zb.a:-1
zb.<init>:-1
zb.<init>:-1
zaki.a:1836
zaki.b:910
zaki.a:297
MailMessage.a:1592
MailMessage.c:1455
MailMessage.a:1362
MailMessage.load:1339
The exception occurs during MailMessage.load(...).
Environment details:
Library version: aspose-email-23.4-jdk16.jar
Java version: OpenJDK 21
Since the exception originates from ExceptionInInitializerError followed by an internal NullPointerException, it appears to occur during static initialization within the Aspose internal classes.
We would appreciate your guidance on:
Whether this is a known issue in version 23.4.
If this could be triggered by a specific MSG structure or corrupted file format.
Please let us know what additional diagnostic details would help in the investigation.
Thank you for the provided information and the detailed stack trace.
Based on the supplied stack trace, the problem is most likely related to the processing of embedded images within the MSG file during message loading or conversion.
Starting from version 24.3, a significant number of changes and fixes were introduced to the image processing and rendering mechanisms.
Although this behavior is not a typical or widely known issue for version 23.4, it is quite possible that it is caused by a specific MSG file structure rather than environmental differences.
Could you please verify whether the problem occurs with the latest version of the library, Aspose.Email 26.1?
This would help determine whether the issue has already been resolved in the updated processing logic.
If the issue reproduces with the newer version, we will assist with further diagnostics and resolution.
@sergey.vivsiuk , at this time, we are unable to validate the version upgrade directly in the customer’s environment where the issue is occurring. Until we are able to reproduce the issue in our local setup, we cannot confirm whether it has been resolved in version 26.1. As per your root cause diagnosis, we will configure a test case using an MSG file containing embedded images and verify the results. We will share our findings once the validation is complete.