lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Commented: (SOLR-118) Some admin pages stop working with "error 404" as the only symptom
Date Mon, 22 Jan 2007 19:48:30 GMT


Hoss Man commented on SOLR-118:

FYI: there was more tothat orriginal thread then the apache archives show (because they are
split up by month) here's the full discussion... the time i wasn't able to reproduce the problem, but i wasn't hammering the port very
hard.  I suspect heavily that since hte problem was only with the admin pages, and all of
the update/query functionality still worked fine that it was a JSP issue with Jetty.

> Some admin pages stop working with "error 404" as the only symptom
> ------------------------------------------------------------------
>                 Key: SOLR-118
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: web gui
>         Environment: Fedora Core 4 (Linux version 2.6.11-1.1369_FC4smp)  Sun's JVM 1.5.0_07-b03
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
> This was reported to the mailing list a while ago, see
> Today I'm seeing the same thing on a Solr instance that has been running since January
9th (about 13 days) with the plain start.jar setup. Index contains 150'000 docs, 88322 search
requests to date.
> $ curl http://localhost:8983/solr/admin/analysis.jsp
> <html>
> <head>
> <title>Error 404 /admin/analysis.jsp</title>
> </head>
> <body>
> <h2>HTTP ERROR: 404</h2><pre>/admin/analysis.jsp</pre>
> <p>RequestURI=/solr/admin/analysis.jsp</p>
> ...
> curl http://localhost:8983/solr/admin/index.jsp
> <html>
> <head>
> <title>Error 404 /admin/index.jsp</title>
> </head>
> <body>
> <h2>HTTP ERROR: 404</h2><pre>/admin/index.jsp</pre>
> <p>RequestURI=/solr/admin/index.jsp</p>
> ...
> Other admin pages work correctly, for example http://localhost:8983/solr/admin/stats.jsp
> I don't see any messages in the logs, which are capturing stdout and stderr from the
> I guess I'll have to restart this instance, I'm out of possibilities to find out what's
happening exactly.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message