Understood. Thanks Hoss.
- Chris
- Original Message -
From: Chris Hostetter
Sent: Fri, 18/9/2009 5:58pm
To: java-user@lucene.apache.org
Subject: RE: New "Stream closed" exception with Java 6 - solved
: > not really ... adding a document multiple times is a perfec
: > not really ... adding a document multiple times is a perfectly legal use
: > case, adding a document with a "Reader" based field where the reader is
: > already closed ... that's not legal (And Lucene doesn't really have any
: > way of knowing if the Reader is closed because *it* closed it.
ers? :-)
Thanks again,
- Chris
- Original Message -
From: Chris Hostetter
Sent: Thu, 17/9/2009 7:38pm
To: java-user@lucene.apache.org
Subject: RE: New "Stream closed" exception with Java 6 - solved
: It turns out that the cause of the exceptions is in fact adding an item
: t
: It turns out that the cause of the exceptions is in fact adding an item
: twice - so you were correct right at the start :-) I ran a test where I
glad to see it all worked out.
: Just a minor point: isn't Lucence in a position to detect the duplicate
: insertion attempt and flag it with so
nks to you, Mark and Grant for all your help on this - much
appreciated.
- Chris
- Original Message -
From: Chris Hostetter
Sent: Tue, 15/9/2009 6:37pm
To: java-user@lucene.apache.org
Subject: RE: New "Stream closed" exception with Java 6
: "it's possibly you just h
: "it's possibly you just have a simple bug where you are closing the reader
before you pass it to Lucene,
:
: or maybe you are mistakenly adding the same field twice
:
: (or in two different documents)"
:
: Are you saying that if I were attempting to delete a doc and then add it
: aga
umption is that 2.4 is stable (we are moving from 2.0 to 2.4
at present) - should I reconsider that assumption?
Thanks for any ideas.
- Chris
- Original Message -
From: Mark Miller
Sent: Tue, 8/9/2009 8:06pm
To: java-user@lucene.apache.org
Subject: Re: New "Stream closed" e
- should I reconsider that assumption?
Thanks for any ideas.
- Chris
- Original Message -
From: Mark Miller
Sent: Tue, 8/9/2009 8:06pm
To: java-user@lucene.apache.org
Subject: Re: New "Stream closed" exception with Java 6
Chris Hostetter wrote:
> : I'm coming to the
om: Chris Hostetter
Sent: Tue, 8/9/2009 7:57pm
To: java-user@lucene.apache.org
Subject: RE: New "Stream closed" exception with Java 6
: I'm coming to the same conclusion - there must be >1 threads accessing this
index at the same time. Better go figure it out ... :-)
caref
Thanks for your input Mark and Chris. I will take all into account
Chris
- Original Message -
From: Mark Miller
Sent: Tue, 8/9/2009 8:06pm
To: java-user@lucene.apache.org
Subject: Re: New "Stream closed" exception with Java 6
Chris Hostetter wrote:
> : I'm
Chris Hostetter wrote:
> : I'm coming to the same conclusion - there must be >1 threads accessing this
> index at the same time. Better go figure it out ... :-)
>
> careful about your assumptions ... you could get this same type of
> exception even with only one thread, the stream that's being
: I'm coming to the same conclusion - there must be >1 threads accessing this
index at the same time. Better go figure it out ... :-)
careful about your assumptions ... you could get this same type of
exception even with only one thread, the stream that's being closed isn't
internal to Luce
- Chris
Chris Bamford
Senior Development Engineer
Scalix
chris.bamf...@scalix.com
Tel: +44 (0)1344 381814
www.scalix.com
- Original Message -
From: Grant Ingersoll
Sent: Thu, 3/9/2009 2:59pm
To: java-user@lucene.apache.org
Subject: Re: New "Stream closed" exception with Java 6
s,
- Chris
----- Original Message -
From: Daniel Shane
Sent: Tue, 1/9/2009 10:52pm
To: java-user@lucene.apache.org
Subject: Re: New "Stream closed" exception with Java 6
I think you should do this instead (it will print the exception
message
*and* the stack trace instead of onl
aniel Shane
Sent: Tue, 1/9/2009 10:52pm
To: java-user@lucene.apache.org
Subject: Re: New "Stream closed" exception with Java 6
I think you should do this instead (it will print the exception message
*and* the stack trace instead of only the message) :
throw new IndexerException (&quo
quot; - " + ex.toString());
}
Thanks,
- Chris
Chris Bamford
Senior Development Engineer
Scalix
chris.bamf...@scalix.com
Tel: +44 (0)1344 381814
www.scalix.com
- Original Message -
From: Grant Ingersoll
Sent: Sat, 29/8/2009 12:00pm
To: java-user@lucene.apache.org
Subject:
attached.
>
> Thanks,
>
> - Chris
>
>
> - Original Message -
> From: Grant Ingersoll
> Sent: Fri, 28/8/2009 1:26pm
> To: java-user@lucene.apache.org
> Subject: Re: New "Stream closed" exception with Java 6
>
> Are there any log messages a
: java-user@lucene.apache.org
Subject: Re: New "Stream closed" exception with Java 6
Are there any log messages around that spot? Did something happen to
the underlying Reader you are using? Can you share that little bit of
indexing code?
On Aug 27, 2009, at 10:11 AM, Chris Bamford w
Hi Grant
Please see attached.
Thanks,
- Chris
- Original Message -
From: Grant Ingersoll
Sent: Fri, 28/8/2009 1:26pm
To: java-user@lucene.apache.org
Subject: Re: New "Stream closed" exception with Java 6
Are there any log messages around that spot? Did something happe
Are there any log messages around that spot? Did something happen to
the underlying Reader you are using? Can you share that little bit of
indexing code?
On Aug 27, 2009, at 10:11 AM, Chris Bamford wrote:
Hi,
Since moving our app to Java 6 and Tomcat 6, we have started getting
occasion
Hi,
Since moving our app to Java 6 and Tomcat 6, we have started getting occasional
exceptions of the form:
java.io.IOException: Stream closed
at sun.nio.cs.StreamDecoder.ensureOpen(Unknown Source)
at sun.nio.cs.StreamDecoder.read(Unknown Source)
at java.io.InputStreamReader.read(Un
21 matches
Mail list logo
