Exist: Wrapper startup broken on macOS

[joewiz]

As first discussed in https://github.com/eXist-db/exist/pull/1065#issuecomment-232386003, something about the changes in https://github.com/eXist-db/exist/pull/1016 (merged in on May 18) resulted in wrapper startup failures on macOS with builds of the develop branch since that day. As a result, methods of startup which used to work - double-clicking on the macOS .app version of eXist (from a .dmg installer), double-clicking on start.jar, or using the command open start.jar - no longer work.

To confirm this, I downloaded two nightlies from Adam's site to see whether this change resulted in the problem we're seeing. Indeed, the .app from the .dmg nightly of May 17 starts right up, whereas the May 19th version doesn't start.

I also see a difference between the process of the May 17th (158eaa3) and May 19th (50d037f) versions. Here's how each appears when I start them via start.jar (opening its application package and double-click directly on its start.jar):

May 17:

$ ps aux | grep java
joe 34956 0.2 2.8 7290824 467980 ?? S 5:06PM 0:18.43 /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -Dwrapper.java.library.path=/Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/.tools/wrapper/ -Xms256m -Dfile.encoding=UTF-8 -Xmx1024m -Xdock:name=eXist-db -Xdock:icon=icon.png -Dapple.laf.useScreenMenuBar=true -Dapple.awt.UIElement=true -Dexist.home=/Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/. -Djava.endorsed.dirs=/Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/./lib/endorsed -jar /Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/./start.jar org.exist.launcher.Launcher

May 19:

$ ps aux | grep java
joe 34935 0.0 0.1 8284660 17660 ?? Ss 5:03PM 0:00.02 /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -jar /Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/start.jar

When I swap the May 17th version out and put the May 19th version in its place, the startup command from the May 17th process output successfully starts the May 19th version:

$ /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -Dwrapper.java.library.path=/Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/.tools/wrapper/ -Xms256m -Dfile.encoding=UTF-8 -Xmx1024m -Xdock:name=eXist-db -Xdock:icon=icon.png -Dapple.laf.useScreenMenuBar=true -Dapple.awt.UIElement=true -Dexist.home=/Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/. -Djava.endorsed.dirs=/Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/./lib/endorsed -jar /Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/./start.jar org.exist.launcher.Launcher

[dizzzz]

So start.jar uses the (new) service wrapper, an interesting and nice design. But actually the wrapper should be used in a different way. in the EXIST_HOME/tools/yajsw/bin/ directory there are a few files of interest:

• installDaemon.sh and uninstallDaemon.sh are used to register exist-dn to have it started/stopped during the boot/shutdown of the UNIX server. The script is UNIX-flavour agnostic (linux flavors, macos, etc)
• queryDaemon.sh to check if the server is running
• startDaemon.sh and stopDaemon.sh to start/stop the server, UNIX agnostic.
• runConsole.sh to have the server started using the wrapper, but without actual OS registration

note that there are .bat scripts to do the same for Windows machines.

[dizzzz]

So, the issue is: the scripts mentioned above do not seem to work for macOS. Jetty does not seem to be started, there is no trace of stdout info (can't find it). In the tools/yajsw/logs/wrapper.log the only visible lines are:

WARNING|wrapper|Service eXist-db|16-07-21 20:04:56|YAJSW: yajsw-beta-12.06
WARNING|wrapper|Service eXist-db|16-07-21 20:04:56|OS   : Mac OS X/10.11.6/x86_64
WARNING|wrapper|Service eXist-db|16-07-21 20:04:56|JVM  : Oracle Corporation/1.8.0_91//Library/Java/JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home/jre/64
INFO|wrapper|Service eXist-db|16-07-21 20:04:56|starting 
INFO|wrapper|Service eXist-db|16-07-21 20:04:57|started process 7637
INFO|wrapper|Service eXist-db|16-07-21 20:04:57|started process with pid 7637
INFO|7637/0|Service eXist-db|16-07-21 20:05:00|cannot report service startup: listener is null
INFO|7637/0|Service eXist-db|16-07-21 20:05:00|cannot report service startup: listener is null

[joewiz]

With https://github.com/eXist-db/exist/pull/1070, java -jar start.jar now works on macOS: the splash screen and task bar icon appear. Also, I now see two new entries in the task bar:

However, double-clicking on start.jar (and the equivalent, open start.jar) still don't work. I don't think this is a matter of defaults/configuration on my Mac, because 3.0RC1 does start the splash screen and task bar icon when I double-click on its start.jar. Here is how the process appears via ps aux | grep java:

joe 54832 0.7 5.3 6967528 448676 ?? S 4:38PM 0:20.34 /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -Xms256m -Dfile.encoding=UTF-8 -Xmx1024m -Xdock:name=eXist-db -Xdock:icon=icon.png -Dapple.laf.useScreenMenuBar=true -Dapple.awt.UIElement=true -Dexist.home=/Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db -Djava.endorsed.dirs=/Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/lib/endorsed -jar /Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/start.jar org.exist.launcher.Launcher

Here's how the process looks when starting the develop branch of eXist:

joe 54848 0.0 0.1 6059264 11596 ?? Ss 4:40PM 0:00.01 /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -jar /Users/joe/workspace/exist/start.jar

This indicates that something about the new version has changed, rather than a misconfiguration of my Mac.

I haven't tested whether eXist will start when built as eXist-db.app with the .dmg installer.

[adamretter]

Hmm are you sure to related? Even before #1070 I think 'java -jar
start.jar' worked just fine for me on Mac.

On Saturday, 23 July 2016, Joe Wicentowski [email protected] wrote:

With #1070 https://github.com/eXist-db/exist/pull/1070, java -jar
start.jar now works on macOS: the splash screen and task bar icon appear.
Also, I now see two new entries in the task bar:

[image: screen_shot_2016-07-23_at_4_07_41_pm]
https://cloud.githubusercontent.com/assets/59118/17080142/c4950d18-50f2-11e6-8549-060446fa4961.png

However, double-clicking on start.jar (and the equivalent, open start.jar)
still don't work. I don't think this is a matter of defaults/configuration
on my Mac, because 3.0RC1 does start the splash screen and task bar icon
when I double-click on its start.jar. Here is how the process appears:

$ ps aux | grep java
joe 54832 0.7 5.3 6967528 448676 ?? S 4:38PM 0:20.34 /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -Xms256m -Dfile.encoding=UTF-8 -Xmx1024m -Xdock:name=eXist-db -Xdock:icon=icon.png -Dapple.laf.useScreenMenuBar=true -Dapple.awt.UIElement=true -Dexist.home=/Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db -Djava.endorsed.dirs=/Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/lib/endorsed -jar /Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/start.jar org.exist.launcher.Launcher

Here's how the process looks when starting the develop branch of eXist:

$ ps aux | grep java
joe 54848 0.0 0.1 6059264 11596 ?? Ss 4:40PM 0:00.01 /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -jar /Users/joe/workspace/exist/start.jar

This indicates that something about the new version has changed, rather
than a misconfiguration of my Mac.

I haven't tested whether eXist will start when built as eXist-db.app with
the .dmg installer.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/eXist-db/exist/issues/1069#issuecomment-234739132,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNJuUUM_JBJAXb-mXGV5tZ5EP9wC76vks5qYnzAgaJpZM4JSDZK
.

Adam Retter

skype: adam.retter
tweet: adamretter
http://www.adamretter.org.uk

[joewiz]

My recollection is that the server started but that there was no splash screen or menu bar entry. I will rewind and double check.

[joewiz]

Thanks for the pointer, I had misremembered. Please disregard my comments from today. #1070 had no effect on the ability to start eXist via 2 of the 3 methods reported in the initial issue above. The issues, as originally reported, remain:

• Double-clicking on start.jar fails to start the server
• Likewise, the command open start.jar fails to start the server

I'm unsure whether #1070 had any effect on the 3rd method (since I don't have the installer build steps configured):

• Starting eXist-db.app installed via .dmg

[joewiz]

I ran sh build.sh app and found a new eXist-db.app in $EXIST_HOME/dist. (I didn't do anything before this to prepare, i.e., install any installer dependencies. None is needed, right?)

Double-clicking on the app caused an eXist icon to appear and bounce in the dock a few times, then go away. No splash screen appeared, no menu bar icon. No warning about running an unsigned app. Just to be sure it wasn't an app signing issue, I right-clicked on the app and selected Open, and had the same result. The only indication I could find that the app had started was a new process:

joe 2099 0.0 0.2 6050056 14392 ?? Ss 9:40PM 0:00.02 /Users/joe/workspace/exist/dist/eXist-db.app/Contents/MacOS/JavaAppLauncher

I repeated this on builds immediately before and including #1070, with no change.

Just for everyone's info, this is Mac OS X 10.11.6, with Oracle Java JDK 1.8.0_102.

[joewiz]

Also, should this be of any help, here's what happens when I go into $EXIST_HOME/tools/yajsw/bin and run queryDaemon.sh:

$ sh queryDaemon.sh
++++++++++ YAJSW SET ENV ++++++++++
java version "1.8.0_102"
Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)
wrapper home : /Users/joe/workspace/exist/tools/yajsw
configuration: /Users/joe/workspace/exist/tools/yajsw/conf/wrapper.conf
java version "1.8.0_102"
Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)
---------- YAJSW SET ENV ----------
Password:
++++++++++ YAJSW SET ENV ++++++++++
java version "1.8.0_102"
Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)
wrapper home : /Users/joe/workspace/exist/tools/yajsw
configuration: /Users/joe/workspace/exist/tools/yajsw/conf/wrapper.conf
java version "1.8.0_102"
Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)
---------- YAJSW SET ENV ----------
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/groovy/groovy-patch.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/groovy/groovy-all-2.3.11.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/commons/commons-httpclient-3.0.1.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/commons/commons-codec-1.3.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/commons/commons-net-3.2.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/regex/automaton-1.11.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/glazedlists/glazedlists-1.8.0_java15.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/glazedlists/commons-beanutils-1.8.2.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/cron/joda-time-2.7.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/cron/yacron4j-00.03.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/jgoodies/forms-1.2.0.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/vfs-webdav/jackrabbit-webdav-1.5.6.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/vfs-webdav/xercesImpl.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/vfs-webdav/slf4j-jdk14-1.5.0.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/vfs-webdav/slf4j-api-1.5.0.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/vfs-dbx/vfs-dbx-00.02.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/vfs-dbx/dropbox-core-sdk-1.7.7.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/vfs-dbx/jackson-core-2.2.4.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/glazedlists/commons-beanutils-1.8.2.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/glazedlists/glazedlists-1.8.0_java15.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/keystore/keystore.jar
INFO: lib not found: /Users/joe/workspace/exist/tools/yajsw/lib/extended/abeille/formsrt.jar
YAJSW: yajsw-beta-12.06
OS   : Mac OS X/10.11.6/x86_64
JVM  : Oracle Corporation/1.8.0_102//Library/Java/JavaVirtualMachines/jdk1.8.0_102.jdk/Contents/Home/jre/64
Jul 23, 2016 9:49:03 PM org.apache.commons.vfs2.VfsLog info
INFO: Using "/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/vfs_cache" as temporary files store.
Name        : eXist-db
Installed   : false
Running     : false
Interactive : false
Automatic   : false
Manual      : false
Disabled    : false
Paused      : false
Unknown      : false

I'm not sure if any of the INFO: lib not found: statements are an indication of problems or not, but I thought the output here might be helpful info about my system.

[adamretter]

@joewiz I am still certain that these issues you describe:

Double-clicking on start.jar fails to start the server
Likewise, the command open start.jar fails to start the server

Are specific to your Mac because of the file type associations configured on your machine.

Regards the .dmg and .app I suspect these are YAJSW and are still broken. I believe @wolfgangmm and @zwobit are looking into that at the moment...

Regards building your own .app, I believe that the process would be ./build.sh clean && ./build.sh && ./build.sh dist && ./build.sh app

[joewiz]

Are specific to your Mac because of the file type associations configured on your machine.

@adamretter Hmm, if so, then I'm confused as to why, with 3.0RC1 (dmg release), does double-clicking its start.jar does start the splash screen and task bar icon.

Regards building your own .app, I believe that the process would be ./build.sh clean && ./build.sh && ./build.sh dist && ./build.sh app

Ah, I hadn't performed the dist step. And, in fact, running this command, the build fails on the dist step:

BUILD FAILED
/Users/joe/workspace/exist/build/scripts/dist.xml:331: /Users/joe/workspace/exist/dist/eXist-db-3.0.RC2/yajsw/bin does not exist.

[joewiz]

Changing /Users/joe/workspace/exist/build/scripts/dist.xml:332 from <fileset dir="${dist.dir}/yajsw/bin"> to <fileset dir="${dist.dir}/tools/yajsw/bin"> allowed the dist target to build successfully.

[adamretter]

@joewiz Ah ha! Regards the dist build script can you send a PR please?

Regards the Mac specific stuff and double clicking a start.jar to launch, I think you should check two different start.jar versions, (not from a .dmg or .app), a previous version which you believe works, i.e. the official eXist-3.0.RC1 release and a recent build.

[joewiz]

@adamretter Certainly, the PR will be on its way shortly.

Shall I perform a check as follows: compare double-clicking start.jar on (1) official eXist-3.0.RC1 release versus (2) the most recent nightly build from your static site?

[adamretter]

@joewiz Sounds like a reasonable comparison to me :-)

[joewiz]

@adamretter Okay, I retrieved the most recent nightly available on your nightlies site:

eXist-db-3.0.RC2-develop-f99352e.dmg 06-Jul-2016 03:02 169869312

Via http://static.adamretter.org.uk/exist-nightly/eXist-db-3.0.RC2-develop-f99352e.dmg.

I opened the dmg, dragged the app to my desktop, performed a right-click > Show Package Contents, drilled into Contents > Resources > eXist-db, right-clicked on start.jar > Open with, confirmed that the default application to handle this file extension is Jar Launcher (default) (15.0.1), moved back to select Open, and indicated to the security dialog that I wanted to allow the app to open despite not being signed. Result:

• server is inaccessible at localhost:8080
• no splash screen, no menu bar icon
• the process appears as follows:

joe 4593 0.0 0.1 6056960 4628 ?? S 2:44PM 0:00.01 /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -jar /Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/start.jar

Downloading 3.0RC1 from eXist-db.org via https://bintray.com/existdb/releases/download_file?file_path=eXist-db-3.0.RC1.dmg, I performed the same steps, but upon selecting Open:

• eXist opened a window called eXist-db Configuration, prompting me to set min/max memory, cache values, and the data directory
• advancing past this dialog, the splash screen and menu bar icon appeared
• the server is accessible at localhost:8080
• the process appears as follows:

joe 4641 0.1 4.8 6949820 404372 ?? S 2:50PM 0:20.35 /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -Xms256m -Dfile.encoding=UTF-8 -Xmx1024m -Xdock:name=eXist-db -Xdock:icon=icon.png -Dapple.laf.useScreenMenuBar=true -Dapple.awt.UIElement=true -Dexist.home=/Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db -Djava.endorsed.dirs=/Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/lib/endorsed -jar /Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/start.jar org.exist.launcher.Launcher

[adamretter]

@joewiz I just realised that the nightlies has stopped building as I ran out of disk space. I have just added a step which will now discard any nightlies that are older than ~2 months (62 days).

Could you try with the latest nightly 3.0.RC2-develop-56ba9c4 instead of the one you used from July 6th?

[joewiz]

@adamretter Ah, I see. Thanks for that fix! I've downloaded 3.0.RC2-develop-56ba9c4 (Jul 24) and repeated my test. The results were identical to the results with 3.0.RC2-develop-f99352e.

[joewiz]

I found a class in the source whose description stuck out to me:

Mainly used when launching eXist by double clicking on start.jar

This class is found at: https://github.com/eXist-db/exist/blob/develop/src/org/exist/launcher/LauncherWrapper.java#L42-L50. This class is the source of one string, -Dapple.awt.UIElement=true that (1) is nowhere else in source and (2) appears in the process when started via java -jar start.jar (3) but does not appear in the process resulting from double-clicking on start.jar.

This leads me to think that something changed on May 18 that caused the logic involved in emitting -Dapple.awt.UIElement=true to work when eXist is started via java -jar start.jar but to fail when eXist is started by double-clicking start.jar.

[joewiz]

One other surface level difference between the "old" version (official 3.0-RC1) and the "new" version (3.0-RC2 nightly, Jul 24), which is perhaps worth noting if it's a clue. (Or perhaps this is more due to the Jetty 9 upgrade?)

In the old version, the console logging stopped after a few lines:

$ java -jar start.jar
/Library/Java/JavaVirtualMachines/jdk1.8.0_102.jdk/Contents/Home/jre/bin/java -Xms256m -Xmx1024m -Dfile.encoding=UTF-8 -Xdock:name="eXist-db" -Xdock:icon="icon.png" -Dapple.laf.useScreenMenuBar="true" -Dapple.awt.UIElement=true -Dexist.home="/Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db" -Djava.endorsed.dirs="/Users/joe/Desktop/eXist-db.app/Contents/Resources/eXist-db/lib/endorsed" -jar start.jar org.exist.launcher.Launcher
starting 
started process 5220
$ 

In the new version the logging out to the console continues, and even keeps getting inserted when shutting down eXist:

$ java -jar start.jar
/Library/Java/JavaVirtualMachines/jdk1.8.0_102.jdk/Contents/Home/jre/bin/java -Xmx1024m -Xms64m -Dfile.encoding=UTF-8 -Xdock:name="eXist-db" -Xdock:icon="icon.png" -Dapple.laf.useScreenMenuBar="true" -Dapple.awt.UIElement=true -Dexist.home="/Users/joe/workspace/exist" -Djava.endorsed.dirs="/Users/joe/workspace/exist/lib/endorsed" -jar start.jar org.exist.launcher.Launcher
starting 
started process 5152
choski-pro-13:exist joe$ 24 Jul 2016 15:46:43,519 [Thread-4] INFO  (JettyStart.java [run]:136) - Configuring eXist from Optional[/Users/joe/workspace/exist/conf.xml] 
24 Jul 2016 15:46:43,521 [Thread-4] INFO  (JettyStart.java [run]:138) - Running with Java 1.8.0_102 [Oracle Corporation (Java HotSpot(TM) 64-Bit Server VM) in /Library/Java/JavaVirtualMachines/jdk1.8.0_102.jdk/Contents/Home/jre] 
24 Jul 2016 15:46:43,521 [Thread-4] INFO  (JettyStart.java [run]:145) - Running as user 'joe' 
24 Jul 2016 15:46:43,522 [Thread-4] INFO  (JettyStart.java [run]:146) - [eXist Home : /Users/joe/workspace/exist] 
24 Jul 2016 15:46:43,523 [Thread-4] INFO  (JettyStart.java [run]:147) - [eXist Version : 3.0.RC2] 
24 Jul 2016 15:46:43,523 [Thread-4] INFO  (JettyStart.java [run]:148) - [eXist Build : 20160724] 
24 Jul 2016 15:46:43,523 [Thread-4] INFO  (JettyStart.java [run]:149) - [Git commit : fix-dist-target-path-to-yajsw-7ef938f] 
24 Jul 2016 15:46:43,523 [Thread-4] INFO  (JettyStart.java [run]:151) - [Operating System : Mac OS X 10.11.6 x86_64] 
24 Jul 2016 15:46:43,524 [Thread-4] INFO  (JettyStart.java [run]:152) - [log4j.configurationFile : file:///Users/joe/workspace/exist/log4j2.xml] 
24 Jul 2016 15:46:43,524 [Thread-4] INFO  (JettyStart.java [run]:153) - [jetty.home : /Users/joe/workspace/exist/tools/jetty] 
24 Jul 2016 15:46:43,525 [Thread-4] INFO  (JettyStart.java [run]:154) - [jetty.base : /Users/joe/workspace/exist/tools/jetty] 
24 Jul 2016 15:46:43,525 [Thread-4] INFO  (JettyStart.java [run]:155) - [jetty configuration : /Users/joe/workspace/exist/tools/jetty/etc/standard.enabled-jetty-configs] 
24 Jul 2016 15:46:45,443 [Thread-4] INFO  (JettyStart.java [run]:193) - [loading jetty configuration : /Users/joe/workspace/exist/tools/jetty/etc/jetty.xml] 
24 Jul 2016 15:46:45,588 [Thread-4] INFO  (JettyStart.java [run]:193) - [loading jetty configuration : /Users/joe/workspace/exist/tools/jetty/etc/jetty-gzip.xml] 
24 Jul 2016 15:46:45,624 [Thread-4] INFO  (JettyStart.java [run]:193) - [loading jetty configuration : /Users/joe/workspace/exist/tools/jetty/etc/jetty-http.xml] 
24 Jul 2016 15:46:45,668 [Thread-4] INFO  (JettyStart.java [run]:193) - [loading jetty configuration : /Users/joe/workspace/exist/tools/jetty/etc/jetty-jaas.xml] 
24 Jul 2016 15:46:45,673 [Thread-4] INFO  (JettyStart.java [run]:193) - [loading jetty configuration : /Users/joe/workspace/exist/tools/jetty/etc/jetty-jmx.xml] 
24 Jul 2016 15:46:45,743 [Thread-4] INFO  (JettyStart.java [run]:193) - [loading jetty configuration : /Users/joe/workspace/exist/tools/jetty/etc/jetty-requestlog.xml] 
24 Jul 2016 15:46:45,758 [Thread-4] INFO  (JettyStart.java [run]:193) - [loading jetty configuration : /Users/joe/workspace/exist/tools/jetty/etc/jetty-ssl.xml] 
24 Jul 2016 15:46:45,773 [Thread-4] INFO  (JettyStart.java [run]:193) - [loading jetty configuration : /Users/joe/workspace/exist/tools/jetty/etc/jetty-ssl-context.xml] 
24 Jul 2016 15:46:45,807 [Thread-4] INFO  (JettyStart.java [run]:193) - [loading jetty configuration : /Users/joe/workspace/exist/tools/jetty/etc/jetty-https.xml] 
24 Jul 2016 15:46:45,815 [Thread-4] INFO  (JettyStart.java [run]:193) - [loading jetty configuration : /Users/joe/workspace/exist/tools/jetty/etc/jetty-deploy.xml] 
24 Jul 2016 15:46:45,856 [Thread-4] INFO  (JettyStart.java [run]:193) - [loading jetty configuration : /Users/joe/workspace/exist/tools/jetty/etc/jetty-plus.xml] 
24 Jul 2016 15:46:45,889 [Thread-4] INFO  (JettyStart.java [run]:193) - [loading jetty configuration : /Users/joe/workspace/exist/tools/jetty/etc/jetty-annotations.xml] 
24 Jul 2016 15:46:45,894 [Thread-4] INFO  (JettyStart.java [startJetty]:457) - [Starting jetty component : org.eclipse.jetty.server.Server] 
24 Jul 2016 15:46:45,895 [Thread-4] INFO  (JettyStart.java [lifeCycleStarting]:605) - Jetty server starting... 
24 Jul 2016 15:46:47,945 [Thread-4] INFO  (JettyStart.java [lifeCycleStarted]:614) - Jetty server started. 
24 Jul 2016 15:46:48,133 [Thread-4] WARN  (JettyStart.java [run]:244) - Could not find OpenID extension. OpenID will be disabled! 
24 Jul 2016 15:46:48,134 [Thread-4] WARN  (JettyStart.java [run]:251) - Could not find OAuthServlet extension. OAuth will be disabled! 
24 Jul 2016 15:46:48,137 [Thread-4] INFO  (JettyStart.java [run]:260) - ----------------------------------------------------- 
24 Jul 2016 15:46:48,138 [Thread-4] INFO  (JettyStart.java [run]:261) - Server has started, listening on: 
24 Jul 2016 15:46:48,138 [Thread-4] INFO  (JettyStart.java [run]:263) -     http://10.0.0.27:8080/ 
24 Jul 2016 15:46:48,138 [Thread-4] INFO  (JettyStart.java [run]:263) -     https://10.0.0.27:8443/ 
24 Jul 2016 15:46:48,139 [Thread-4] INFO  (JettyStart.java [run]:266) - Configured contexts: 
24 Jul 2016 15:46:48,139 [Thread-4] INFO  (JettyStart.java [run]:272) -     / 
24 Jul 2016 15:46:48,140 [Thread-4] INFO  (JettyStart.java [run]:272) -     /exist 
24 Jul 2016 15:46:48,140 [Thread-4] INFO  (JettyStart.java [run]:310) - ----------------------------------------------------- 

$ ls
LICENSE         atom-services.xml   build.properties    conf.xml        exist.jar       log4j2.xml      schema          vm.properties
README          autodeploy      build.sh        conf.xml.tmpl       extensions      mime-types.xml      src         webapp
README.md       backup.properties   build.xml       descriptor.xml      icon.png        mime-types.xml.tmpl start.jar
VERSION.txt     bin         client.properties   descriptor.xml.tmpl installer       nbbuild.xml     test
VERSION.txt.tmpl    build           client.properties.tmpl  eXist-db.iml        jdee-project        nbproject       tmp
atom-example.xq     build.bat       collection.xconf.init   exist-optional.jar  lib         samples         tools
$ 24 Jul 2016 15:47:06,746 [AWT-EventQueue-0] INFO  (JettyStart.java [shutdown]:543) - Database shutdown: stopping server in 1sec ... 
24 Jul 2016 15:47:07,749 [jetty shutdown schedule] INFO  (JettyStart.java [lifeCycleStopping]:627) - Jetty server stopping... 
24 Jul 2016 15:47:07,767 [jetty shutdown schedule] INFO  (JettyStart.java [lifeCycleStopped]:634) - Jetty server stopped 
$ 

Weird, eh?

[adamretter]

If I take both 3.0.RC1 release and 3.0.RC2-develop-56ba9c4 and reach inside the .dmg and attempt to run start.jar directly I get the same error for both:

$ /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -jar /tmp/3.0.RC1/eXist-db.app/Contents/Java/start.jar 
ERROR: exist.home cound not be autodetected, bailing out.

$ /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java -jar /tmp/eXist-db.app/Contents/Java/start.jar 
ERROR: exist.home could not be autodetected, bailing out.

However if I double-click the 3.0.RC1 eXist-db.app file, then it runs correctly, the same is not true of the 3.0.RC2-develop-56ba9c4 version which fails to start. I think the problem is very much in the Mac JavaAppLauncher somewhere... I don't think we are any closer to solving this, unless @zwobit or @wolfgangmm have made any progress.

[joewiz]

Fair enough. I certainly don't have any more ideas ;)

[dizzzz]

@wolfgangmm figured out that open start.jar and the equivalent clicking on the jar file, does not work because of the missing exist.home ; to be continued

[adamretter]

@wolfgangmm @dizzzz I don't think that's the issue, as that existed on 3.0.RC1 which worked ok...

[wolfgangmm]

I found out the issue with the mac app is caused by whitespace in the path to the java executable. I have a fix but need to retest on windows tomorrow to make sure all is ok.

[joewiz]

Three cheers for @wolfgangmm!

[dizzzz]

Nice catch!