that there was no issue in network.
> One more thing i need to include here is i had found same bug with ID
> SOLR-2235 on ASF JIRA.
>
>
> Thanks,
> Gaurav
>
>> Date: Fri, 3 Jun 2011 09:13:00 -0400
>> Subject: Re: java.io.IOException: The specified n
ct: Re: java.io.IOException: The specified network name is no longer
> available
> From: erickerick...@gmail.com
> To: solr-user@lucene.apache.org
>
> You'v got to tell us more about your setup. We can only guess that you're
> on a remote file system and there's a problem th
> Sent: Fri, June 3, 2011 1:52:42 AM
> Subject: java.io.IOException: The specified network name is no longer
available
>
>
> Hi,
>
> I am using solr 1.4.1 and at the time of updating index getting following
>error:
>
> 2011-06-03 05:54:06,943 ERROR [org.apache.solr.c
Fri, Jun 3, 2011 at 1:52 AM, Gaurav Shingala
wrote:
>
> Hi,
>
> I am using solr 1.4.1 and at the time of updating index getting following
> error:
>
> 2011-06-03 05:54:06,943 ERROR [org.apache.solr.core.SolrCore]
> (http-10.38.33.146-8080-4) java.io.IOException: The spec
Hi,
I am using solr 1.4.1 and at the time of updating index getting following error:
2011-06-03 05:54:06,943 ERROR [org.apache.solr.core.SolrCore]
(http-10.38.33.146-8080-4) java.io.IOException: The specified network name is
no longer available
at java.io.RandomAccessFile.readBytes(Native
Erick Erickson wrote:
>
> SOLR uses Lucene, so I'd expect that putting your index files on a share
> isn't any more robust under SOLR than Lucene
>
> Sounds to me like your network's glitchy.
>
>
Except that with Lucene we had separate processes searching and indexing
directly against th
SOLR uses Lucene, so I'd expect that putting your index files on a share
isn't any more robust under SOLR than Lucene
Sounds to me like your network's glitchy.
FWIW
Erick
On Fri, Sep 10, 2010 at 3:00 PM, brian519 wrote:
>
>
> Yonik Seeley-2-2 wrote:
> >
> >
> > Hmmm, that's interesting. I
Yonik Seeley-2-2 wrote:
>
>
> Hmmm, that's interesting. I wonder if it's a Java bug or something?
> There's nothing in lucene/solr that I know of that would lead to "The
> specified network name is no longer
> available".
>
> What JVM are you using?
>
> -Yonik
> http://lucenerevolution.org
On Fri, Sep 10, 2010 at 2:12 PM, brian519 wrote:
> Once we see the error, it is persistent. Restarting Tomcat makes the error
> stop. This is happening across a variety of deployments and networks, so I
> don't think there is an actual network problem. Many other apps operate
> fine on the same
Hi all,
Using Solr 1.4 hosted with Tomcat 6 on Windows 2003 (sometimes Windows 2008)
Occasionally, we can't search anymore and this error shows up in the log
file:
SEVERE: java.io.IOException: The specified network name is no longer
available
at java.io.RandomAccessFile.read
10 matches
Mail list logo
