[
https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232622#comment-13232622
]
Yonik Seeley commented on SOLR-3159:
------------------------------------
>From that link, it looks like it should probably be:
{code}
<Call name="setAttribute">
<Arg>org.eclipse.jetty.server.Request.maxFormContentSize</Arg>
<Arg>200000</Arg>
</Call>
{code}
Can anyone test and confirm this works?
bq. These are the same settings we had for jetty 6, but I do not know if this
is still the best choice. In particular, I'm not sure about the
.bio.SocketConnector vs .nio.SelectChannelConnector
The NIO connector was causing intermittent failures on Jenkins. I have no idea
if the bugs were ever found/fixed in Jetty land - but it's a risk. It would be
nice to move to the NIO connector if it is now stable though, since it could
possibly allow for better logging/debugging (i.e. if we can specify our own
thread pool to handle requests such that we can tell different jetty instances
apart during logging).
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and
> improvements are now hosted at eclipse. Assuming performance is equivalent,
> I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
