[
https://issues.apache.org/jira/browse/SOLR-9244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348946#comment-15348946
]
Gary Lee commented on SOLR-9244:
--------------------------------
[~tomasflobbe] I don't think I've seen a stack trace - just a lot of these
messages in our solr logs:
{noformat}
2016-06-24 23:05:24,173 ERROR org.apache.solr.request.SolrRequestInfo -
Previous SolrRequestInfo was not closed! req=commit=true
2016-06-24 23:05:24,173 ERROR org.apache.solr.request.SolrRequestInfo - prev ==
info : false
{noformat}
When I debugged through this one time, I remember it was the HttpSolrCall.call
where I saw the error occur, so i was led to believe that this was possibly the
point where we do not close, but as you pointed out, the destroy is called, so
it is getting cleaned up. In that case, the code path in SOLR-8657 is probably
the same one we're hitting.
> Lots of "Previous SolrRequestInfo was not closed" in Solr log
> -------------------------------------------------------------
>
> Key: SOLR-9244
> URL: https://issues.apache.org/jira/browse/SOLR-9244
> Project: Solr
> Issue Type: Bug
> Components: Server
> Affects Versions: 5.3.1
> Reporter: Gary Lee
> Priority: Minor
> Fix For: 5.3.1
>
>
> After upgrading to Solr 5.3.1, we started seeing a lot of "Previous
> SolrRequestInfo was not closed" ERROR level messages in the logs. Upon
> further inspection, it appears this is a sanity check and not an error that
> needs attention. It appears that the SolrRequestInfo isn't freed in one
> particular path (no corresponding call to SolrRequestInfo.clearRequestInfo in
> HttpSolrCall.call), which often leads to a lot of these messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
