[ 
https://issues.apache.org/jira/browse/SOLR-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539538#comment-13539538
 ] 

Mark Smith commented on SOLR-4191:
----------------------------------

This happening for me as well on Solr 4.0.  Interestingly enough, I'm not doing 
any writes.  I've got my solr app running for the past few weeks, and have not 
done any changes (no updates, no inserts, only selects).  Every few days I see 
this exception, so I simply kill my server and restart, and everything is fine. 
 Please let me know if there is any test or more info that can help.
                
> Exceptions thrown when /admin/mbeans is accessed during update/commit
> ---------------------------------------------------------------------
>
>                 Key: SOLR-4191
>                 URL: https://issues.apache.org/jira/browse/SOLR-4191
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.1
>         Environment: solr-impl 4.1-SNAPSHOT 1421496 - ncindex - 2012-12-13 
> 14:56:25
>            Reporter: Shawn Heisey
>             Fix For: 4.1, 5.0
>
>         Attachments: solr-2012-12-14[1].log
>
>
> I am getting the following exceptions in quick succession in the solr log 
> when /admin/mbeans is accessed at the moment that an update/commit is 
> happening:
> ERROR - 2012-12-13 18:17:01.930; org.apache.solr.common.SolrException; 
> null:org.eclipse.jetty.io.EofException
> ERROR - 2012-12-13 18:17:01.982; org.apache.solr.common.SolrException; 
> null:org.eclipse.jetty.io.EofException
> WARN  - 2012-12-13 18:17:01.984; org.eclipse.jetty.server.Response; Committed 
> before 500 {msg=Broken pipe,trace=org.eclipse.jetty.io.EofException
> WARN  - 2012-12-13 18:17:01.984; org.eclipse.jetty.servlet.ServletHandler; 
> /solr/s0live/admin/mbeans
> java.lang.IllegalStateException: Committed
> I will attach the full solr log.  Before SOLR-4135 was fixed, I got a *lot* 
> of those exceptions, but these were far less common.  Now these appear to be 
> the only thing I am getting in my logs, which log4j is logging at WARN.

--
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]

Reply via email to