This is an old bug what on latest version is yet solved ( My mistake was allowed copy or move the contents into himselft and that caused infinite loop ).
You will not solve from UI, must be done by scripting accessing database at low level when deleting nodes. First of all stop openkm to be sure the looping process is definitively stopped.
Take this script as sample
http://wiki.openkm.com/index.php/Script ... _traversal and do some modifications:
Code: Select allimport org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import com.openkm.api.*;
import com.openkm.bean.*;
Logger log = LoggerFactory.getLogger("com.openkm.scripting");
int MAX_DEPTH = Integer.MAX_VALUE;
void nodeTask(String path, int depth) throws Exception {
for (Folder fld : OKMFolder.getInstance().getChildren(null, path)) {
log.info("Folder: {}", level);
if (depth < MAX_DEPTH) {
nodeTask(fld.getPath(), depth + 1);
}
}
OKMFolder.getInstance().purge(null, path);
}
log.info("***** Process BEGIN *****");
nodeTask("/okm:root", 0);
log.info("***** Process END *****");
IMPORTANT CHANGE THE nodeTask("/okm:root", 0); for the node you want to start deleting. The idea is go at the end and start backwards deleting. The proces can take several hours or days before be completed ( do not stop the openkm service while be running ). The purge methods removes definitively the node without going to trash.
When you get it solved migrate to latest 6.3 version
