Hi Dannes,

My apologies, it is actually a different NPE:





29 Apr 2013 12:24:22,859 [Thread-4] INFO  (JettyStart.java [run]:224) - -----------------------------------------------------
29 Apr 2013 12:24:22,861 [Thread-4] INFO  (JettyStart.java [run]:225) - Server has started on ports 8080 8443. Configured contexts:
29 Apr 2013 12:24:22,863 [Thread-4] INFO  (JettyStart.java [run]:234) - '/exist'
29 Apr 2013 12:24:22,863 [Thread-4] INFO  (JettyStart.java [run]:272) - -----------------------------------------------------
    at org.exist.launcher.UtilityPanel.update(UtilityPanel.java:192)
    at org.exist.launcher.Launcher.checkInstalledApps(Launcher.java:367)
    at org.exist.launcher.Launcher.signalStarted(Launcher.java:343)
    at org.exist.launcher.SplashScreen.update(SplashScreen.java:92)
    at java.util.Observable.notifyObservers(Observable.java:159)
    at org.exist.jetty.JettyStart.run(JettyStart.java:298)
    at org.exist.launcher.Launcher$2$1.run(Launcher.java:121)



I presume this means it’s getting a little further along the start up process before failing…



From: Dannes Wessels [mailto:dizzzz@exist-db.org] On Behalf Of Dannes Wessels
Sent: 29 April 2013 11:55
To: Michael Cullen
Cc: wolfgang@exist-db.org; 'eXist open Mailinglist'
Subject: Re: [Exist-open] exist-DB on Ubuntu 12.04



On 29 Apr 2013, at 12:36 , Michael Cullen <michael.cullen@astech.ie> wrote:

Sorry for the delay in returning with feedback: I got sidetracked with some other projects…

I did a clean build of eXist using the source code including thw 18376 commit, but to my surprise the problem persisted: the Null Pointer error is still displayed. The problem seems to be specific to that particular machine – I tried the stable eXist download on my personal laptop running Ubuntu 12.04 64bit and eXist installed and started without difficulty.


Is the NullpointerException-trace identical to the one in your mail on 2013-04-23 or is it another one?



Could some other installed software be causing a conflict of some kind? No other software is using port 8080 on the problem machine, and I don’t think it has any “special” changes made to the desktop setttings…


Based on the previous trace it has nothing to do with an other application listening on port 8080......