User Tools

Site Tools


en:release:3.09_release_notes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
en:release:3.09_release_notes [2019/07/10 03:43] anupamaen:release:3.09_release_notes [2019/09/05 07:21] – [Important Changes and Bug Fixes] anupama
Line 313: Line 313:
   * Patches to perl code upgrading perl syntax to work with newer versions of perl   * Patches to perl code upgrading perl syntax to work with newer versions of perl
   * GLI updates:   * GLI updates:
-    * The GLI Applet has been converted to a Java WebStart Application. Java Web Start not supported from Java 9 or onwards. To use the JRE bundled with your Greenstone, ensure no custom installed System Java is in the environment.+    * The GLI Applet has been converted to a Java WebStart Application. Java Web Start not supported from Java 9 or onwards. Therefore, to use the JRE v7 bundled with your Greenstone, ensure no custom installed System Java is in the environment.
     * GEMS can now launch in languages other than English     * GEMS can now launch in languages other than English
 ===== IMPORTANT information ===== ===== IMPORTANT information =====
Line 343: Line 343:
 We've added a work around to one kind of SIGPIPE errors which could occur with large collections when using ''solr'' as indexer. However, a couple of people on the mailing list encountered SIGPIPE errors on occasions when solr was not the indexer. **If your collection is using ''jdbm'' as the database type** and the error messages surrounding the SIGPIPE mention issues with "transaction commit", then Mariana Pichinini on the mailing list found that the following helped: We've added a work around to one kind of SIGPIPE errors which could occur with large collections when using ''solr'' as indexer. However, a couple of people on the mailing list encountered SIGPIPE errors on occasions when solr was not the indexer. **If your collection is using ''jdbm'' as the database type** and the error messages surrounding the SIGPIPE mention issues with "transaction commit", then Mariana Pichinini on the mailing list found that the following helped:
   * change the database type from ''jdbm'' to ''gdbm''   * change the database type from ''jdbm'' to ''gdbm''
-  * or leave the database type at ''jdbm'' and move your GS3's bundled JRE (the GS3's ''packages/jre'' subfolder) outside your GS3 installation. Next install a newer Java on your system so that GS3.08 can find that. If on Linux, ensure you open a new terminal before running GLI or command line building your collection.+  * or leave the database type at ''jdbm'' and move your GS3's bundled JRE (the GS3's ''packages/jre'' subfolder) outside your GS3 installation. Next install a newer Java on your system so that GS3.09 can find that. If on Linux, ensure you open a new terminal before running GLI or command line building your collection.
 === Your browser doesn't remember you being logged into greenstone === === Your browser doesn't remember you being logged into greenstone ===
 **The issue:** **The issue:**
en/release/3.09_release_notes.txt · Last modified: 2023/03/13 01:46 by 127.0.0.1