search

eXist-db / exist

eXist Native XML Database and Application Platform
https://exist-db.org
GNU Lesser General Public License v2.1
429 stars 179 forks source link

eXist 3.0 RC1 doesn't start #844

Closed StephanMa closed 7 years ago

StephanMa commented 8 years ago

Dear Community,

yesterday i tried to start a fresh build of eXist 3.0 RC1 (dev 8b8fb2e). Starting eXist with sudo java -jar start.jar doesn't work. The Splashscreen appears but the server is not started.

The eXist-Log throws just one Error "ERROR (Configuration.java [lookupModuleClass]:449) - Configuration problem: class not found for module 'http://exist-db.org/xquery/jndi' (ClassNotFoundException); class:'org.exist.xquery.modules.jndi.JNDIModule'; message:'org.exist.xquery.modules.jndi.JNDIModule' "

System: Ubuntu 14.04 Java 8 (1.8.0_66-b17)

Best wishes from Germany Stephan

dizzzz commented 8 years ago

What modules did you explicitly set in conf.xml ?

StephanMa commented 8 years ago

I haven't changed anything. Just cloned and installed it without any changes. JNDI is enabled in this version.

I temporary deleted this line in the conf.xml. The error disappears but the Server does not start either.

`

        <!--module uri="http://exist-db.org/xquery/context"            class="org.exist.xquery.modules.context.ContextModule" /-->

        <module uri="http://exist-db.org/xquery/counter"            class="org.exist.xquery.modules.counter.CounterModule" />

        <module uri="http://exist-db.org/xquery/datetime"           class="org.exist.xquery.modules.datetime.DateTimeModule" />

        <module uri="http://exist-db.org/xquery/httpclient"         class="org.exist.xquery.modules.httpclient.HTTPClientModule" />

        <module uri="http://exist-db.org/xquery/image"              class="org.exist.xquery.modules.image.ImageModule" />

        <!--<module uri="http://exist-db.org/xquery/jndi"               class="org.exist.xquery.modules.jndi.JNDIModule" /> -->

        <module uri="http://exist-db.org/xquery/mail"               class="org.exist.xquery.modules.mail.MailModule" />

        <module uri="http://exist-db.org/xquery/scheduler"          class="org.exist.xquery.modules.scheduler.SchedulerModule" />

        <module uri="http://exist-db.org/xquery/sql"                class="org.exist.xquery.modules.sql.SQLModule" />

        <!--module uri="http://exist-db.org/xquery/versioning/svn"     class="org.exist.versioning.svn.xquery.SVNModule" /-->

        <module uri="http://exist-db.org/xquery/xmldiff"            class="org.exist.xquery.modules.xmldiff.XmlDiffModule" />`
joewiz commented 8 years ago

After you cloned the repo did you run build.sh/.bat?

StephanMa commented 8 years ago

Yes, i run build.sh.

The building process afterwards was without any errors. And as i mentioned.... when i run sudo java -jar start.jar everything seems to went well. Unfortunately it does not start completely and it stucks at the Splashscreen.

Its not that urgent. But i wanted to report it in case that its not just my fault....

ChiSamurai commented 8 years ago

Same error on jndi here (after 'build.sh rebuild' ), too. Though on my machine 'java -jar start.jar' works and starts DB without any significant problem...

joewiz commented 8 years ago

How odd... Another troubleshooting step: before rebuilding could you do build.sh clean-all please?

ChiSamurai commented 8 years ago

hmmm.. this drops my database, doesnt it? I could try it on a plain one it you like...

ChiSamurai commented 8 years ago

Build of clean checkout (develop branch) leads to that JNDI error:

2015-12-04 10:48:04,932 [AWT-EventQueue-0] ERROR (Configuration.java [lookupModuleClass]:449) - Configuration problem: class not found for module 'http://exist-db.org/xquery/jndi' (ClassNotFoundException); class:'org.exist.xquery.modules.jndi.JNDIModule'; message:'org.exist.xquery.modules.jndi.JNDIModule' 
2015-12-04 10:48:05,230 [Thread-4] ERROR (Configuration.java [lookupModuleClass]:449) - Configuration problem: class not found for module 'http://exist-db.org/xquery/jndi' (ClassNotFoundException); class:'org.exist.xquery.modules.jndi.JNDIModule'; message:'org.exist.xquery.modules.jndi.JNDIModule'

@joewiz: I could send you the build log if you want. There are some errors like

[ivy:retrieve] :: problems summary ::
[ivy:retrieve] :::: ERRORS
[ivy:retrieve]  unknown resolver chain
[ivy:retrieve]  unknown resolver chain
[ivy:retrieve]  unknown resolver chain

I'm not familiar with the build process nor sure if related to that issue.

But: eXist starts with java -jar start.jar without problems.

joewiz commented 8 years ago

Just to confirm, I assume you haven't modified your $EXIST_HOME/extensions/build.properties or added your own local.build.properties in the same folder? If you have changed these files, please state where. But when you said "fresh checkout" I assumed you meant no modifications.

joewiz commented 8 years ago

(I guess this is progress, though - despite the build errors related to JNDI, you're able to start the db normally...)

StephanMa commented 8 years ago

Well for me, i haven't changed anything.

But, other then ChiSamurai, eXist doesn't seem to startup. Tested different times in a VM or on my Testnotebook.

ChiSamurai commented 8 years ago

no, i did very new checkout and build.properties are untouched. no modifications to any file at all.

pherk commented 8 years ago

I'm not shure if my problem is the same: I did clean build of today's develop branch (RC2) the JNDI error (class not found) persists, despite this the server starts ... but I cannot login via dashboard (admin, guest passswords should be blank after clean build) exist log shows: 2016-01-07 09:16:49,733 [eXistThread-26] WARN (ServletHandler.java [doHandle]:538) -
javax.servlet.ServletException: An error occurred while processing request to /exist/apps/dashboard/plugins/userManager/api/user/: exerr:ERROR You must be an authenticated user [at line 44, column 17, source: /db/apps/dashboard/plugins/userManager/userManager.xqm]

... restoring a existdb2-2master backup completes (after build.sh clean-default-data-dir), but the login problem persists ... oddly, after refreshing the webpage the login top left is showing admin, but all further action on dashboard fail

regards Peter

dizzzz commented 8 years ago

Please could you clean your browser cache?

pherk commented 8 years ago

already done (Cache, Cookies, Browser-Data cleared), but same picture

Peter

Ubuntu 14.04LTS, Java8, FF43

Quoting Dannes Wessels notifications@github.com:

Please could you clean your browser cache?

Reply to this email directly or view it on GitHub: https://github.com/eXist-db/exist/issues/844#issuecomment-169600276

dizzzz commented 8 years ago

@pherk I'd prefer not to hijack this thread :-) please start a new thread, and verify if you have any plugin in the browser that blocks javascript, ads, etc; please switch them all off. Your issue is not about exist-db not being started...

StephanMa commented 8 years ago

Well i will take the opportunity to give you a small feedback.

Now i am using the Version 3.0.RC2 (develop-503ad32).

The log says still the same "Configuration problem: class not found for module 'http://exist-db.org/xquery/jndi' (ClassNotFoundException); class:'org.exist.xquery.modules.jndi.JNDIModule'; message:'org.exist.xquery.modules.jndi.JNDIModule' "

No changes were made to any of the conf-Files. Just plain cloning and ./build.sh

System: Ubuntu 15.10 Java 1.8.0_74

Update: I saw that 7 modules where evicted by Ivy. there are 95 modules but only 88 artifacts. Afterwards i got a "unknown resolver chain" error. These are the evicted modules:

[ivy:retrieve] :: evicted modules: [ivy:retrieve] org.apache.tika#tika-core;1.5 by [org.apache.tika#tika-core;1.12] in [default] [ivy:retrieve] com.healthmarketscience.jackcess#jackcess;2.1.0 by [com.healthmarketscience.jackcess#jackcess;2.1.2] in [default] [ivy:retrieve] commons-lang#commons-lang;2.4 by [commons-lang#commons-lang;2.6] in [default] [ivy:retrieve] org.jdom#jdom2;2.0.3 by [org.jdom#jdom2;2.0.4] in [default] [ivy:retrieve] com.google.guava#guava;10.0 by [com.google.guava#guava;17.0] in [default] [ivy:retrieve] org.apache.uima#uimaj-cpe;2.4.0 by [org.apache.uima#uimaj-cpe;2.6.0] in [default] [ivy:retrieve] org.apache.uima#uimaj-tools;2.4.0 by [org.apache.uima#uimaj-tools;2.6.0] in [default]

StephanMa commented 8 years ago

2016-04-06 15:59:21,405 [WrapperListener_start_runner] WARN (WebAppContext.java [doStart]:503) - Failed startup of context eXist-db Open Source Native XML Database javax.servlet.UnavailableException: org.directwebremoting.servlet.DwrServlet at org.eclipse.jetty.servlet.Holder.doStart(Holder.java:114) ~[jetty-servlet-8.1.17.v20150415.jar:8.1.17.v20150415] at org.eclipse.jetty.servlet.ServletHolder.doStart(ServletHolder.java:298) ~[jetty-servlet-8.1.17.v20150415.jar:8.1.17.v20150415] at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) ~[jetty-util-8.1.17.v20150415.jar:8.1.17.v20150415] at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:791) ~[jetty-servlet-8.1.17.v20150415.jar:8.1.17.v20150415] at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:265) ~[jetty-servlet-8.1.17.v20150415.jar:8.1.17.v20150415] at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1242) ~[jetty-webapp-8.1.17.v20150415.jar:8.1.17.v20150415] at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717) ~[jetty-server-8.1.17.v20150415.jar:8.1.17.v20150415] at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494) [jetty-webapp-8.1.17.v20150415.jar:8.1.17.v20150415] at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) [jetty-util-8.1.17.v20150415.jar:8.1.17.v20150415] at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229) [jetty-server-8.1.17.v20150415.jar:8.1.17.v20150415] at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) [jetty-util-8.1.17.v20150415.jar:8.1.17.v20150415] at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95) [jetty-server-8.1.17.v20150415.jar:8.1.17.v20150415] at org.eclipse.jetty.server.Server.doStart(Server.java:282) [jetty-server-8.1.17.v20150415.jar:8.1.17.v20150415] at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) [jetty-util-8.1.17.v20150415.jar:8.1.17.v20150415] at org.exist.jetty.JettyStart.run(JettyStart.java:199) [exist-optional.jar:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_74] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_74] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_74] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_74] at org.exist.wrapper.Main.start(Main.java:95) [classes/:?] at org.tanukisoftware.wrapper.WrapperManager$10.run(WrapperManager.java:4163) [wrapper.jar:3.5.26]

tuurma commented 7 years ago

this issue seems no longer relevant, hopefully @StephanMa would be willing to test new 3.0 release?

joewiz commented 7 years ago

Closing due to lack of response from user reporting the problem. I assume the issue no longer affects 3.x releases. Please open a new issue if you experience this problem with 3.4.0+.