[MarkLogic Dev General] ML8 404 Error
Dave.Cassel at marklogic.com
Fri Mar 20 16:07:23 PDT 2015
More info about using the declarative rewriter here<http://docs.marklogic.com/guide/relnotes/chap4#id_43618>.
Developer Community Manager
From: Erik Hennum <Erik.Hennum at marklogic.com<mailto:Erik.Hennum at marklogic.com>>
Reply-To: MarkLogic Developer Discussion <general at developer.marklogic.com<mailto:general at developer.marklogic.com>>
Date: Friday, March 20, 2015 at 7:05 PM
To: MarkLogic Developer Discussion <general at developer.marklogic.com<mailto:general at developer.marklogic.com>>
Subject: Re: [MarkLogic Dev General] ML8 404 Error
When you say "redeployed my app," what kind of application is it?
If it's a ApplicationBuilder app, it depends on the REST API, which switched from the imperative XQuery rewriter to the new declarative XML rewriter. In that case, you might open the appserver in the Admin Ui and check the url rewriter field to make sure that upgrade has set the field to
Hoping that helps,
From: general-bounces at developer.marklogic.com<mailto:general-bounces at developer.marklogic.com> [general-bounces at developer.marklogic.com<mailto:general-bounces at developer.marklogic.com>] on behalf of Paul Williams [Paul.Williams at flatironssolutions.com<mailto:Paul.Williams at flatironssolutions.com>]
Sent: Friday, March 20, 2015 3:17 PM
To: general at developer.marklogic.com<mailto:general at developer.marklogic.com>
Subject: [MarkLogic Dev General] ML8 404 Error
I recently upgraded to ML8 and redeployed my app on my local dev environment (Win Serv 2k8) without a hitch. But when I tried the same upgrade steps on a test server (Linux), I am getting a 404 error when trying to access the application. It’s as if it cannot see modules in the modules db associated with the appserver. I’ve double checked the modules db and root path settings.
In the qconsole, the Content Source properly lists my “[database] ([modules db])” combination and I can invoke a loaded module there successfully. The ErrorLog shows nothing and the AccessLog for that port just shows the GET attempt with the 404 response code.
-- Paul Williams
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the General