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

Timothy Potter commented on SOLR-5145:
--------------------------------------

I'm almost certain this is because somewhere in the code for this test, the 
core doesn't get closed. Look for instances of cc.getCore(name) outside of the 
try with resources block, i.e. should be doing:

      try (SolrCore core = cc.getCore(coreName)) {
          // code
      }

> wait w/o notify situation happening on shutdown in 
> CoreContainer/CloserThread/SolrCores.modifyLock
> --------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-5145
>                 URL: https://issues.apache.org/jira/browse/SOLR-5145
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>
> Working on SOLR-4952 i was running tests on the 4x branch and noticed 
> TestManagedSchema.testPersistUniqueKey stalled for 1623s -- but nothing baout 
> hte situation seems to be specific to that test.
> I'll attache a threaddump, but the key things i note...
> * TestHarness is trying to shutdown the CoreContainer
> * CoreContainer.shutdown(CoreContainer.java:358) is waiting on 
> <0x00000000f690b880> (a org.apache.solr.core.CloserThread)
> * CloserThread.run(CoreContainer.java:961) is waiting on <0x00000000e068d718> 
> (a java.lang.Object)
> ** that's aparently "SolrCores.modifyLock"
> * a "searcherExecutor-46-thread-1" is still alive and parking to wait for  
> <0x00000000f66ff860> (a 
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> * no other threads seem to be doing anything -- so as far as i can tell 
> nothing is ever going to notify on that modifyLock



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to