On Jan 7, 2011, at 16:03, dar...@ontrenet.com wrote:
Not really because each thread is a worker that stays alive and
iterates
over work items.
How does that prevent threads from being pooled and reused ? When a
worker is done, it goes back to the pool, ready to be reused. Anyway,
that w
Not really because each thread is a worker that stays alive and iterates
over work items. The fatality seems to happen when they all are using the
index (lucene is supposed to be multi-read threadsafe).
It does it without the detach, but when the detach is in there it fatals
_on_ the detach. wierd
On Jan 7, 2011, at 15:36, Darren Govoni wrote:
That's a good thought.
I just wish I knew how to interpret the JVM fatal error. I rarely
ever see them working with straight java,
so I'm also wondering if something else is at play. Its pretty
predicatable when it happens.
Like at either a
That's a good thought.
I just wish I knew how to interpret the JVM fatal error. I rarely ever
see them working with straight java,
so I'm also wondering if something else is at play. Its pretty
predicatable when it happens.
Like at either a vm.detachCurrentThread or perhaps when an object
atta
On Fri, 7 Jan 2011, Darren Govoni wrote:
I'll try that and report.
It seems to happen when many threads are attached at once and the CPU
throttles.
Maybe some GC settings could also help work around this ?
Andi..
On 01/06/2011 09:42 PM, Andi Vajda wrote:
On Thu, 6 Jan 2011, Darren Gov
I'll try that and report.
It seems to happen when many threads are attached at once and the CPU
throttles.
On 01/06/2011 09:42 PM, Andi Vajda wrote:
On Thu, 6 Jan 2011, Darren Govoni wrote:
Hi,
I am getting these JVM fatal errors:
#
# A fatal error has been detected by the Java Runtime E
