No, I'm pretty sure nothing implements SolrInfoMBean.
I applied the new 1K version of SOLR-1427.patch from
https://issues.apache.org/jira/browse/SOLR-1427
(which appears to be a secondary patch, to be applied once the main
SOLR-1427 patch has already been applied) to my problematic Solr
instance, which is based on Solr SVN r815830. This patch did not seem
to solve the hang problem; once I reenabled JMX, then the process
would hang at the same spot, i.e. right after
INFO: Adding debug
component:org.apache.solr.handler.component.debugcompon...@1d7b222
appeared in the Tomcat log.
When Solr/Tomcat are hung, there are two Solr-related threads that
show up in a thread dump. I'll paste those stack traces below:
"pool-1-thread-1" prio=6 tid=0x0b1ef800 nid=0xdc8 waiting on condition
[0x0b68f000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x035f3e60> (a
java.util.concurrent.CountDownLatch$Sync)
at java.util.concurrent.locks.LockSupport.park(Unknown Source)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(Unknown
Source)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(Unknown
Source)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(Unknown
Source)
at java.util.concurrent.CountDownLatch.await(Unknown Source)
at org.apache.solr.core.SolrCore$1.call(SolrCore.java:559)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
"Thread-1" prio=6 tid=0x00c92c00 nid=0xf14 in Object.wait() [0x0b19e000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x035d2ab0> (a java.lang.Object)
at java.lang.Object.wait(Object.java:485)
at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:994)
- locked <0x035d2ab0> (a java.lang.Object)
at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:907)
at
org.apache.solr.handler.ReplicationHandler.getIndexVersion(ReplicationHandler.java:472)
at
org.apache.solr.handler.ReplicationHandler.getStatistics(ReplicationHandler.java:490)
at
org.apache.solr.core.JmxMonitoredMap$SolrDynamicMBean.getMBeanInfo(JmxMonitoredMap.java:224)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getNewMBeanClassName(Unknown
Source)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(Unknown
Source)
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(Unknown Source)
at org.apache.solr.core.JmxMonitoredMap.put(JmxMonitoredMap.java:137)
at org.apache.solr.core.JmxMonitoredMap.put(JmxMonitoredMap.java:47)
at
org.apache.solr.core.SolrResourceLoader.inform(SolrResourceLoader.java:446)
at org.apache.solr.core.SolrCore.<init>(SolrCore.java:578)
at org.apache.solr.core.CoreContainer.create(CoreContainer.java:425)
at org.apache.solr.core.CoreContainer.load(CoreContainer.java:278)
at
org.apache.solr.core.CoreContainer$Initializer.initialize(CoreContainer.java:117)
at
org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:83)
at
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
<snip>
2009/9/18 Grant Ingersoll <gsing...@apache.org>:
> Also, do you have any custom components or anything that implements
> SolrInfoMBean?
>
> On Sep 18, 2009, at 8:16 AM, Grant Ingersoll wrote:
>
>> Can you try the patch I just put up on
>> https://issues.apache.org/jira/browse/SOLR-1427 and let me know if it works
>> when JMX is enabled?
>>
>> Also, do you have warming queries setup?
>>
>> On Sep 17, 2009, at 12:46 PM, Chris Harris wrote:
>>
>>> It looks like this works as a fix for me as well. (I'm not currently
>>> using JMX for anything anyway.)
>>>
>>> Curiously, the single-core example solrconfig.xml also has "<jmx />",
>>> but it doesn't seem to be a problem there.
>>>
>>> 2009/9/17 Dadasheva, Olga <olga_dadash...@harvard.edu>:
>>>>
>>>> Hi,
>>>>
>>>> FWIW: disabling <jmx/> fixed this problem for me.
>>>>
>>>> Thanks you!
>>>>
>>>> -Olga
>>>>
>>>> -----Original Message-----
>>>> From: ysee...@gmail.com [mailto:ysee...@gmail.com] On Behalf Of Yonik
>>>> Seeley
>>>> Sent: Thursday, September 17, 2009 1:09 PM
>>>> To: solr-user@lucene.apache.org
>>>> Subject: Re: Latest trunk locks execution thread in
>>>> SolrCore.getSearcher()
>>>>
>>>> Interesting... I still haven't been able to reproduce a hang with either
>>>> jetty or tomcat.
>>>> I enabled replication and JMX... still nothing.
>>>>
>>>> -Yonik
>>>> http://www.lucidimagination.com
>>>>
>>>>
>>>> On Thu, Sep 17, 2009 at 12:35 PM, Chris Harris <rygu...@gmail.com>
>>>> wrote:
>>>>>
>>>>> I found what looks like the same issue when I tried to install r815830
>>>>> under Tomcat. (It works ok with the normal Jetty example/start.jar.) I
>>>>> haven't checked the stack trace, but Tomcat would hang right after the
>>>>> message
>>>>>
>>>>> INFO: Adding debug
>>>>> component:org.apache.solr.handler.component.debugcompon...@1904e0d
>>>>>
>>>>> showed up in the log.
>>>>>
>>>>> I have a little more evidence about Yonik's theory that SOLR-1427 is
>>>>> part of the cause. In particular, when I reverse-merged r815587 (the
>>>>> commit for SOLR-1427) into (out of?) my r815830-based working copy,
>>>>> then Tomcat was able to load Solr normally.
>>>>>
>>>>> 2009/9/16 Yonik Seeley <yo...@lucidimagination.com>:
>>>>>>
>>>>>> On a quick look, it looks like this was caused (or at least triggered
>>>>>> by)
>>>>>> https://issues.apache.org/jira/browse/SOLR-1427
>>>>>>
>>>>>> Registering the bean in the SolrCore constructor causes it to
>>>>>> immediately turn around and ask for the stats which asks for a
>>>>>> searcher, which blocks.
>>>>>>
>>>>>> -Yonik
>>>>>> http://www.lucidimagination.com
>>>>>>
>>>>>> On Wed, Sep 16, 2009 at 9:34 PM, Dadasheva, Olga
>>>>>> <olga_dadash...@harvard.edu> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I am testing EmbeddedSolrServer vs StreamingUpdateSolrServer for
>>>>>>> my crawlers using more or less recent Solr code and everything was
>>>>>>> fine till today when I took the latest trunk code.
>>>>>>> When I start my crawler I see a number of INFO outputs
>>>>>>> 2009-09-16 21:08:29,399 INFO Adding
>>>>>>> component:org.apache.solr.handler.component.highlightcompon...@36ae8
>>>>>>> 3
>>>>>>> (SearchHandler.java:132) - [main]
>>>>>>> 2009-09-16 21:08:29,400 INFO Adding
>>>>>>> component:org.apache.solr.handler.component.statscompon...@1fb24d3
>>>>>>> (SearchHandler.java:132) - [main]
>>>>>>> 2009-09-16 21:08:29,401 INFO Adding
>>>>>>> component:org.apache.solr.handler.component.termvectorcompon...@14ba
>>>>>>> 9a2
>>>>>>> (SearchHandler.java:132) - [main]
>>>>>>> 2009-09-16 21:08:29,402 INFO Adding debug
>>>>>>> component:org.apache.solr.handler.component.debugcompon...@12ea1dd
>>>>>>> (SearchHandler.java:137) - [main]
>>>>>>>
>>>>>>> and then the log/program stops.
>>>>>
>>>>
>>
>> --------------------------
>> Grant Ingersoll
>> http://www.lucidimagination.com/
>>
>> Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids) using
>> Solr/Lucene:
>> http://www.lucidimagination.com/search
>>
>
> --------------------------
> Grant Ingersoll
> http://www.lucidimagination.com/
>
> Search the Lucene ecosystem (Lucene/Solr/Nutch/Mahout/Tika/Droids) using
> Solr/Lucene:
> http://www.lucidimagination.com/search
>
>
