Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Notarized Mac application does not start up correctly #14

Copy link
Copy link
@adamretter

Description

@adamretter
Issue body actions

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:

  1. 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?

  2. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.