java.lang.ArrayIndexOutOfBoundsException: 0 rike.java:75)

Issue Description

A customer applied an OS patch and immediately their reports began to fail when users tried to run them. The exception in the jasperserver.log was:

java.lang.ArrayIndexOutOfBoundsException: 0
at sun.font.CompositeStrike.getStrikeForSlot(CompositeStrike.java:75)
at sun.font.CompositeStrike.getFontMetrics....

The stacktrace indicated that the exception was thrown during report-fill

Resolution

A bug in the redhat patch is breaking the JVM's ability to fetch font. See the two links below:

• https://bugzilla.redhat.com/show_bug.cgi?id=1484079
• https://stackoverflow.com/questions/45569367/upgrade-rhel-from-7-3-to-7-4-arrayindexoutofboundsexception-in-sun-font-composi

The second link above describes a workaround involving an edit to local.conf, but we recommend you ask redhat their thoughts.

For background, TIBCO JasperReports^® Server needs a physical font file (.ttf) at runtime. You can associate specific .ttf with reports via our font-extensions feature, if you haven't done this, then JasperReports^® Server relies on the Java Virtual Machine (JVM) and the JVM relies on the OS. Essentially the JVM has logical and physical font mappings and the redhat update seems to have change something at the physical font level OR perhaps at a JVM level.

If you cannot change local.conf, a font-extension might help avoid the error if you specify a .ttf for the 'default' font in JasperReports^®​​​​​​​ Server. The default font comes from a property, which is this value out-of-box:

net.sf.jasperreports.default.font.name=SansSerif

So theoretically you could create a font-extension for SansSerif in which you define the ttf to be used for font family name "SansSerif"

For information on creating font extensions please see the Fonts chapter in the Studio user guide - https://community.jaspersoft.com/documentation/tibco-jaspersoft-studio-user-guide/v720/working-font-extensions-0

Ref. Case 01794343