We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Crash on IBM i series when trying to use Aspose PDF

Hi there,
Please see below the crash that I receive when trying to run a report using Aspose PDF 16.12.0.

Exception in thread “main” java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.ensureError(J9VMInternals.java:141)
at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:130)
at com.aspose.pdf.Document.m2(Unknown Source)
at com.aspose.pdf.Document.getLocalFontPaths(Unknown Source)
at com.aspose.pdf.internal.p68.z17.m12(Unknown Source)
at com.aspose.pdf.internal.p68.z17.m9(Unknown Source)
at com.aspose.pdf.internal.p68.z17.m8(Unknown Source)
at com.aspose.pdf.internal.p68.z17.m1(Unknown Source)
at com.aspose.pdf.FontRepository.findFont(Unknown Source)
at com.aspose.pdf.z207.m1(Unknown Source)
at com.aspose.pdf.z207.m1(Unknown Source)
at com.aspose.pdf.TextFragment.m3(Unknown Source)
at com.aspose.pdf.TextFragment.(Unknown Source)
at com.aspose.pdf.Cells.add(Unknown Source)
at blu.pa.reports.WGUME02J.buildPDF(WGUME02J.java:218)
at blu.pa.reports.WGUME02J.main(WGUME02J.java:62)

Caused by: java.lang.UnsupportedOperationException: Unsupported Platform, pid: 9
at com.aspose.pdf.internal.p277.z18.m1(Unknown Source)
at com.aspose.pdf.internal.p319.z8.m2(Unknown Source)
at com.aspose.pdf.internal.p319.z8.m4(Unknown Source)
at com.aspose.pdf.internal.p319.z8.(Unknown Source)
at com.aspose.pdf.internal.p319.z8.(Unknown Source)
… 14 more
Java program completed with exit code 1

Please assist.

Thanks in Advance.

Regards,
Duane

Hi Duane,


Thanks for your inquriy. We have recently resolved Fonts issue of IBM i series in Aspose.Pdf for Java 17.1.0. We will appreciate it if you please test the new version, 17.1.0, in your environment and share the results.

Looking forward to your feedback.

Best Regards,

Hi there,

I have tried it on the new version and it works.

Thank you for your assistance.

Hi Duane,


Thanks for the acknowledgement.

We are glad to hear that your problem is resolved with latest release. Please continue using our API and in the event of any further query, please feel free to contact.