Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
We got this error and we traced it back to have a too long url going to our solr instance. Jetty was not able to cope with this url. The too long url was caused by adding a lot of facets.
The solution was to extend the [solr-dir]/etc/jetty.xml and extend the addConnector with a higher headerBufferSize.
This:
<Call name="addConnector">
<Arg>
<New class="org.mortbay.jetty.bio.SocketConnector">
<Set name="host"><SystemProperty name="jetty.host" /></Set>
<Set name="port"><SystemProperty name="jetty.port" default="8983"/></Set>
<Set name="maxIdleTime">50000</Set>
<Set name="lowResourceMaxIdleTime">1500</Set>
<Set name="statsOn">false</Set>
</New>
</Arg>
</Call>
Should become
<Call name="addConnector">
<Arg>
<New class="org.mortbay.jetty.bio.SocketConnector">
<Set name="host"><SystemProperty name="jetty.host" /></Set>
<Set name="port"><SystemProperty name="jetty.port" default="8983"/></Set>
<Set name="maxIdleTime">50000</Set>
<Set name="lowResourceMaxIdleTime">1500</Set>
<Set name="statsOn">false</Set>
<Set name='headerBufferSize'>8096</Set>
</New>
</Arg>
</Call>
We just wanted to post this solution in case someone has the same problem. It took us some time to figure it out.
Comments
Comment #1
xatoo CreditAttribution: xatoo commentedNote that the error in the title can also mean that jetty was unable to write to the index. In my case because I had to chown/chmod the index files to be owned by jetty. In general: always look into the Jetty/Tomcat logs to give some more meaning to Solr errors.
Comment #2
OanaIlea CreditAttribution: OanaIlea at bio.logis Genetic Information Management GmbH commentedThis issue was closed due to lack of activity over a long period of time. If the issue is still acute for you, feel free to reopen it and describe the current state.