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

xatoo’s picture

Note 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.

OanaIlea’s picture

Status: Active » Closed (outdated)

This 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.