I upgraded to solr version 4.9. By retrieving search-index data (admin/config/search/apachesolr/settings/solr/index) I got at first these two error messages in the watchdog:
1. Message: JSP support not configured: JSP support not configured;

Response: <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/> <title>Error 500 JSP support not configured</title> </head> <body><h2>HTTP ERROR 500</h2> <p>Problem accessing /solr/core1/admin/stats.jsp. Reason: <pre> JSP support not configured</pre></p><hr /><i><small>Powered by Jetty://</small></i><br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> </body> </html> ;
Request: GET /solr/alertatest/admin/stats.jsp HTTP/1.0 User-Agent: Drupal (+http://drupal.org/) Host: localhost:8983 ;
Caller: call_user_func_array() (line Unknown of Unknown)

2. HTTP 500; JSP support not configured: JSP support not configured

After adding JSP support (http://lucene.472066.n3.nabble.com/Solr-4-0-How-do-I-enable-JSP-support-...) I get these two error messages:
1. HTTP Status: 404;
Message: Not Found: Not Found;

Response: <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/> <title>Error 404 Not Found</title> </head> <body><h2>HTTP ERROR 404</h2> <p>Problem accessing /solr/core1/admin/stats.jsp. Reason: <pre> Not Found</pre></p><hr /><i><small>Powered by Jetty://</small></i><br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> </body> </html> ;
Request: GET /solr/alertatest/admin/stats.jsp HTTP/1.0 User-Agent: Drupal (+http://drupal.org/) Host: localhost:8983 ;
Caller: call_user_func_array() (line Unknown of Unknown)

2. HTTP 404; Not Found: Not Found

Indexing and retrieving results works!
I use Java 8u11 and Solr 4.9.0, without extra jetties (like tomcat)

Any idea how to solve this?

Comments

PROMES’s picture

PROMES
Primary language Dutch
CreditAttribution: PROMES commented
Status: Active » Closed (works as designed)
PROMES’s picture

PROMES
Primary language Dutch
CreditAttribution: PROMES commented

I have two sites with Solr search enabled. A test and a production site. This morning I discovered the production site doesn't have above problem.
I the testsite I disabled all Solr modules and enabled them again. Now it works normal.

R.J. Steinert’s picture

R.J. Steinert CreditAttribution: R.J. Steinert commented

I'm struggling with this error as well. The strange thing is that when other Drupal installations use this Solr server they don't run into this issue when queueing all contetent for reindexing.