Differences

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

--- en:release:3.09_release_notes [2018/12/11 06:02] – [Important Changes and Bug Fixes] anupama
+++ en:release:3.09_release_notes [2018/12/13 05:44] – [Content Encoding Error when visiting the local solr servlet page] anupama
@@ Line 286: / Line 286: @@
 ==== Troubleshooting ====
+=== Content Encoding Error when visiting the local solr servlet page ===
+If you see a Content Encoding Error when opening your GS3's solr servlet page at ''http://127.0.0.1:8383/solr'' or ''http://localhost:8383/solr'' in your browser, then this may have to do with the version of Java you have installed on your machine. From GS3.09 onward, if your machine has its own Java installed, then assuming that its version is sufficient and its bit-architecture (32 or 64 bit) matches, Greenstone will use your Java in preference to the bundled Java Runtime (JRE) that Greenstone ships with. We found that a recent version of Java (version 1.8.0_161 was problematic for us), caused the Content Encoding Error when visiting the solr servlet, whereas the bundled JRE and slightly earlier and much newer versions of Java such as 1.8.0_144 and 1.8.0_191 did not have these issues.
+**Solution:** if you have a problematic version of Java installed,
+- either unset JAVA_HOME and remove this Java's ''bin'' folder from the PATH environment variable too, thus helping Greenstone 3 use its bundled JRE instead
+- install a newer version of Java on your system. We found that the current latest one, 1.8.0_191 worked successfully for this purpose.
+=== SIGPIPE errors when building a collection ===
+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''
+  * 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.
 === Your browser doesn't remember you being logged into greenstone ===
 **The issue:**