You are viewing a plain text version of this content. The canonical link for it is here.

Posted to solr-dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2008/04/16 21:01:27 UTC

[jira] Resolved: (SOLR-541) Legacy update support doesn't log errors

     [ https://issues.apache.org/jira/browse/SOLR-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hoss Man resolved SOLR-541.
---------------------------

    Resolution: Fixed

Committed revision 648794.


> Legacy update support doesn't log errors
> ----------------------------------------
>
>                 Key: SOLR-541
>                 URL: https://issues.apache.org/jira/browse/SOLR-541
>             Project: Solr
>          Issue Type: Bug
>          Components: update
>    Affects Versions: 1.2
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>             Fix For: 1.3
>
>
> If no handler is mapped to /update, and SolrUpdateServlet (which delegates to XmlUpdateRequestHandler.doLegacyUpdate) is used, any errors encountered (like stale lock files) are only returned to the client in the body of the XML response -- they are not logged by Solr.  Because the legacy XML response info always uses an HTTP status code of 200, there is *nothing* in any server side log (not even the servlet containers access log) to indicate a problem.
> simple fix: add some logging to the error case section of doLegacyUpdate.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.