You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2010/08/02 23:55:16 UTC
[jira] Created: (SOLR-2022) Annecdotal evidence that Solr has
problems running on Tomcat 7
Annecdotal evidence that Solr has problems running on Tomcat 7
--------------------------------------------------------------
Key: SOLR-2022
URL: https://issues.apache.org/jira/browse/SOLR-2022
Project: Solr
Issue Type: Bug
Affects Versions: 1.4.1
Reporter: Hoss Man
Based on this thread, users seem to have problems with Solr on tomcat 7 that do not exist on tomcat 6...
http://search.lucidimagination.com/search/document/9c09498631b7afbb/problems_running_on_tomcat
based on the descri[ption of hte problem, it seems to be related to the way links of the admin screen work (possibly due to changes in how tomcat prioritizes SolrDispatchFilter vs other JSP based links?)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (SOLR-2022) Annecdotal evidence that Solr has
problems running on Tomcat 7
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924662#action_12924662 ]
Hoss Man commented on SOLR-2022:
--------------------------------
Verified the symptoms described using Solr 1.4.1 and tomcat 7.0.4
Specific problems...
>From admin screen, running solr in a webapp named "demo" with a a core named "books" and loading the admin screen...
{noformat}http://localhost:8080/demo/books/admin/{noformat}
the "schema.xml" and "config" links point to these URLs...
{noformat}
http://localhost:8080/demo/books/admin/file/?file=schema.xml
http://localhost:8080/demo/books/admin/file/?file=solrconfig.xml
{noformat}
...those both generate 404 error messages with this descriptions...
{noformat}
message /demo/admin/file/index.jsp
description The requested resource (/demo/admin/file/index.jsp) is not available.
{noformat}
...manullly changing the urls to remove the "/" prior to the question mark makes the URLs work fine.
Clicking the "Search" button on the main admin screen leads to...
{noformat}
http://localhost:8080/demo/books/select/?q=*%3A*&version=2.2&start=0&rows=10&indent=on
{noformat}
..which also fails. again removing the "/" prior to the question mark makes it work.
> Annecdotal evidence that Solr has problems running on Tomcat 7
> --------------------------------------------------------------
>
> Key: SOLR-2022
> URL: https://issues.apache.org/jira/browse/SOLR-2022
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4.1
> Reporter: Hoss Man
>
> Based on this thread, users seem to have problems with Solr on tomcat 7 that do not exist on tomcat 6...
> http://search.lucidimagination.com/search/document/9c09498631b7afbb/problems_running_on_tomcat
> based on the descri[ption of hte problem, it seems to be related to the way links of the admin screen work (possibly due to changes in how tomcat prioritizes SolrDispatchFilter vs other JSP based links?)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Updated: (SOLR-2022) request handler paths ending in "/"
don't work with Tomcat 7
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-2022:
---------------------------
Description:
As originally reported in this thread...
http://search.lucidimagination.com/search/document/9c09498631b7afbb/problems_running_on_tomcat
Tomcat 7 has made changes in how URLs are resolved that result in the requests with paths that end in a "/" character being given to the SolrDispatchFilter with "index.jsp" appended to them. This results in SolrDispatchFilter being unable to correctly identify some situations when a request should be processed by a request handler based on the name registered (ie: "/update/csv/" is seen as "update/csv/index.jsp" so as a result the handler registered to "/update/csv/ is not consulted). The problem manifests as a generic 404 (because the request is propagated to the underlying JspServlet which can not find these paths and jsps in the war)
This is most notable in a basic solr install when clicking some URLs that are linked to from the main admin page (see comments below) but this problem can also affect any situation where a client is attempting to access a request handler (or "/select/") using a path ending in "/". The workaround is to remove hte trailing "/" character
was:
Based on this thread, users seem to have problems with Solr on tomcat 7 that do not exist on tomcat 6...
http://search.lucidimagination.com/search/document/9c09498631b7afbb/problems_running_on_tomcat
Updated description to clarify the scope of hte problem
> request handler paths ending in "/" don't work with Tomcat 7
> ------------------------------------------------------------
>
> Key: SOLR-2022
> URL: https://issues.apache.org/jira/browse/SOLR-2022
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.1.0, 1.2, 1.3, 1.4, 1.4.1, 1.4.2, 1.5, 3.1, 4.0, Next
> Reporter: Hoss Man
>
> As originally reported in this thread...
> http://search.lucidimagination.com/search/document/9c09498631b7afbb/problems_running_on_tomcat
> Tomcat 7 has made changes in how URLs are resolved that result in the requests with paths that end in a "/" character being given to the SolrDispatchFilter with "index.jsp" appended to them. This results in SolrDispatchFilter being unable to correctly identify some situations when a request should be processed by a request handler based on the name registered (ie: "/update/csv/" is seen as "update/csv/index.jsp" so as a result the handler registered to "/update/csv/ is not consulted). The problem manifests as a generic 404 (because the request is propagated to the underlying JspServlet which can not find these paths and jsps in the war)
> This is most notable in a basic solr install when clicking some URLs that are linked to from the main admin page (see comments below) but this problem can also affect any situation where a client is attempting to access a request handler (or "/select/") using a path ending in "/". The workaround is to remove hte trailing "/" character
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Updated: (SOLR-2022) request handler paths ending in "/"
don't work with Tomcat 7
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-2022:
---------------------------
Description:
Based on this thread, users seem to have problems with Solr on tomcat 7 that do not exist on tomcat 6...
http://search.lucidimagination.com/search/document/9c09498631b7afbb/problems_running_on_tomcat
was:
Based on this thread, users seem to have problems with Solr on tomcat 7 that do not exist on tomcat 6...
http://search.lucidimagination.com/search/document/9c09498631b7afbb/problems_running_on_tomcat
based on the descri[ption of hte problem, it seems to be related to the way links of the admin screen work (possibly due to changes in how tomcat prioritizes SolrDispatchFilter vs other JSP based links?)
Affects Version/s: Next
4.0
3.1
1.5
1.4.2
1.1.0
1.2
1.3
1.4
Summary: request handler paths ending in "/" don't work with Tomcat 7 (was: Annecdotal evidence that Solr has problems running on Tomcat 7)
updated summary and description now that root cause has been identified
> request handler paths ending in "/" don't work with Tomcat 7
> ------------------------------------------------------------
>
> Key: SOLR-2022
> URL: https://issues.apache.org/jira/browse/SOLR-2022
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.1.0, 1.2, 1.3, 1.4, 1.4.1, 1.4.2, 1.5, 3.1, 4.0, Next
> Reporter: Hoss Man
>
> Based on this thread, users seem to have problems with Solr on tomcat 7 that do not exist on tomcat 6...
> http://search.lucidimagination.com/search/document/9c09498631b7afbb/problems_running_on_tomcat
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (SOLR-2022) request handler paths ending in "/"
don't work with Tomcat 7
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925495#action_12925495 ]
Hoss Man commented on SOLR-2022:
--------------------------------
FYI: comments in tomcat bug#50161 that this is a result of a deliberate change in order to correctly implement Servlet Spec 3.0 - but i've posted some followup questions - in particular, it's not clear to me that HttpServletRequest.getServletPath() is returning what it should be even in light of the comments posted.
There is some mention that future versions of tomcat may allow a system property to override this behavior from the servlet spec, but in future versions of Solr we should probably don't want to have to rely on that being set. There may be ways we can work around this behavior a little better -- depending on what response we get in bug#50161 we might consider changes to our web.xml to override the default "welcome-file" behavior, or changing the way SolrDispatchFilter attempts to parse the URL path.
> request handler paths ending in "/" don't work with Tomcat 7
> ------------------------------------------------------------
>
> Key: SOLR-2022
> URL: https://issues.apache.org/jira/browse/SOLR-2022
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.1.0, 1.2, 1.3, 1.4, 1.4.1, 1.4.2, 1.5, 3.1, 4.0, Next
> Reporter: Hoss Man
>
> Based on this thread, users seem to have problems with Solr on tomcat 7 that do not exist on tomcat 6...
> http://search.lucidimagination.com/search/document/9c09498631b7afbb/problems_running_on_tomcat
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] Commented: (SOLR-2022) Annecdotal evidence that Solr has
problems running on Tomcat 7
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925269#action_12925269 ]
Hoss Man commented on SOLR-2022:
--------------------------------
Well, the root cause seems to be a bug in tomcat...
https://issues.apache.org/bugzilla/show_bug.cgi?id=50161
for these specific links, we could work around the problem by removing the trailing "/" in any links on the admin screen to a solr handler (SolrCore internally normalizes handler paths and ignores the trailing "/" anyway) but that wouldn't help any users who have clients hitting ".../select/?..." (or any other handler) that try to upgrade tomcat.
> Annecdotal evidence that Solr has problems running on Tomcat 7
> --------------------------------------------------------------
>
> Key: SOLR-2022
> URL: https://issues.apache.org/jira/browse/SOLR-2022
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4.1
> Reporter: Hoss Man
>
> Based on this thread, users seem to have problems with Solr on tomcat 7 that do not exist on tomcat 6...
> http://search.lucidimagination.com/search/document/9c09498631b7afbb/problems_running_on_tomcat
> based on the descri[ption of hte problem, it seems to be related to the way links of the admin screen work (possibly due to changes in how tomcat prioritizes SolrDispatchFilter vs other JSP based links?)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org