Exporting a Repository That Contains UTF-8
The following errors may happen when you have international characters in repository objects, for example, in user IDs.
Error During Export
Upgrading typically requires doing an export operation on your database. If you are using MySQL and getting this null pointer exception, it may be due to an incorrect character in the file js.jdbc.properties:
java.lang.NullPointerException
ResourceExporter.exportResource(ResourceExporter.java:258)
Check the URL in this file in <js-install>buildomatic/build_conf/default/; it should look like the following:
jdbc:mysql://localhost:3306/jasperserver?useUnicode=true&characterEncoding=UTF-8
Note the ampersand & character. It is incorrect if it appears as &. The & is only correct in an HTML or XML context. It is incorrect in a properties file.
Error During Export from Repository on Oracle
Oracle requires a specific JVM property to handle UTF-8 characters properly. When this error happens, the export is empty and an error occurs when attempting to compress the result:
ERROR ExporterImpl:129 - java.util.zip.ZipException: ZIP file must have at least one entry
If you have stored your repository database on an Oracle RDBMS, modify the last line of both <js-install>/buildomatic/js-export.* files as follows:
From: java -classpath ...
To: java -Doracle.jdbc.defaultNChar=true -classpath ...
Recommended Comments
There are no comments to display.