Solr now starts up fine in Tomcat with both JMX and ReplicationHandler
enabled if I construct my working copy as follows:
download solr-r815830
reverse merge r815587 (SOLR-1427: fixed registry MBean issue)
apply 1427.afterlatch.patch
I haven't tried applying 1427.afterlatch.patch to the svn
: 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
Yeah, I believe the hang is really orthoginal to the SearchComponents
issue and seems to be because of the
HURAH! Works for me!
Thank you!
-Original Message-
From: Chris Hostetter [mailto:hossman_luc...@fucit.org]
Sent: Sunday, September 20, 2009 6:49 PM
To: solr-user@lucene.apache.org
Subject: Re: Latest trunk locks execution thread in
SolrCore.getSearcher()
: instance, which is based
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
[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
Forgot to answer this one. Yes, I do have a warming query to get the
sort caches up to speed. I think it takes a while to run; my guess
would be 30 seconds or so.
2009/9/18 Grant Ingersoll gsing...@apache.org:
Also, do you have warming queries setup?
On Sep 17, 2009, at 12:46 PM, Chris Harris
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
: Interesting... I still haven't been able to reproduce a hang with
: either jetty or tomcat.
: I enabled replication and JMX... still nothing.
I haven't tried to reproduce the problem, and i don't even have a concrete
theory as to what the problem is ... but i did want to point out something
: Maybe moving the resourceLoader.inform(infoRegistry) call PRIOR to
: resourceLoader.inform( this ) *or* AFTER latch.countDown() would solve
: this problem?
If this really is the problem, then a more general purpose solution to
future proof us against similar problems down the road would
On Sep 16, 2009, at 6:54 PM, Yonik Seeley wrote:
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
Ok, let me revise my previous report:
It turns out if I take the single-core or multicore example stuff from
running ant example on r815830 and plop them into Tomcat, this
doesn't hang. However, if I plop Solr as I configure it for production
use into Tomcat, it does hang.
The main ways I can
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
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
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
14 matches
Mail list logo
