[
https://issues.apache.org/jira/browse/SOLR-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545188#comment-13545188
]
Shawn Heisey edited comment on SOLR-4274 at 1/6/13 6:35 PM:
------------------------------------------------------------
There is also a pair of exceptions logged to stderr by 3.5.0/jetty6, using the
standard JUL binding. No idea whether these can be shortened or eliminated. I
do not see the jetty exceptions on stderr with Solr 4.1 under Jetty 8, but on
that deployment, I am using the log4j binding, which seems to grab a lot more
logs, so it may be logged to Solr's log now.
was (Author: elyograg):
There is also a pair of exceptions logged to stdout by jetty. No idea
whether these can be shortened or eliminated.
> Solr logs loud exception when a client closes the connection before the
> response is sent
> ----------------------------------------------------------------------------------------
>
> Key: SOLR-4274
> URL: https://issues.apache.org/jira/browse/SOLR-4274
> Project: Solr
> Issue Type: Bug
> Affects Versions: 3.5, 4.0
> Reporter: Shawn Heisey
> Fix For: 4.2, 5.0
>
>
> If a client closes the HTTP/TCP connection before Solr has had time to
> respond, a loud Jetty exception is thrown and logged. If possible, I would
> like to see that reduced to a warning message that includes the request
> parameters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
