[MGNLSOLR-14] SOLR server was not found (404) after update solr server config in magnolia Created: 17/Apr/13  Updated: 13/Jun/13  Resolved: 12/Jun/13

Status: Closed
Project: Apache Solr (closed)
Component/s: None
Affects Version/s: 3.0
Fix Version/s: 3.0

Type: Bug Priority: Critical
Reporter: Milan Divilek Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When I updated connectionTimeout property in Configuration-modules/solr/config/solrConfig then Solr server starts to be unreachable from magnolia.

When I do "Add or update content to Apache Solr" then "operation failed with: java.lang.RuntimeException: org.apache.solr.client.solrj.SolrServerException: Server at http://localhost:8983/solr/ was not found (404)." pop up.
When I do "Remove content from Apache Solr" then NPE occure.
There is no more information in log.

Direct connect to Solr server http://localhost:8983/solr/ works without problem. An also after restart Magnolia instance everything works again.



 Comments   
Comment by Jan Haderka [ 10/Jun/13 ]

It seems like following happens:

  • on config update, stop(),start() methods are called in SolrModule class. The first will deregister listener, the second will reregister it and update config in case server is null, however this is not true after config update so server never gets updated (until restart).

One possible solution would be to set server variable to null upon calling stop() method of the module.

Comment by Jan Haderka [ 11/Jun/13 ]

junit test?

Generated at Sun Feb 11 23:19:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.