This is kind of a continuation of this question: https://ask.openlca.org/918/fetches-from-collaboration-server-stopping
Software: Windows Server 2012, Tomcat 8.3. (xms2g, xmx4g), ElasticSearch 6.2.4 (xms8g, xmx10g), JDK 1.8.0_172
Hardware: Some virtual server, Intel Xeon, 16GB RAM
Starting from a fresh server start, we can fetch a repository (21,165 files in the repository folder, consisting of mostly reference data), the fetch can happen once. On the second, the fetch status will freeze and the openlca client hangs. On the server side, debug level tomcat stdout logs show that the elasticsearch queries were complete, but the localaccess log doesn't show the post from the openlca client (POST http://website:8080/lca-collaboration/ws/public/fetch/request/group/repository?download=false). This can happen such that one client on machine A can fetch, and a second client on machine B cannot fetch. It will happen if both fetches are done on the same machine (after restarting the client).
On another small repository (214 files in the repository folder), we can fetch once into an empty local database. We start a new, empty local database, and fetch again. On the third time, the fetch status will freeze and the openlca client hangs (all from the above). This is all done using the same machine after restarting the client (I haven't tested with multiple clients).
On another repository, which consists only of openlca reference data (i.e., we created a new database with complete reference data and commit that to a new repository). This database will not fetch at all into an empty local database after a restart.
The server will still respond to other requests - show data set info through the web server, will initiate other fetches, etc.
Stopping and starting both the elasticsearch and tomcat services in windows does not appear to be enough to allow the fetches to happen again - the server must be restarted.
