Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[4.7.0] Restore fails if contextPath is "/" #2919

Open
claudius108 opened this issue Aug 4, 2019 · 2 comments
Open

[4.7.0] Restore fails if contextPath is "/" #2919

claudius108 opened this issue Aug 4, 2019 · 2 comments
Labels
awaiting-response requires additional information from submitter

Comments

@claudius108
Copy link
Contributor

claudius108 commented Aug 4, 2019 •
edited by dizzzz

Restore of a database contents from command line fails if contextPath is "/",instead of "/exist".

Context:
latest eXist 4.7.0, ubuntu, java 1.8, 64 bit, JAR installer,.

Error message:
Problems occured found during restore:
ERROR: HTTP server returned unexpected status: Not Found

If you restored collections inside /db/apps, you may want
to rebuild the application repository. To do so, run the following query
as admin:

import module namespace repair="http://exist-db.org/xquery/repo/repair"
at "resource:org/exist/xquery/modules/expathrepo/repair.xql";
repair:clean-all(),
repair:repair()
org.xmldb.api.base.XMLDBException: HTTP server returned unexpected status: Not Found
	at org.exist.xmldb.RemoteCollection.instance(RemoteCollection.java:99)
	at org.exist.xmldb.RemoteCollection.instance(RemoteCollection.java:75)
	at org.exist.xmldb.DatabaseImpl.readCollection(DatabaseImpl.java:267)
	at org.exist.xmldb.DatabaseImpl.getRemoteCollection(DatabaseImpl.java:229)
	at org.exist.xmldb.DatabaseImpl.getCollection(DatabaseImpl.java:169)
	at org.exist.xmldb.DatabaseImpl.getCollection(DatabaseImpl.java:158)
	at org.xmldb.api.DatabaseManager.getCollection(DatabaseManager.java:235)
	at org.exist.backup.Main.process(Main.java:261)
	at org.exist.backup.Main.main(Main.java:406)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.exist.start.Main.invokeMain(Main.java:140)
	at org.exist.start.Main.run(Main.java:453)
	at org.exist.start.Main.main(Main.java:64)
Caused by: org.apache.xmlrpc.client.XmlRpcHttpTransportException: HTTP server returned unexpected status: Not Found
	at org.apache.xmlrpc.client.XmlRpcSunHttpTransport.getInputStream(XmlRpcSunHttpTransport.java:94)
	at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:152)
	at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:143)
	at org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTransport.java:69)
	at org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:56)
	at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167)
	at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:158)
	at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:147)
	at org.exist.xmldb.RemoteCollection.instance(RemoteCollection.java:87)
	... 15 more
caused by 
org.apache.xmlrpc.client.XmlRpcHttpTransportException: HTTP server returned unexpected status: Not Found
	at org.apache.xmlrpc.client.XmlRpcSunHttpTransport.getInputStream(XmlRpcSunHttpTransport.java:94)
	at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(XmlRpcStreamTransport.java:152)
	at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(XmlRpcHttpTransport.java:143)
	at org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(XmlRpcSunHttpTransport.java:69)
	at org.apache.xmlrpc.client.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:56)
	at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:167)
	at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:158)
	at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java:147)
	at org.exist.xmldb.RemoteCollection.instance(RemoteCollection.java:87)
	at org.exist.xmldb.RemoteCollection.instance(RemoteCollection.java:75)
	at org.exist.xmldb.DatabaseImpl.readCollection(DatabaseImpl.java:267)
	at org.exist.xmldb.DatabaseImpl.getRemoteCollection(DatabaseImpl.java:229)
	at org.exist.xmldb.DatabaseImpl.getCollection(DatabaseImpl.java:169)
	at org.exist.xmldb.DatabaseImpl.getCollection(DatabaseImpl.java:158)
	at org.xmldb.api.DatabaseManager.getCollection(DatabaseManager.java:235)
	at org.exist.backup.Main.process(Main.java:261)
	at org.exist.backup.Main.main(Main.java:406)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.exist.start.Main.invokeMain(Main.java:140)
	at org.exist.start.Main.run(Main.java:453)
	at org.exist.start.Main.main(Main.java:64)
@triage-new-issues triage-new-issues bot added the triage issue needs to be investigated label Aug 4, 2019
@duncdrum
Copy link
Contributor

does this still apply to 5.0.0?

@duncdrum duncdrum added the awaiting-response requires additional information from submitter label Sep 27, 2019
@triage-new-issues triage-new-issues bot removed the triage issue needs to be investigated label Sep 27, 2019
@claudius108
Copy link
Contributor Author

I have not tested in 5.0.0.

@duncdrum duncdrum mentioned this issue Oct 28, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
awaiting-response requires additional information from submitter
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@claudius108 @duncdrum