sockets are used during this time? Try 'netstat -s | fgrep 8983' (or
your Solr URL port #) and watch the active, TIME_WAIT, CLOSE_WAIT sockets build
up. This may give a hint.
On Tue, Oct 13, 2009 at 8:47 AM, Dadasheva, Olga
wrote:
> Hi,
>
&g
Hi,
I am indexing documents using StreamingUpdateSolrServer. My 'setup' code
is almost a copy of the junit test of the Solr trunk.
try {
StreamingUpdateSolrServer streamingServer = new
StreamingUpdateSolrServer( url, 2, 5 ) {
@Overri
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 on S
>> 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
>> wrote:
>>> Hi,
>>>
>>>
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.apa
5:10 PM, Dadasheva, Olga wrote:
> Hi,
>
> I run Solr 1.3 in Weblogic 10.3 Java 6; I have a single core
> application deployed to the same server as Solr 1.3.
> I am not using solrj.
>
> I do not have any problems with search and update - they work fine.
>
> However
Hi,
I run Solr 1.3 in Weblogic 10.3 Java 6;
I have a single core application deployed to the same server as Solr
1.3.
I am not using solrj.
I do not have any problems with search and update - they work fine.
However I am getting stack overflow when I try to access solr/admin
page.
java.lang
