evolvedbinary / fusiondb-server Goto Github PK

View Code? Open in Web Editor NEW

21.0 12.0 0.0 0 B

FusionDB Server

Home Page: https://www.fusiondb.com

nosql database multi-model xquery xml json key-value xslt

fusiondb-server's People

Stargazers

Watchers

fusiondb-server's Issues

Launcher systray does not reflect Service status correctly

FusionDB 1.0.0-ALPHA2
Windows Server 2012 R2 Standard

Install FusionDB as a service.
Either:
1. Stop FusionDB using the Windows Service manager
2. Terminate the Apache Commons Daemon procrun process
Click the Launcher (System Tray icon), see that it still says "Stop FusionDB"... yet FusionDB Server is not running!

Launcher must refresh the service status each time the popup menu is opened.

Poor REST performance vs. eXist

I have been benchmarking different types of requests to the RESTful API for both Fusion and eXist, using the latest USLM versions of titles 1 (a short one) and 42 (the longest one) of the US Code. Each of these tests had 100 repetitions, and both eXist and Fusion were identically configured on the same VM.

First, I tested a simple PUT of a document to /exist/rest/db/test:

usc01.xml eXist:
    Minimum: 0.43300747871398926 s
    Maximum: 1.388643503189087 s
    Mean:    0.6491883111000061 s
    Median:  0.6234605312347412 s
    Stddev:  0.15249426666857233 s
usc01.xml Fusion:
    Minimum: 0.5359818935394287 s
    Maximum: 2.7659928798675537 s
    Mean:    1.2113053154945375 s
    Median:  1.1449862718582153 s
    Stddev:  0.47974903573925054 s
usc42.xml eXist:
    Minimum: 35.580822229385376 s
    Maximum: 54.87896108627319 s
    Mean:    41.51840656995773 s
    Median:  41.32154309749603 s
    Stddev:  4.195144231762311 s
usc42.xml Fusion:
    Minimum: 188.74798727035522 s
    Maximum: 1077.4066643714905 s
    Mean:    404.10182027816774 s
    Median:  320.5594769716263 s
    Stddev:  191.0485587590224 s

Next, I tested GET:

usc01.xml eXist:
    Minimum: 0.03500247001647949 s
    Maximum: 0.2610175609588623 s
    Mean:    0.05440183639526367 s
    Median:  0.0410001277923584 s
    Stddev:  0.04378882484633538 s
usc01.xml Fusion:
    Minimum: 0.5689961910247803 s
    Maximum: 0.7550196647644043 s
    Mean:    0.6137096118927002 s
    Median:  0.6049911975860596 s
    Stddev:  0.030363894050856537 s
usc42.xml eXist:
    Minimum: 13.213871717453003 s
    Maximum: 15.583616971969604 s
    Mean:    13.67682737827301 s
    Median:  13.544020891189575 s
    Stddev:  0.40090442662817194 s
usc42.xml Fusion:
    Minimum: 264.0210030078888 s
    Maximum: 293.1509966850281 s
    Mean:    272.6948435425758 s
    Median:  269.29898858070374 s
    Stddev:  7.9907570945070505 s

Then, I POSTed some XQuery to get a specific section of a document:

1 U.S.C. 1 eXist:
    Minimum: 0.004994392395019531 s
    Maximum: 0.011027336120605469 s
    Mean:    0.006702215671539307 s
    Median:  0.0060079097747802734 s
    Stddev:  0.0012504552254434967 s
1 U.S.C. 1 Fusion:
    Minimum: 0.00799870491027832 s
    Maximum: 0.03599071502685547 s
    Mean:    0.010678362846374512 s
    Median:  0.009988903999328613 s
    Stddev:  0.0033822034856866566 s
42 U.S.C. 2000e eXist:
    Minimum: 0.012010574340820312 s
    Maximum: 0.04998445510864258 s
    Mean:    0.016210291385650635 s
    Median:  0.014001250267028809 s
    Stddev:  0.005966727038671187 s
42 U.S.C. 2000e Fusion:
    Minimum: 0.02099442481994629 s
    Maximum: 0.06598377227783203 s
    Mean:    0.026210627555847167 s
    Median:  0.02399766445159912 s
    Stddev:  0.006877559298661334 s

(the XQuery I used was an adapted version of a giant block we're using for a client that does a bunch of pre- and post-processing, but the most relevant piece is //*[@identifier=$identifier], and this is an indexed attribute)

Finally, I ran a DELETE (PUTting the document back between repetitions, but only timing the DELETE):

1 U.S.C. eXist:
    Minimum: 0.4656083583831787 s
    Maximum: 1.5618107318878174 s
    Mean:    0.6475286889076233 s
    Median:  0.5726385116577148 s
    Stddev:  0.2086682498874921 s
1 U.S.C. Fusion:
    Minimum: 2.4692959785461426 s
    Maximum: 4.827873945236206 s
    Mean:    3.485269944667816 s
    Median:  3.424243688583374 s
    Stddev:  0.5818232474143926 s
42 U.S.C. eXist:
    Minimum: 18.95114755630493 s
    Maximum: 26.387588024139404 s
    Mean:    21.3156515455246 s
    Median:  21.073147296905518 s
    Stddev:  1.509445739774873 s
42 U.S.C. Fusion:
    Minimum: 1957.4530036449432 s
    Maximum: 2816.1365151405334 s
    Mean:    2314.854492249489 s
    Median:  2259.181742668152 s
    Stddev:  224.80505757124126 s

It appears that Fusion's running time across the board grows faster than eXist with respect to document size. As several of Xcential's use cases involve handling large-ish documents, as a result we currently can't recommend Fusion over eXist to clients (which is a unfortunate, because in other POST XQuery tests, such as generating a small top-level outline for all USC titles, Fusion is faster).

Branding exist or fusion

There is a few instances, where fusion still refers to itself as exist. This is meant to collect them.

The name of the main log file is exist.log it is also the menu bar item on macOS Open exist.log

all login screens (e.g. monex) use exist-db branding

Dashboard reports exist-db 1.0.0-ALPHA which this is not

Journal files not removed on Windows

FusionDB Server 1.0.0-ALPHA2 (installed as a service)
Windows Server 2012 R2 Standard
As the Administrator

Generate a 10GB XMark dataset using:

xmlgen /f 68 /i /s 10000 /o output\output.xml

Make sure the files have .xml file extensions

find output/ -name \*.xml* -exec mv {} {}.xml \;

Load the XML files using the JAC in embedded mode.
Examine the C:\Users\Administrator\AppData\Roaming\FusionDB Server\data\rocks directory. You will see very many .log files, which take up much more space than the .sst files.

Restarting the FusionDB-Server service, leads to recovery running:

Determining the recovery process is in-progress can be seen by looking in C:\Users\Administrator\AppData\Roaming\FusionDB Server\logs\fusiondb-server-stdout.2019-09-09.log and seeing the end of the log looking like:

09 Sep 2019 12:09:49,800 [main] INFO  (JettyStart.java [run]:186) - [Operating System : Windows Server 2012 R2 6.3 amd64] 
09 Sep 2019 12:09:50,457 [main] INFO  (JettyStart.java [run]:200) - Configuring FusionDB eXist component from C:\Program Files\FusionDB Server\etc\conf.xml

You can observe the recovery process by looking in C:\Users\Administrator\AppData\Roaming\FusionDB Server\logs\rocksdb.log and seeing:

2019-09-09 12:16:14,963 [main] INFO  (RocksLoggerAdapter.java [log]:79) - [db_impl\db_impl_open.cc:676] Recovering log #176 mode 2 
2019-09-09 12:16:23,961 [main] INFO  (RocksLoggerAdapter.java [log]:79) - [db_impl\db_impl_open.cc:676] Recovering log #181 mode 2 
2019-09-09 12:16:33,197 [main] INFO  (RocksLoggerAdapter.java [log]:79) - [db_impl\db_impl_open.cc:676] Recovering log #182 mode 2 
2019-09-09 12:16:42,366 [main] INFO  (RocksLoggerAdapter.java [log]:79) - [db_impl\db_impl_open.cc:676] Recovering log #187 mode 2 
2019-09-09 12:16:51,631 [main] INFO  (RocksLoggerAdapter.java [log]:79) - [db_impl\db_impl_open.cc:676] Recovering log #188 mode 2 
2019-09-09 12:17:00,692 [main] INFO  (RocksLoggerAdapter.java [log]:79) - [db_impl\db_impl_open.cc:676] Recovering log #193 mode 2

The numbers #176, #181, etc. correspond to .log files in the C:\Users\Administrator\AppData\Roaming\FusionDB Server\data\rocks folder. They will be processed incrementally and a log line written for each. When each has completed, back in fusiondb-server-stdout.2019-09-09.log you should see the startup complete, once it says:

07 Sep 2019 12:21:01,265 [main] INFO  (JettyStart.java [run]:286) - FusionDB Server has started, listening on: 
07 Sep 2019 12:21:01,265 [main] INFO  (JettyStart.java [run]:288) - http://172.31.27.186:4059/ 
07 Sep 2019 12:21:01,265 [main] INFO  (JettyStart.java [run]:288) - https://172.31.27.186:5059/

At least in our test instance, we are not quite sure why there are so many outstanding Journal logs, each one should be cleared once the corresponding SST file has been fsync'd to disk.

StackOverflowError when retrieving a lock from WeakLazyStripes

As reported to me:

"I’ve been using the Docker instance for two weeks now, quite successfully. However, please note the transcript below – the WeakLazyStripes part. This happened a number of days ago, but has not affected my ability to work with the Docker instance. In other words, it’s still running just fine."

20 Sep 2019 17:38:50,405 [main] INFO  (JettyStart.java [run]:286) - FusionDB Server has started, listening on:
20 Sep 2019 17:38:50,406 [main] INFO  (JettyStart.java [run]:288) -     http://172.17.0.2:4059/
20 Sep 2019 17:38:50,407 [main] INFO  (JettyStart.java [run]:288) -     https://172.17.0.2:5059/
20 Sep 2019 17:38:50,407 [main] INFO  (JettyStart.java [run]:291) - Configured contexts:
20 Sep 2019 17:38:50,407 [main] INFO  (JettyStart.java [run]:297) -     /
20 Sep 2019 17:38:50,408 [main] INFO  (JettyStart.java [run]:312) - '/iprange'
20 Sep 2019 17:38:50,408 [main] INFO  (JettyStart.java [run]:297) -     /exist
20 Sep 2019 17:38:50,409 [main] INFO  (JettyStart.java [run]:312) - '/exist/iprange'
20 Sep 2019 17:38:50,409 [main] INFO  (JettyStart.java [run]:318) - -----------------------------------------------------
20 Sep 2019 17:39:20,410 [qtp502066023-80] WARN  (Descriptor.java [<init>]:116) - Giving up unable to read descriptor.xml file from classloader in package org.exist.http, eXist-db Core, version 1.0
20 Sep 2019 17:50:52,849 [qtp502066023-77] INFO  (TemporaryFileManager.java [<init>]:109) - Temporary folder is: /tmp/exist-db-temp-file-manager-5119084716874131087
21 Sep 2019 22:26:12,235 [qtp502066023-229] WARN  (TransactionManager.java [close]:528) - Transaction was not committed or aborted, auto aborting!
21 Sep 2019 22:26:12,266 [qtp502066023-229] ERROR (EXistServlet.java [doGet]:285) - null

java.lang.StackOverflowError: null
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:177) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:214) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:214) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:214) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:214) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:214) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:214) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:214) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:214) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:214) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:214) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:214) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:214) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:214) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:214) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]
        at org.exist.util.WeakLazyStripes.get(WeakLazyStripes.java:214) ~[fusiondb-server.uber.jar:1.0.0-ALPHA2]

Notarized Mac application does not start up correctly

When opening the FusionDB Server application via the Dock from /Applications, you are initially presented with the launcher config dialog. Upon clicking save the Dialog disappears and nothing seems to happen. Instead, at that point launcher.stage2.sh should have been executed to show the Menu Icon and start the server.

However, if you instead run /Applications/FusionDB\ Server.app/Contents/MacOS/fdb-JavaAppLauncher from the Terminal.app then FusionDB Server starts fine. This can be used as a temporary workaround.

Why it does not run from the Dock, but does run from the command line is somewhat of a mystery. At the moment we have two lines of investigation:

Perhaps the launcher.stage2.sh is somehow not permitted to be run from the Dock. It is a Bash script, that is executed from LauncherWrapper.java via a ProcessBuilder. Does directly trying to execute a .sh script when not already inside a Terminal.app perhaps not work?
The Launcher's config dialog when clicking save, writes a bunch of files inside of /Applications/FusionDB Server.app. Directly, after a fresh install of the App from the DMG to /Applications, we can see that the codesign utility reports this:

codesign --verify --deep --verbose=8 /Applications/FusionDB\ Server.app
/Applications/FusionDB Server.app: valid on disk
/Applications/FusionDB Server.app: satisfies its Designated Requirement

However, after first launching from the Dock and clicking Save in the launcher's config dialog, we see that the codesign utility reports this:

/Applications/FusionDB Server.app: a sealed resource is missing or invalid
file added: /Applications/FusionDB Server.app/Contents/Resources/etc/jetty/jetty-http.xml.orig.20200622112408
file added: /Applications/FusionDB Server.app/Contents/Resources/etc/jetty/jetty-ssl.xml.orig.20200622112408
file added: /Applications/FusionDB Server.app/Contents/Resources/etc/jetty/jetty-requestlog.xml.orig.20200622112408
file added: /Applications/FusionDB Server.app/Contents/Resources/etc/jetty/jetty-logging.xml.orig.20200622112408
file added: /Applications/FusionDB Server.app/Contents/Resources/etc/launcher.properties
file added: /Applications/FusionDB Server.app/Contents/Resources/etc/log4j2.xml.orig.20200622112408
file added: /Applications/FusionDB Server.app/Contents/Resources/etc/conf.xml.orig.20200622112408
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/urlrewrite.log
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/statistics.log
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/expath-repo.log
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/scheduler.log
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/profile.log
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/xmldb.log
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/rocks.log
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/xmlrpc.log
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/exist.log
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/betterform.log
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/backup.log
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/launcher.log
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/ensure-locking.log
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/restxq.log
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/ehcache.log
file added: /Applications/FusionDB Server.app/Contents/Resources/logs/locks.log
file modified: /Applications/FusionDB Server.app/Contents/Resources/etc/log4j2.xml
file modified: /Applications/FusionDB Server.app/Contents/Resources/etc/conf.xml
file modified: /Applications/FusionDB Server.app/Contents/Resources/etc/jetty/jetty-ssl.xml
file modified: /Applications/FusionDB Server.app/Contents/Resources/etc/jetty/jetty-http.xml
file modified: /Applications/FusionDB Server.app/Contents/Resources/etc/jetty/jetty-requestlog.xml
file modified: /Applications/FusionDB Server.app/Contents/Resources/etc/jetty/jetty-logging.xml

We also see that /Applications/FusionDB Server.app/Contents/Resources/logs/exist.log contains only this:

2020-06-22 11:24:08,704 [global.BrokerPools.ShutdownHook] INFO  (BrokerPools.java [lambda$0]:68) - Executing shutdown thread

Consider fixing the deb package dependencies when installing

Installed the latest Fusion DB snapshot (1.0.0~20200615135044) on Ubuntu 20.04, kernel 5.4, pretty vanilla Ubuntu install with nothing fancy. The install complained about these missing dependencies:

Unpacking fusiondb-server (1.0.0~20200615135044) ...
dpkg: dependency problems prevent configuration of fusiondb-server:
 fusiondb-server depends on dh-systemd; however:
  Package dh-systemd is not installed.
 fusiondb-server depends on libzstd-dev; however:
  Package libzstd-dev is not installed.

dpkg: error processing package fusiondb-server (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 fusiondb-server

It wasn't a big deal installing the missing packages manually but I know that deb packages can be made to handle that sort of thing automatically.

Thanks for the hard work.

Unable to enable ZStd for bottommostCompression

See - facebook/rocksdb#5795

Version the key/value layouts of each column family

At the moment we serialize/deserialize data into each column family according to one or more fixed layouts.

For future proofing, we should store the version of the layout. At startup we should check the versions. We could also provide functions for each layout to move from version n to version n+1, which would enable a seamless migration at startup.

Another option might be to investigate using a serialization/deserialization format which might allow backwards compatibility e.g. Protobuf, Cap'n Proto, etc.

Fusion DB losing Connection

Hello,
Our customer who has fusion Db on their server keeps losing connection. Restarting the DB doesn't help It will lose connection again. The first time this happened (last week) we had to rebuild the DB from a back up. This fixed the issue for about a week. Now the DB connection is an issue again. Can you help guide us to why we keep losing connection to the DB?

thanks in advance

Consider an improved WebDAV implementation

WebDAV test suite: http://www.webdav.org/neon/litmus/

Java options:

or... C/C++/Rust Options?

Easily Staple Notarization (requires XCode 13+)

With XCode 13+ there are newer commands that can be used for notarization:

https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution/customizing_the_notarization_workflow#3087734

One such new flag is --wait which could be used to wait until notarization completes, after which we could immediately run staple

Admin password blank by default, must be proactively set

The admin password has to be set manually in the user manager upon a fresh install, otherwise it is blank. This encourages bad security practice among DBAs and could increase the likelihood and severity of breaches if deployed at scale.

Possible solution: screen at setup similar to eXist's for setting the admin password.

httpclient

I'm getting an error with

import module namespace httpclient="http://exist-db.org/xquery/httpclient";

Is this missing from the Alpha build?

Issue with Notarization

Notarization status(s) is retrievable with:

xcrun altool --notarization-history 0 --username <apple Developer ID here> --password <notarization API key here>

Which gives something like:

Notarization History - page 0

Date                      RequestUUID                          Status  Status Code Status Message
------------------------- ------------------------------------ ------- ----------- ----------------
2021-12-17 16:20:27 +0000 8375797c-5324-404c-ba36-80e72189ad0f invalid 2           Package Invalid

Notarization info about a specific request, and a link to the log is retrievable with:

xcrun altool --notarization-info 8375797c-5324-404c-ba36-80e72189ad0f --username <apple Developer ID here> --password <notarization API key here>

{
  "logFormatVersion": 1,
  "jobId": "8375797c-5324-404c-ba36-80e72189ad0f",
  "status": "Invalid",
  "statusSummary": "Archive contains critical validation errors",
  "statusCode": 4000,
  "archiveFilename": "fusiondb-server-1.0.0-SNAPSHOT.dmg",
  "uploadDate": "2021-12-17T16:20:27Z",
  "sha256": "48cecde44497fe2459e01c12d576284332e5b517bdf87eefcaa05f81e4cc78c3",
  "ticketContents": null,
  "issues": [
    {
      "severity": "error",
      "code": null,
      "path": "fusiondb-server-1.0.0-SNAPSHOT.dmg/FusionDB Server.app/Contents/Java/jansi-2.4.0.jar/org/fusesource/jansi/internal/native/Mac/x86/libjansi.jnilib",
      "message": "The binary is not signed.",
      "docUrl": null,
      "architecture": "i386"
    },
    {
      "severity": "error",
      "code": null,
      "path": "fusiondb-server-1.0.0-SNAPSHOT.dmg/FusionDB Server.app/Contents/Java/jansi-2.4.0.jar/org/fusesource/jansi/internal/native/Mac/x86/libjansi.jnilib",
      "message": "The signature does not include a secure timestamp.",
      "docUrl": null,
      "architecture": "i386"
    },
    {
      "severity": "error",
      "code": null,
      "path": "fusiondb-server-1.0.0-SNAPSHOT.dmg/FusionDB Server.app/Contents/Java/jansi-2.4.0.jar/org/fusesource/jansi/internal/native/Mac/arm64/libjansi.jnilib",
      "message": "The binary is not signed with a valid Developer ID certificate.",
      "docUrl": null,
      "architecture": "arm64"
    },
    {
      "severity": "error",
      "code": null,
      "path": "fusiondb-server-1.0.0-SNAPSHOT.dmg/FusionDB Server.app/Contents/Java/jansi-2.4.0.jar/org/fusesource/jansi/internal/native/Mac/arm64/libjansi.jnilib",
      "message": "The signature does not include a secure timestamp.",
      "docUrl": null,
      "architecture": "arm64"
    },
    {
      "severity": "error",
      "code": null,
      "path": "fusiondb-server-1.0.0-SNAPSHOT.dmg/FusionDB Server.app/Contents/Java/jansi-2.4.0.jar/org/fusesource/jansi/internal/native/Mac/x86_64/libjansi.jnilib",
      "message": "The binary is not signed.",
      "docUrl": null,
      "architecture": "x86_64"
    },
    {
      "severity": "error",
      "code": null,
      "path": "fusiondb-server-1.0.0-SNAPSHOT.dmg/FusionDB Server.app/Contents/Java/jansi-2.4.0.jar/org/fusesource/jansi/internal/native/Mac/x86_64/libjansi.jnilib",
      "message": "The signature does not include a secure timestamp.",
      "docUrl": null,
      "architecture": "x86_64"
    }
  ]
}

Fusion Studio API unavailable

As reported by @pwin :

FusionDB Server 1.0.0-ALPHA2
Fusion Studio 0.1.0
Windows 10

Installed Fusion Studio from: fusion-studio-installer-0.1.0.exe.
Downloaded the FusionDB Server Zip file: fusiondb-server-1.0.0-ALPHA2-win.zip.
Uncompressed it to: C:\fusiondb.
From cmd.exe: cd C:\fusiondb\bin.
startup.bat.

All appears to start up correctly. We can access http://localhost:4059/exist from a web-browser.

However, Fusion Studio API appears to be unavailable :

Calling http://localhost:4059/exist/restxq/fusiondb/version results in a HTTP 404 response.
Trying to connect to FusionDB Server from Fusion Studio shows HTTP 404 responses when requesting API end-points: .

The restxq.log looks like:

2019-09-06 10:45:40,306 [main] INFO  (RestXqServiceRegistryManager.java [getRegistry]:49) - Initialising RESTXQ... 
2019-09-06 10:45:40,314 [main] INFO  (RestXqServiceRegistryManager.java [getRegistry]:67) - RESTXQ is ready. 
2019-09-06 10:45:43,460 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/packageservice/controller.xql' has a missing dependency on '/db/apps/packageservice/modules/login-helper.xql'. Will re-examine if the missing module is added. 
2019-09-06 10:45:44,379 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/packageservice/modules/local-apps-json.xql' has a missing dependency on '/db/apps/packageservice/modules/packages.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:45:44,509 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/packageservice/modules/local-apps.xql' has a missing dependency on '/db/apps/packageservice/modules/packages.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:45:44,590 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/packageservice/modules/local-packages-json.xql' has a missing dependency on '/db/apps/packageservice/modules/packages.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:45:44,643 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/packageservice/modules/local-packages.xql' has a missing dependency on '/db/apps/packageservice/modules/packages.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:45:44,748 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/apps/packageservice/modules/login-helper.xql' has been added to the database, re-examining '/db/apps/packageservice/controller.xql'... 
2019-09-06 10:45:44,778 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/packageservice/controller.xql' has a missing dependency on '/db/apps/packageservice/modules/packages.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:45:44,778 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/apps/packageservice/controller.xql 
2019-09-06 10:45:45,529 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/apps/packageservice/modules/packages.xqm' has been added to the database, re-examining '/db/apps/packageservice/modules/local-packages-json.xql'... 
2019-09-06 10:45:46,157 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/apps/packageservice/modules/local-packages-json.xql 
2019-09-06 10:45:46,159 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/apps/packageservice/modules/packages.xqm' has been added to the database, re-examining '/db/apps/packageservice/modules/local-packages.xql'... 
2019-09-06 10:45:46,646 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/apps/packageservice/modules/local-packages.xql 
2019-09-06 10:45:46,647 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/apps/packageservice/modules/packages.xqm' has been added to the database, re-examining '/db/apps/packageservice/controller.xql'... 
2019-09-06 10:45:47,001 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/apps/packageservice/controller.xql 
2019-09-06 10:45:47,002 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/apps/packageservice/modules/packages.xqm' has been added to the database, re-examining '/db/apps/packageservice/modules/local-apps-json.xql'... 
2019-09-06 10:45:47,224 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/apps/packageservice/modules/local-apps-json.xql 
2019-09-06 10:45:47,225 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/apps/packageservice/modules/packages.xqm' has been added to the database, re-examining '/db/apps/packageservice/modules/local-apps.xql'... 
2019-09-06 10:45:47,481 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/apps/packageservice/modules/local-apps.xql 
2019-09-06 10:45:59,492 [main] ERROR (ExistXqueryRegistry.java [findServices]:272) - XQuery '/db/apps/dashboard/bower_components/existdb-backup/modules/backup.xql' could not be compiled! Unable to compile XQuery: /db/apps/dashboard/bower_components/existdb-backup/modules/backup.xql: err:XQST0033 Cannot bind prefix 'backup' to 'http://exist-db.org/apps/dashboard/backup' it is already bound to 'http://fusiondb.com/ns/xquery/backup' 
2019-09-06 10:46:01,696 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/dashboard/bower_components/existdb-usermanager/controller.xql' has a missing dependency on '/db/apps/dashboard/bower_components/existdb-usermanager/modules/userManager.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:46:02,490 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/dashboard/bower_components/existdb-usermanager/modules/mytest.xql' has a missing dependency on '/db/apps/dashboard/bower_components/existdb-usermanager/modules/userManager2.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:46:02,979 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/apps/dashboard/bower_components/existdb-usermanager/modules/userManager.xqm' has been added to the database, re-examining '/db/apps/dashboard/bower_components/existdb-usermanager/controller.xql'... 
2019-09-06 10:46:03,434 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/apps/dashboard/bower_components/existdb-usermanager/controller.xql 
2019-09-06 10:46:23,427 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/dashboard/modules/dashboard.xqm' has a missing dependency on '/db/apps/dashboard/modules/packages/packages.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:46:23,813 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/dashboard/modules/local-applications.xql' has a missing dependency on '/db/apps/dashboard/modules/dashboard.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:46:23,814 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/dashboard/modules/dashboard.xqm' has a missing dependency on '/db/apps/dashboard/modules/packages/packages.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:47:40,352 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/doc/controller.xql' has a missing dependency on '/db/apps/doc/modules/config.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:48:08,669 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/apps/doc/modules/config.xqm' has been added to the database, re-examining '/db/apps/doc/controller.xql'... 
2019-09-06 10:48:08,897 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/apps/doc/controller.xql 
2019-09-06 10:48:09,003 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/doc/modules/diagnostics.xql' has a missing dependency on '/db/apps/doc/modules/rvd-support.xql'. Will re-examine if the missing module is added. 
2019-09-06 10:48:09,290 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/doc/modules/docbook.xql' has a missing dependency on '/db/apps/doc/modules/search.xql'. Will re-examine if the missing module is added. 
2019-09-06 10:48:09,431 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/doc/modules/review.xql' has a missing dependency on '/db/apps/doc/modules/rvd-support.xql'. Will re-examine if the missing module is added. 
2019-09-06 10:48:09,689 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/apps/doc/modules/rvd-support.xql' has been added to the database, re-examining '/db/apps/doc/modules/diagnostics.xql'... 
2019-09-06 10:48:10,032 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/apps/doc/modules/diagnostics.xql 
2019-09-06 10:48:10,032 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/apps/doc/modules/rvd-support.xql' has been added to the database, re-examining '/db/apps/doc/modules/review.xql'... 
2019-09-06 10:48:10,447 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/apps/doc/modules/review.xql 
2019-09-06 10:48:10,792 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/apps/doc/modules/search.xql' has been added to the database, re-examining '/db/apps/doc/modules/docbook.xql'... 
2019-09-06 10:48:11,026 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/apps/doc/modules/docbook.xql 
2019-09-06 10:48:11,242 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/doc/modules/test-runner.xql' has a missing dependency on '/db/apps/doc/modules/test-suite.xql'. Will re-examine if the missing module is added. 
2019-09-06 10:48:11,567 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/apps/doc/modules/test-suite.xql' has been added to the database, re-examining '/db/apps/doc/modules/test-runner.xql'... 
2019-09-06 10:48:12,009 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/apps/doc/modules/test-runner.xql 
2019-09-06 10:48:20,893 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/markdown/parse.xql' has a missing dependency on '/db/apps/markdown/content/markdown.xql'. Will re-examine if the missing module is added. 
2019-09-06 10:48:21,253 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/apps/markdown/content/markdown.xql' has been added to the database, re-examining '/db/apps/markdown/parse.xql'... 
2019-09-06 10:48:21,348 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/apps/markdown/parse.xql' has a missing dependency on '/db/apps/markdown/content/tei-config.xql'. Will re-examine if the missing module is added. 
2019-09-06 10:48:21,348 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/apps/markdown/parse.xql 
2019-09-06 10:48:21,461 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/apps/markdown/content/tei-config.xql' has been added to the database, re-examining '/db/apps/markdown/parse.xql'... 
2019-09-06 10:48:21,611 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/apps/markdown/parse.xql 
2019-09-06 10:48:25,476 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/system/repo/fusion-studio-api-0.1.0/api.xqm' has a missing dependency on '/db/system/repo/fusion-studio-api-0.1.0/modules/config.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:48:25,867 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/system/repo/fusion-studio-api-0.1.0/modules/collection.xqm' has a missing dependency on '/db/system/repo/fusion-studio-api-0.1.0/modules/error.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:48:25,940 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/system/repo/fusion-studio-api-0.1.0/modules/config.xqm' has been added to the database, re-examining '/db/system/repo/fusion-studio-api-0.1.0/api.xqm'... 
2019-09-06 10:48:26,007 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/system/repo/fusion-studio-api-0.1.0/api.xqm' has a missing dependency on '/db/system/repo/fusion-studio-api-0.1.0/modules/collection.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:48:26,007 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/system/repo/fusion-studio-api-0.1.0/modules/collection.xqm' has a missing dependency on '/db/system/repo/fusion-studio-api-0.1.0/modules/error.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:48:26,008 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/system/repo/fusion-studio-api-0.1.0/api.xqm 
2019-09-06 10:48:26,085 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/system/repo/fusion-studio-api-0.1.0/modules/document.xqm' has a missing dependency on '/db/system/repo/fusion-studio-api-0.1.0/modules/error.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:48:26,142 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/system/repo/fusion-studio-api-0.1.0/modules/error.xqm' has been added to the database, re-examining '/db/system/repo/fusion-studio-api-0.1.0/modules/collection.xqm'... 
2019-09-06 10:48:26,154 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/system/repo/fusion-studio-api-0.1.0/modules/collection.xqm' has a missing dependency on '/db/system/repo/fusion-studio-api-0.1.0/modules/util.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:48:26,154 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/system/repo/fusion-studio-api-0.1.0/modules/collection.xqm 
2019-09-06 10:48:26,155 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/system/repo/fusion-studio-api-0.1.0/modules/error.xqm' has been added to the database, re-examining '/db/system/repo/fusion-studio-api-0.1.0/modules/document.xqm'... 
2019-09-06 10:48:26,174 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/system/repo/fusion-studio-api-0.1.0/modules/document.xqm' has a missing dependency on '/db/system/repo/fusion-studio-api-0.1.0/modules/util.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:48:26,174 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/system/repo/fusion-studio-api-0.1.0/modules/document.xqm 
2019-09-06 10:48:26,232 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/system/repo/fusion-studio-api-0.1.0/modules/explorer.xqm' has a missing dependency on '/db/system/repo/fusion-studio-api-0.1.0/modules/util.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:48:26,419 [main] WARN  (ExistXqueryRegistry.java [recordMissingDependency]:429) - Module '/db/system/repo/fusion-studio-api-0.1.0/modules/index.xqm' has a missing dependency on '/db/system/repo/fusion-studio-api-0.1.0/modules/util.xqm'. Will re-examine if the missing module is added. 
2019-09-06 10:48:26,919 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/system/repo/fusion-studio-api-0.1.0/modules/util.xqm' has been added to the database, re-examining '/db/system/repo/fusion-studio-api-0.1.0/modules/collection.xqm'... 
2019-09-06 10:48:26,948 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/system/repo/fusion-studio-api-0.1.0/modules/collection.xqm' has been added to the database, re-examining '/db/system/repo/fusion-studio-api-0.1.0/api.xqm'... 
2019-09-06 10:48:27,270 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 19 resource functions for /db/system/repo/fusion-studio-api-0.1.0/api.xqm 
2019-09-06 10:48:27,271 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}delete-collection#1 
2019-09-06 10:48:27,655 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-5580959730979724623.tmp 
2019-09-06 10:48:27,668 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-5580959730979724623.tmp -> restxq.registry 
2019-09-06 10:48:27,669 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}delete-document#1 
2019-09-06 10:48:27,669 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-1417571018805290828.tmp 
2019-09-06 10:48:27,681 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-1417571018805290828.tmp -> restxq.registry 
2019-09-06 10:48:27,682 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}delete-group#1 
2019-09-06 10:48:27,683 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-8119712867634775334.tmp 
2019-09-06 10:48:27,694 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-8119712867634775334.tmp -> restxq.registry 
2019-09-06 10:48:27,694 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}delete-user#1 
2019-09-06 10:48:27,695 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-6912838566115102509.tmp 
2019-09-06 10:48:27,707 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-6912838566115102509.tmp -> restxq.registry 
2019-09-06 10:48:27,708 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}explorer#1 
2019-09-06 10:48:27,709 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-4992943218538666468.tmp 
2019-09-06 10:48:27,720 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-4992943218538666468.tmp -> restxq.registry 
2019-09-06 10:48:27,721 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}explorerOptions#0 
2019-09-06 10:48:27,721 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-5524352986320004239.tmp 
2019-09-06 10:48:27,732 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-5524352986320004239.tmp -> restxq.registry 
2019-09-06 10:48:27,733 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}get-document#1 
2019-09-06 10:48:27,734 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-1593750744940714229.tmp 
2019-09-06 10:48:27,749 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-1593750744940714229.tmp -> restxq.registry 
2019-09-06 10:48:27,749 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}get-group#1 
2019-09-06 10:48:27,751 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-4849279330120765411.tmp 
2019-09-06 10:48:27,767 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-4849279330120765411.tmp -> restxq.registry 
2019-09-06 10:48:27,768 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}get-index#1 
2019-09-06 10:48:27,769 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-1014445286730013907.tmp 
2019-09-06 10:48:27,784 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-1014445286730013907.tmp -> restxq.registry 
2019-09-06 10:48:27,785 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}get-user#1 
2019-09-06 10:48:27,786 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-7743964834028142663.tmp 
2019-09-06 10:48:27,801 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-7743964834028142663.tmp -> restxq.registry 
2019-09-06 10:48:27,802 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}list-groups#0 
2019-09-06 10:48:27,803 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-994744802767830050.tmp 
2019-09-06 10:48:27,818 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-994744802767830050.tmp -> restxq.registry 
2019-09-06 10:48:27,819 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}list-users#0 
2019-09-06 10:48:27,820 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-1933021388046620456.tmp 
2019-09-06 10:48:27,833 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-1933021388046620456.tmp -> restxq.registry 
2019-09-06 10:48:27,834 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}put-collection#3 
2019-09-06 10:48:27,835 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-9138498900973314875.tmp 
2019-09-06 10:48:27,849 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-9138498900973314875.tmp -> restxq.registry 
2019-09-06 10:48:27,850 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}put-document#5 
2019-09-06 10:48:27,852 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-2956692306886629595.tmp 
2019-09-06 10:48:27,865 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-2956692306886629595.tmp -> restxq.registry 
2019-09-06 10:48:27,866 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}put-group#2 
2019-09-06 10:48:27,867 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-8901203778131903235.tmp 
2019-09-06 10:48:27,880 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-8901203778131903235.tmp -> restxq.registry 
2019-09-06 10:48:27,881 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}put-user#2 
2019-09-06 10:48:27,882 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-4964870219308279721.tmp 
2019-09-06 10:48:27,893 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-4964870219308279721.tmp -> restxq.registry 
2019-09-06 10:48:27,894 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}query#2 
2019-09-06 10:48:27,895 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-5394857290960372051.tmp 
2019-09-06 10:48:27,909 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-5394857290960372051.tmp -> restxq.registry 
2019-09-06 10:48:27,909 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}restxq#0 
2019-09-06 10:48:27,910 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-1543488558680406436.tmp 
2019-09-06 10:48:27,922 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-1543488558680406436.tmp -> restxq.registry 
2019-09-06 10:48:27,923 [main] INFO  (RestXqServiceRegistryLogger.java [registered]:44) - Registered RESTXQ Resource Function: /db/system/repo/fusion-studio-api-0.1.0/api.xqm,{http://fusiondb.com/studio/api}version#0 
2019-09-06 10:48:27,923 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:152) - Preparing new RESTXQ registry on disk: C:\Users\Pedro\AppData\Local\Temp\exist-db-temp-file-manager-6726148585296002251\exist-db-temp-5930394597636400958.tmp 
2019-09-06 10:48:27,935 [main] INFO  (RestXqServiceRegistryPersistence.java [updateRegistryOnDisk]:190) - Replaced RESTXQ registry: exist-db-temp-5930394597636400958.tmp -> restxq.registry 
2019-09-06 10:48:27,936 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/system/repo/fusion-studio-api-0.1.0/modules/collection.xqm 
2019-09-06 10:48:27,937 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/system/repo/fusion-studio-api-0.1.0/modules/util.xqm' has been added to the database, re-examining '/db/system/repo/fusion-studio-api-0.1.0/modules/document.xqm'... 
2019-09-06 10:48:27,974 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/system/repo/fusion-studio-api-0.1.0/modules/document.xqm 
2019-09-06 10:48:27,974 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/system/repo/fusion-studio-api-0.1.0/modules/util.xqm' has been added to the database, re-examining '/db/system/repo/fusion-studio-api-0.1.0/modules/index.xqm'... 
2019-09-06 10:48:28,015 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/system/repo/fusion-studio-api-0.1.0/modules/index.xqm 
2019-09-06 10:48:28,015 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:322) - Missing dependency '/db/system/repo/fusion-studio-api-0.1.0/modules/util.xqm' has been added to the database, re-examining '/db/system/repo/fusion-studio-api-0.1.0/modules/explorer.xqm'... 
2019-09-06 10:48:28,038 [main] INFO  (ExistXqueryRegistry.java [reexamineModulesWithResolvedDependencies]:325) - Discovered 0 resource functions for /db/system/repo/fusion-studio-api-0.1.0/modules/explorer.xqm

Switch to Java 11 as minimum

Modularise
Bundle JRE with app on Win and Mac. See also https://dave.autonoma.ca/blog/2020/06/29/write-once-build-anywhere/

Add a winget Windows Package distribution

https://devblogs.microsoft.com/commandline/windows-package-manager-preview/

Cannot build FusionDB Server when eXist-db public repo is offline

Part of the build involves downloading eXist-db Apps from the eXist-db public repo for FusionDB's eXist-db compatibility component. Unfortunately when the eXist-db public repo is offline (which has been not infrequent recently), then the build fails.

We must remove this fragile dependency on the eXist-db public repo.

Service does not run on Windows 2019 - FDB Snapshot 20200510

Using a SNAPSHOT build of fdb from 20200510, installing the service works on Windows 2019 DataCentre. However the service fails to start.

launcher.log

2020-05-11 18:11:57,788 [AWT-EventQueue-0] DEBUG (WindowsServiceManager.java [run]:429) - WindowsServiceManager Executing: [cmd.exe, /c, ""C:\Program Files\FusionDB Server\bin\prunsrv-x86_64.exe" install FusionDB-Server --DisplayName=FusionDB-Server --Description="FusionDB Server" --StdError=auto --StdOutput=auto --LogPath="C:\Users\aretter\AppData\Roaming\FusionDB Server\logs" --LogPrefix=service --PidFile=service.pid --Startup=auto --ServiceUser=LocalSystem --Jvm="C:\Program Files\BellSoft\LibericaJRE-11-Full\bin\client\jvm.dll" --Classpath="C:/Program Files/FusionDB Server/lib/*" --JvmMs=128m --StartMode=jvm --StartClass=org.exist.service.ExistDbDaemon --StartMethod=start --StopMode=jvm --StopClass=org.exist.service.ExistDbDaemon --StopMethod=stop --JvmOptions="-Dfile.encoding=UTF-8;-Dlog4j.configurationFile=C:\Program Files\FusionDB Server/etc/log4j2.xml;-Djetty.home=C:\Program Files\FusionDB Server;-Dexist.jetty.config=C:\Program Files\FusionDB Server/etc/jetty/standard.enabled-jetty-configs;-Djetty.git.hash=ab228fde9e55e9164c738d7fa121f8ac5acd51c9;-Dexist.home=C:\Program Files\FusionDB Server;-Dexist.configurationFile=C:\Program Files\FusionDB Server/etc/conf.xml" --StartParams="C:\Program Files\FusionDB Server\etc\conf.xml" --JvmMx=4224m"] 
2020-05-11 18:11:57,913 [AWT-EventQueue-0] DEBUG (WindowsServiceManager.java [run]:429) - WindowsServiceManager Executing: [sc.exe, query, FusionDB-Server] 
2020-05-11 18:11:57,944 [AWT-EventQueue-0] DEBUG (WindowsServiceManager.java [run]:429) - WindowsServiceManager Executing: [cmd.exe, /c, ""C:\Program Files\FusionDB Server\bin\prunsrv-x86_64.exe" start FusionDB-Server"] 
2020-05-11 18:12:01,230 [AWT-EventQueue-0] ERROR (WindowsServiceManager.java [start]:232) - Could not start service, exitCode=5, output=''

fusiondb-server-stdout.2020-05-11.log

2020-05-11 18:11:58 Apache Commons Daemon procrun stdout initialized.
11 May 2020 18:11:59,931 [main] INFO  (JettyStart.java [run]:182) - Running with Java 11.0.7 [BellSoft (OpenJDK 64-Bit Client VM) in C:\Program Files\BellSoft\LibericaJRE-11-Full] 
11 May 2020 18:11:59,931 [main] INFO  (JettyStart.java [run]:189) - Approximate maximum amount of memory for JVM: 247 MB 
11 May 2020 18:11:59,931 [main] INFO  (JettyStart.java [run]:190) - Number of processors available to JVM: 2 
11 May 2020 18:11:59,931 [main] INFO  (JettyStart.java [run]:192) - Running as user 'EC2AMAZ-N4968ER$' 
11 May 2020 18:11:59,931 [main] INFO  (JettyStart.java [run]:193) - [FusionDB Home : C:\Program Files\FusionDB Server] 
11 May 2020 18:11:59,931 [main] INFO  (JettyStart.java [run]:194) - [FusionDB Version : 1.0.0-SNAPSHOT] 
11 May 2020 18:11:59,931 [main] INFO  (JettyStart.java [run]:195) - [FusionDB Build : 20200510233829] 
11 May 2020 18:11:59,931 [main] INFO  (JettyStart.java [run]:196) - [Git commit : 6227cf129eb8a6822d50425e3f88067f0c4c1702] 
11 May 2020 18:11:59,931 [main] INFO  (JettyStart.java [run]:198) - [Operating System : Windows Server 2019 10.0 amd64] 
11 May 2020 18:12:00,369 [main] INFO  (JettyStart.java [run]:212) - Configuring FusionDB eXist component from C:\Program Files\FusionDB Server\etc\conf.xml 
11 May 2020 18:12:00,776 [main] ERROR (JettyStart.java [run]:225) - configuration error: java.lang.UnsatisfiedLinkError: C:\Windows\Temp\librocksdbjni18005926251924699790.dll: Can't find dependent libraries 
org.exist.EXistException: java.lang.UnsatisfiedLinkError: C:\Windows\Temp\librocksdbjni18005926251924699790.dll: Can't find dependent libraries
	at org.exist.storage.BrokerPool.initialize(BrokerPool.java:504) ~[exist-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
	at org.exist.storage.BrokerPools.configure(BrokerPools.java:174) ~[exist-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
	at org.exist.storage.BrokerPools.configure(BrokerPools.java:109) ~[exist-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
	at org.exist.jetty.JettyStart.run(JettyStart.java:217) [exist-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
	at org.exist.jetty.JettyStart.main(JettyStart.java:104) [exist-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:?]
	at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:?]
	at java.lang.reflect.Method.invoke(Unknown Source) ~[?:?]
	at org.exist.start.Main.invokeMain(Main.java:118) [exist-start-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
	at org.exist.start.Main.runEx(Main.java:248) [exist-start-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
	at org.exist.service.ExistDbDaemon.start(ExistDbDaemon.java:36) [exist-service-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
	at org.exist.service.ExistDbDaemon.start(ExistDbDaemon.java:64) [exist-service-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
Caused by: java.lang.UnsatisfiedLinkError: C:\Windows\Temp\librocksdbjni18005926251924699790.dll: Can't find dependent libraries
	at java.lang.ClassLoader$NativeLibrary.load0(Native Method) ~[?:?]
	at java.lang.ClassLoader$NativeLibrary.load(Unknown Source) ~[?:?]
	at java.lang.ClassLoader$NativeLibrary.loadLibrary(Unknown Source) ~[?:?]
	at java.lang.ClassLoader.loadLibrary0(Unknown Source) ~[?:?]
	at java.lang.ClassLoader.loadLibrary(Unknown Source) ~[?:?]
	at java.lang.Runtime.load0(Unknown Source) ~[?:?]
	at java.lang.System.load(Unknown Source) ~[?:?]
	at org.rocksdb.NativeLibraryLoader.loadLibraryFromJar(NativeLibraryLoader.java:79) ~[rocksdbjni-202004011324-patched-debug.jar:?]
	at org.rocksdb.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.java:57) ~[rocksdbjni-202004011324-patched-debug.jar:?]
	at org.rocksdb.RocksDB.loadLibrary(RocksDB.java:67) ~[rocksdbjni-202004011324-patched-debug.jar:?]
	at org.rocksdb.RocksDB.<clinit>(RocksDB.java:38) ~[rocksdbjni-202004011324-patched-debug.jar:?]
	at org.exist.storage.rocks.RocksDatabase.open(RocksDatabase.java:102) ~[exist-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
	at org.exist.storage.rocks.RocksDatabase.open(RocksDatabase.java:92) ~[exist-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
	at org.exist.storage.BrokerPool.initialiseRocksDB(BrokerPool.java:800) ~[exist-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
	at org.exist.storage.BrokerPool._initialize(BrokerPool.java:529) ~[exist-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
	at org.exist.storage.BrokerPool.initialize(BrokerPool.java:490) ~[exist-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
	... 12 more

fusiondb-server-stderr.2020-05-11.log

2020-05-11 18:11:58 Apache Commons Daemon procrun stderr initialized.
org.exist.EXistException: java.lang.UnsatisfiedLinkError: C:\Windows\Temp\librocksdbjni18005926251924699790.dll: Can't find dependent libraries
	at org.exist.storage.BrokerPool.initialize(BrokerPool.java:504)
	at org.exist.storage.BrokerPools.configure(BrokerPools.java:174)
	at org.exist.storage.BrokerPools.configure(BrokerPools.java:109)
	at org.exist.jetty.JettyStart.run(JettyStart.java:217)
	at org.exist.jetty.JettyStart.main(JettyStart.java:104)
	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.exist.start.Main.invokeMain(Main.java:118)
	at org.exist.start.Main.runEx(Main.java:248)
	at org.exist.service.ExistDbDaemon.start(ExistDbDaemon.java:36)
	at org.exist.service.ExistDbDaemon.start(ExistDbDaemon.java:64)
Caused by: java.lang.UnsatisfiedLinkError: C:\Windows\Temp\librocksdbjni18005926251924699790.dll: Can't find dependent libraries
	at java.base/java.lang.ClassLoader$NativeLibrary.load0(Native Method)
	at java.base/java.lang.ClassLoader$NativeLibrary.load(Unknown Source)
	at java.base/java.lang.ClassLoader$NativeLibrary.loadLibrary(Unknown Source)
	at java.base/java.lang.ClassLoader.loadLibrary0(Unknown Source)
	at java.base/java.lang.ClassLoader.loadLibrary(Unknown Source)
	at java.base/java.lang.Runtime.load0(Unknown Source)
	at java.base/java.lang.System.load(Unknown Source)
	at org.rocksdb.NativeLibraryLoader.loadLibraryFromJar(NativeLibraryLoader.java:79)
	at org.rocksdb.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.java:57)
	at org.rocksdb.RocksDB.loadLibrary(RocksDB.java:67)
	at org.rocksdb.RocksDB.<clinit>(RocksDB.java:38)
	at org.exist.storage.rocks.RocksDatabase.open(RocksDatabase.java:102)
	at org.exist.storage.rocks.RocksDatabase.open(RocksDatabase.java:92)
	at org.exist.storage.BrokerPool.initialiseRocksDB(BrokerPool.java:800)
	at org.exist.storage.BrokerPool._initialize(BrokerPool.java:529)
	at org.exist.storage.BrokerPool.initialize(BrokerPool.java:490)
	... 12 more


Failed to start service.

service.log

[2020-05-11 20:48:48] [debug] ( prunsrv.c:1763) [ 4100] Apache Commons Daemon procrun log initialized.
[2020-05-11 20:48:48] [info]  ( prunsrv.c:1767) [ 4100] Apache Commons Daemon procrun (1.2.2.0 64-bit) started.
[2020-05-11 20:48:48] [info]  ( prunsrv.c:1677) [ 4100] Running Service 'FusionDB-Server'...
[2020-05-11 20:48:48] [debug] ( prunsrv.c:1448) [ 6104] Inside ServiceMain...
[2020-05-11 20:48:48] [debug] ( prunsrv.c:910 ) [ 6104] reportServiceStatusE: dwCurrentState = 2, dwWin32ExitCode = 0, dwWaitHint = 3000, dwServiceSpecificExitCode = 0.
[2020-05-11 20:48:48] [info]  ( prunsrv.c:1203) [ 6104] Starting service...
[2020-05-11 20:48:48] [debug] ( javajni.c:216 ) [ 6104] Explicit RuntimeLib specified 'C:\Program Files\BellSoft\LibericaJRE-11-Full\bin\client\jvm.dll'
[2020-05-11 20:48:48] [debug] ( javajni.c:285 ) [ 6104] loading jvm 'C:\Program Files\BellSoft\LibericaJRE-11-Full\bin\client\jvm.dll'
[2020-05-11 20:48:48] [debug] ( javajni.c:795 ) [ 6112] Jvm Option[0] -Dfile.encoding=UTF-8
[2020-05-11 20:48:48] [debug] ( javajni.c:795 ) [ 6112] Jvm Option[1] -Dlog4j.configurationFile=C:\Program Files\FusionDB Server/etc/log4j2.xml
[2020-05-11 20:48:48] [debug] ( javajni.c:795 ) [ 6112] Jvm Option[2] -Djetty.home=C:\Program Files\FusionDB Server
[2020-05-11 20:48:48] [debug] ( javajni.c:795 ) [ 6112] Jvm Option[3] -Dexist.jetty.config=C:\Program Files\FusionDB Server/etc/jetty/standard.enabled-jetty-configs
[2020-05-11 20:48:48] [debug] ( javajni.c:795 ) [ 6112] Jvm Option[4] -Djetty.git.hash=ab228fde9e55e9164c738d7fa121f8ac5acd51c9
[2020-05-11 20:48:48] [debug] ( javajni.c:795 ) [ 6112] Jvm Option[5] -Dexist.home=C:\Program Files\FusionDB Server
[2020-05-11 20:48:48] [debug] ( javajni.c:795 ) [ 6112] Jvm Option[6] -Dexist.configurationFile=C:\Program Files\FusionDB Server/etc/conf.xml
[2020-05-11 20:48:48] [debug] ( javajni.c:795 ) [ 6112] Jvm Option[7] -Djava.class.path=C:/Program Files/FusionDB Server/lib/ant-1.10.7.jar;C:/Program Files/FusionDB Server/lib/ant-launcher-1.10.7.jar;C:/Program Files/FusionDB Server/lib/antlr-2.7.7.jar;C:/Program Files/FusionDB Server/lib/antlr-3.0.jar;C:/Program Files/FusionDB Server/lib/aopalliance-1.0.jar;C:/Program Files/FusionDB Server/lib/apache-mime4j-core-0.8.3.jar;C:/Program Files/FusionDB Server/lib/apache-mime4j-dom-0.8.3.jar;C:/Program Files/FusionDB Server/lib/appassembler-booter-2.1.0.jar;C:/Program Files/FusionDB Server/lib/appassembler-model-2.1.0.jar;C:/Program Files/FusionDB Server/lib/asm-7.1.jar;C:/Program Files/FusionDB Server/lib/asm-analysis-7.2.jar;C:/Program Files/FusionDB Server/lib/asm-commons-7.2.jar;C:/Program Files/FusionDB Server/lib/asm-tree-7.2.jar;C:/Program Files/FusionDB Server/lib/aspectjrt-1.9.4.jar;C:/Program Files/FusionDB Server/lib/avalon-framework-api-4.3.1.jar;C:/Program Files/FusionDB Server/lib/avalon-framework-impl-4.3.1.jar;C:/Program Files/FusionDB Server/lib/backu
[2020-05-11 20:48:48] [debug] ( javajni.c:795 ) [ 6112] Jvm Option[8] exit
[2020-05-11 20:48:48] [debug] ( javajni.c:795 ) [ 6112] Jvm Option[9] abort
[2020-05-11 20:48:51] [debug] ( javajni.c:981 ) [ 6112] argv[0] = C:\Program Files\FusionDB Server\etc\conf.xml
[2020-05-11 20:48:51] [debug] ( javajni.c:1034) [ 6112] Java Worker thread started org/exist/service/ExistDbDaemon:start
[2020-05-11 20:48:52] [debug] ( prunsrv.c:1261) [ 6104] Java started 'org/exist/service/ExistDbDaemon'.
[2020-05-11 20:48:52] [info]  ( prunsrv.c:1359) [ 6104] Service started in 4384 milliseconds.
[2020-05-11 20:48:52] [debug] ( prunsrv.c:910 ) [ 6104] reportServiceStatusE: dwCurrentState = 4, dwWin32ExitCode = 0, dwWaitHint = 0, dwServiceSpecificExitCode = 0.
[2020-05-11 20:48:52] [debug] ( prunsrv.c:1603) [ 6104] Waiting for worker to finish...
[2020-05-11 20:49:00] [debug] ( javajni.c:1057) [ 6112] Java Worker thread finished org/exist/service/ExistDbDaemon:start with status = 0
[2020-05-11 20:49:00] [debug] ( prunsrv.c:1608) [ 6104] Worker finished.
[2020-05-11 20:49:00] [debug] ( prunsrv.c:1635) [ 6104] Waiting for all threads to exit.
[2020-05-11 20:49:00] [debug] ( prunsrv.c:910 ) [ 6104] reportServiceStatusE: dwCurrentState = 3, dwWin32ExitCode = 0, dwWaitHint = 0, dwServiceSpecificExitCode = 0.
[2020-05-11 20:49:00] [debug] ( prunsrv.c:1639) [ 6104] JVM destroyed.
[2020-05-11 20:49:00] [debug] ( prunsrv.c:910 ) [ 6104] reportServiceStatusE: dwCurrentState = 1, dwWin32ExitCode = 0, dwWaitHint = 0, dwServiceSpecificExitCode = 0.
[2020-05-11 20:49:00] [info]  ( prunsrv.c:1679) [ 4100] Run service finished.
[2020-05-11 20:49:00] [info]  ( prunsrv.c:1848) [ 4100] Apache Commons Daemon procrun finished.

Windows Service Manager

sc.exe qc FusionDB-Server

Windows Event Viewer

Querying a document collection does not seem to return non-XML files

I'm running the Alpha 3 Docker instance.

I'm finding that I can't see the PDF files I have installed alongside my XML documents.

This had worked fine with eXist-db and I've changed nothing other that switch to the FusionDB instance.

My simplified xquery is:

xquery version "3.1";
declare namespace d="DAV:";
for $doc in collection('/repository/grantcv1')
return (
let $fileURI := base-uri($doc)
return <d:response xmlns:d="DAV:">
<d:href>{$fileURI}</d:href>
</d:response>
)

I get all the XML files, but nothing else. I used to get the complete list of files in the folder.