Collab-Server: commit function not working

Question

Dear team,

 

we just recently bought the collab server package.

Unfortunately I can not commit anything to the repository even though i should own all the editing and writing permissions to do so.

As it was not possible, also due to errors, to fully fetch the database without having one installed locally, I installed the exact same database (ecoinvent 3.10) on the device I’m working on in hope to create less traffic and make the process easier. This however also brought no solution: tried to commit a newly created process again. It showed the error message below. When logged into the collab-server website no pending commit or push is shown, which tells me it doesn’t even get uploaded properly.

 I am heavily confused as none of the provided function to fetch/commit datasets is working even though the server has been set up properly. I used the openLCA 2.1.

 What could be the problem here?

I'll post the error log as comment

Comments

* openLCA version: 2.1.0
* operating system: Windows 10
* os architecture: amd64
* os version: 10.0
* native libraries loaded: false
* with sparse matrix support: false

# Full error stack trace

```
java.lang.reflect.InvocationTargetException

    at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:395)

    at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:470)

    at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:230)

    at org.eclipse.ui.internal.progress.ProgressManager.lambda$26(ProgressManager.java:836)

    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:74)

    at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:869)

    at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:845)

    at org.openlca.app.App.exec(App.java:282)

    at org.openlca.app.collaboration.navigation.actions.ReferenceCheck.<init>(ReferenceCheck.java:39)

    at org.openlca.app.collaboration.navigation.actions.ReferenceCheck.forRemote(ReferenceCheck.java:45)

    at org.openlca.app.collaboration.navigation.actions.Datasets.select(Datasets.java:36)

    at org.openlca.app.collaboration.navigation.actions.CommitAction.doRun(CommitAction.java:55)

    at org.openlca.app.collaboration.navigation.actions.CommitAction.run(CommitAction.java:49)

    at org.eclipse.jface.action.Action.runWithEvent(Action.java:474)

    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:580)

    at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:414)

    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)

    at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256)

    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1066)

    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4054)

    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3642)

    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)

    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)

    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046)

    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)

    at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:643)

    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)

    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:550)

    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:171)

    at org.openlca.app.rcp.RcpApplication.start(RcpApplication.java:13)

    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)

    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:136)

    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)

    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:402)

    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)

    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

    at java.base/java.lang.reflect.Method.invoke(Unknown Source)

    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)

    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)

    at org.eclipse.equinox.launcher.Main.run(Main.java:1467)

Caused by: java.lang.OutOfMemoryError: Java heap space

-------------------------


i already extended the memory to 7000MB on the device im using, which should in theory be more than enough for an upload.

---

Which system model of Ecoinvent are you using? And the Unit- or Systemprocesses?

Answer 1

The stacktrace indicates an issue with the "Check referenced changes". We will investigate this.

For now you can disable this feature in "File/Preferences -> Collaboration"

Comments

If you are using the system process database the check needs 10G ram - it is because it loads the ids of all data sets into memory, and the exchange table of an ecoinvent system process database contains millions of entries, which leads to this heavy use of memory. In general we can recommend to use the unit process databases instead, which would run this check quickly and without much memory usage.