Upgrade Description of Chart Export

Version

Problem

Using the export, task schedule, and in-designer chart display functions of FineReport requires loading the libj2v8_linux_x86_64.so file in J2V8 if FR is deployed in a Linux environment and the JDK version is below 1.8. Pay attention to the GCC version. If the GCC version is too low, the following problems may occur.

1. The exported chart is blank, and the template reports an error saying "C library and JDK version do not meet the requirements, Please upgrade GBLIC to 2.17 And GLIBCXX to 3.4.19 or JDK to 1.8."

2. In the task schedule execution process, the exported chart is blank, and the template reports an error saying "C library and JDK version do not meet the requirements, Please upgrade GBLIC to 2.17 And GLIBCXX to 3.4.19 or JDK to 1.8."

In this case, how to realize the effect that you can use the chart export and task schedule functions normally if the JDK version is below 1.8 and the environment does not contain J2V8?

Note:

Even if your JDK version is above 1.8, you are advised to upgrade the GCC environment preferentially. After upgrade, the export performance will be enhanced.

Implementation Method

You can upgrade the GCC version in the Linux environment and use J2V8 as the JS running environment during chart drawing.

Determining Whether the Upgrade is Necessary

Prior to the upgrade, you need to confirm the GCC version of the current system. You can use the following commands to check whether GLIBC_2.17 and GLIBCXX_3.4.22 exist in the system.

Check whether GLIBC_2.17 exists in the system.

strings /lib64/libc.so.6 | grep GLIBC

Check whether GLIBCXX_3.4.22 exists in the system.

strings /usr/lib64/libstdc++.so.6 | grep GLIBCXX

If no corresponding GCC version exists in the system, you can consider whether to upgrade the GCC version.

Upgrade Procedure

Download the upgrade tool Upgrade Tool.zip, unzip the update tool, copy and paste the file obtained to any directory other than /usr, enter cd to enter the directory, and execute the following command.

chmod 755 glibcxx_3.4.22.sh
chmod 755 glibc_2.18.sh
./glibcxx_3.4.22.sh
./glibc_2.18.sh

In this case, chomd is used to add execution permission for the script, while ./ is used to execute the obtained script.

After the command is executed, the system will upgrade the GCC version automatically.

Note:

 After upgrade, you need to restart Tomcat.

1. GLIBC

As the C runtime library, GLIBC is the lowest-level API in the Linux system. (All commands, including Linux commands, rely on this library.) If the system contains other significant projects, proceed with caution before upgrade. (The corresponding upgrade file is glibc_2.18.sh.)

2. GLIBCXX

GLIBCXX is the C++ runtime library. Upgrades typically have minimal impact, and version rollback is supported if issues occur after the upgrade. (The corresponding upgrade file is glibcxx_3.4.22.sh.)