Changeset 29947 for main/trunk/greenstone3/src/java/org/greenstone/gsdl3/service

Timestamp:

2015-06-05T20:58:20+12:00 (9 years ago)

Author:

ak19

Message:

First of two commits to fix rebuilding a collection using the online editor on Windows. Resolves the file lock problem. The java code works with changes in activate.pl. activate.pl is passed a flag so that it no longer de-activates and re-activates the collection itself, but just concerns itself with moving building to index. The GS2Construct java code now de-activates the collection prior to calling activate.pl and then re-activates it afterward. In the way it was done before, activate.pl used to handle de- and re-activating the collection. But when it was launched from the server java code, the java VM would exit having left a copy of the file handles to the perl process when forking the process for activate.pl. The perl code could not move building to index since the file handles had locks (6 of them) on the index/text/collection.gdb. Changes have been made to GS2PerlConstructor too, so that it more cleanly closes all the pipes of a process, that the process itself may thereby exit cleanly. Not yet able to move this properly into its own classes since the StreamGobbler classes in GLI are not quite suited but were customised for FormatConverter.

File:

• main/trunk/greenstone3/src/java/org/greenstone/gsdl3/service/GS2Construct.java (modified) (2 diffs)

main/trunk/greenstone3/src/java/org/greenstone/gsdl3/service/GS2Construct.java

@@ -330 +330 @@
         String lang = request.getAttribute(GSXML.LANG_ATT);
 
-        Element response = runCommand(request, GS2PerlConstructor.ACTIVATE);
+        UserContext userContext = new UserContext(request);
+        String request_type = request.getAttribute(GSXML.TYPE_ATT);
+        
+        // now we de-activate the collection before running activate.pl, and then re-activate at end 
+        // So activate.pl only does the moving, no activation. This way will prevent java from launching 
+        // perl, exiting and then leaving dangling file handles (on index/text/col.gdb) in perl.
+        if (!request_type.equals(GSXML.REQUEST_TYPE_STATUS)) {          
+            systemRequest("delete", coll_name, null, userContext); // deactivate collection
+        }   
+
+        Element response = runCommand(request, GS2PerlConstructor.ACTIVATE); // if request is for STATUS, then this won't run activate.pl
+
         Element status = (Element) GSXML.getChildByTagName(response, GSXML.STATUS_ELEM);
-
-        String request_type = request.getAttribute(GSXML.TYPE_ATT);
-        if (request_type.equals(GSXML.REQUEST_TYPE_STATUS))
-        {
-            return response;
-        }
-
-        UserContext userContext = new UserContext(request);
-        systemRequest("delete", coll_name, null, userContext);
 
         // check for finished
@@ -384 +386 @@
         status.appendChild(t);
         // once have got here, we assume
-        // the first bit proceeded successfully, now reload the collection
+        // the first bit proceeded successfully, now reload the collection (sends a collection reactivation request)
         systemRequest("reload", coll_name, status, userContext); // this will append more messages to the status, and overwrite the error code att
         return response;