Facing NullPointerException while splitting 80GB PST file

Aspose.Email Product Family
1

I am facing below exception when splitting large file.
Exception in thread “main” java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader.java:61)
Caused by: java.lang.NullPointerException
at com.aspose.email.PersonalStorage.a(SourceFile:1376)
at com.aspose.email.PersonalStorage.b(SourceFile:1497)
at com.aspose.email.PersonalStorage.a(SourceFile:1425)
at com.aspose.email.PersonalStorage.splitInto(SourceFile:1213)
at com.gwava.pst.SplitPSTUtility.splitPSTIntoMultiplePSTFiles(SplitPSTUtility.java:86)
at com.gwava.pst.SplitPSTUtility.main(SplitPSTUtility.java:56)
… 5 more

This is the java code
image.png (37.1 KB)

2

@pharipriyap

Can you please try using latest Aspose.Email for Java 20.9.1 on your end. In case there is still an issue then please try increasing the Java Heap size on your end. If the issue still prevail then we need access to PST file along with sample code to work on that and try reproducing it.

3

Thank you for helping us. We did try using latest Aspose.Email for java 20.9. But no luck. We are still facing NullPointerException.
Exception in thread “main” java.lang.NullPointerException
at com.aspose.email.PersonalStorage.a(SourceFile:1503)
at com.aspose.email.PersonalStorage.b(SourceFile:1624)
at com.aspose.email.PersonalStorage.a(SourceFile:1552)
at com.aspose.email.PersonalStorage.b(SourceFile:1624)
at com.aspose.email.PersonalStorage.a(SourceFile:1552)
at com.aspose.email.PersonalStorage.splitInto(SourceFile:1340)
at com.gwava.pst.SplitPSTUtility.splitPSTIntoMultiplePSTFiles(SplitPSTUtility.java:86)
at com.gwava.pst.SplitPSTUtility.main(SplitPSTUtility.java:56)

4

We did try with multiple PST files. We faced the same exception. PSTs we used contains customer data. We are waiting for customer approval to share PSTs. Code is attached.image.png (55.1 KB)

5

@pharipriyap

We may need to access the PST that is throwing exception in order to reproduce and resolve the issue please.

6

Getting the permission from customer and sharing the PST is the long way solution. Is there any way to debug this or doing remote session with us to understand the problem better? Is it possible to provide any debugging version?

7

@pharipriyap

I am sorry, without provision of the information we may not be able to tell what is the issue without having access to the PST file. One thing you can do is follow the post below.

You can try working with PST by turning off exceptions and let the process complete. Finally, you can compare what has been processed and what’s missing from PST. Then you can only share those missing ones inside PST for analysis with us.

8

Hi,

We are observing null pointer exception at
java.lang.NullPointerException
at com.aspose.email.PersonalStorage.a(SourceFile:1322)
at com.aspose.email.PersonalStorage.b(SourceFile:1443)
at com.aspose.email.PersonalStorage.a(SourceFile:1371)
at com.aspose.email.PersonalStorage.b(SourceFile:1443)
at com.aspose.email.PersonalStorage.a(SourceFile:1371)
at com.aspose.email.PersonalStorage.b(SourceFile:1443)
at com.aspose.email.PersonalStorage.a(SourceFile:1371)
at com.aspose.email.PersonalStorage.splitInto(SourceFile:1159)
at com.gwava.publish.pst.PSTExport.splitPSTFileAndZIP(PSTExport.java:430)
at com.gwava.publish.pst.PSTExport.createPSTExport(PSTExport.java:251)
at com.gwava.publish.pst.PSTExport.run(PSTExport.java:129)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)

and we are suspecting that it could be related to the issue described in ProGuard Java Optimizer and Obfuscator / Bugs / #531 NPE in obfuscated code after switching to ProGuard 4.11 when optimizing field/propagation/value.

Could you please help us as we have customers who facing this problem.

9

@pharipriyap

Unfortunately, without provision of source file and used sample code, we may not be able to proceed further with investigation on our end and helping you out. Please share the requested information so that we may investigate and assist you further.