You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2011/03/15 08:41:29 UTC

[jira] Created: (CONNECTORS-168) Solr connector does not handle 500 errors well; it assumes they have an XML response

Solr connector does not handle 500 errors well; it assumes they have an XML response
------------------------------------------------------------------------------------

                 Key: CONNECTORS-168
                 URL: https://issues.apache.org/jira/browse/CONNECTORS-168
             Project: ManifoldCF
          Issue Type: Bug
          Components: Lucene/SOLR connector
    Affects Versions: ManifoldCF 0.2
            Reporter: Karl Wright
            Assignee: Karl Wright


The Solr Connector presumes that the response from Solr is XML.  Unfortunately, in some cases it isn't, such as when there's a 500 error and a stack trace.  We should make this work too, without dumping a trace to standard out.


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (CONNECTORS-168) Solr connector does not handle 500 errors well; it assumes they have an XML response

Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CONNECTORS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Wright updated CONNECTORS-168:
-----------------------------------

    Fix Version/s: ManifoldCF 0.2
           Status: Patch Available  (was: Open)

This patch should allow the raw stack trace and error to be returned if the response is not XML.


> Solr connector does not handle 500 errors well; it assumes they have an XML response
> ------------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-168
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-168
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Lucene/SOLR connector
>    Affects Versions: ManifoldCF 0.2
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 0.2
>
>
> The Solr Connector presumes that the response from Solr is XML.  Unfortunately, in some cases it isn't, such as when there's a 500 error and a stack trace.  We should make this work too, without dumping a trace to standard out.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (CONNECTORS-168) Solr connector does not handle 500 errors well; it assumes they have an XML response

Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CONNECTORS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Wright resolved CONNECTORS-168.
------------------------------------

    Resolution: Fixed

r1081809.


> Solr connector does not handle 500 errors well; it assumes they have an XML response
> ------------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-168
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-168
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Lucene/SOLR connector
>    Affects Versions: ManifoldCF 0.2
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 0.2
>
>         Attachments: CONNECTORS-168.patch
>
>
> The Solr Connector presumes that the response from Solr is XML.  Unfortunately, in some cases it isn't, such as when there's a 500 error and a stack trace.  We should make this work too, without dumping a trace to standard out.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (CONNECTORS-168) Solr connector does not handle 500 errors well; it assumes they have an XML response

Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CONNECTORS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Wright updated CONNECTORS-168:
-----------------------------------

    Comment: was deleted

(was: This patch should allow the raw stack trace and error to be returned if the response is not XML.
)

> Solr connector does not handle 500 errors well; it assumes they have an XML response
> ------------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-168
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-168
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Lucene/SOLR connector
>    Affects Versions: ManifoldCF 0.2
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 0.2
>
>         Attachments: CONNECTORS-168.patch
>
>
> The Solr Connector presumes that the response from Solr is XML.  Unfortunately, in some cases it isn't, such as when there's a 500 error and a stack trace.  We should make this work too, without dumping a trace to standard out.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (CONNECTORS-168) Solr connector does not handle 500 errors well; it assumes they have an XML response

Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CONNECTORS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Wright updated CONNECTORS-168:
-----------------------------------

    Attachment: CONNECTORS-168.patch

This patch should allow the raw stack trace and error to be returned if the response is not XML.


> Solr connector does not handle 500 errors well; it assumes they have an XML response
> ------------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-168
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-168
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Lucene/SOLR connector
>    Affects Versions: ManifoldCF 0.2
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 0.2
>
>         Attachments: CONNECTORS-168.patch
>
>
> The Solr Connector presumes that the response from Solr is XML.  Unfortunately, in some cases it isn't, such as when there's a 500 error and a stack trace.  We should make this work too, without dumping a trace to standard out.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (CONNECTORS-168) Solr connector does not handle 500 errors well; it assumes they have an XML response

Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CONNECTORS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Wright updated CONNECTORS-168:
-----------------------------------

    Status: Open  (was: Patch Available)

> Solr connector does not handle 500 errors well; it assumes they have an XML response
> ------------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-168
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-168
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Lucene/SOLR connector
>    Affects Versions: ManifoldCF 0.2
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 0.2
>
>         Attachments: CONNECTORS-168.patch
>
>
> The Solr Connector presumes that the response from Solr is XML.  Unfortunately, in some cases it isn't, such as when there's a 500 error and a stack trace.  We should make this work too, without dumping a trace to standard out.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira