Hello again,
I think you are 100% right here. I managed to roll back to my patched
version of UIMA 2.1.0. In this one, I implemented the pool of threads as
automatically expandable. This seemed to solve all of our problems, and
things are chugging away very happily now.
I know this is the user group, but is this something I should look to
contributing somehow?
Thanks for the brainstorm, guys!
Steve
At 07:38 PM 4/22/2008, you wrote:
On Tue, Apr 22, 2008 at 6:51 PM, Steve Suppe <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Thanks so much for this list - I'm constantly lurking and learning things
> :)
>
> I'm having trouble with our distributed cluster - our setup is as follows:
>
> We have a 'reader' node reading from the local FS, 15 'worker' nodes each
> running identical aggregates of analysis and consumers that connect to an
> oracle DB for final storing of data results. On each worker I have
multiple
> instances running, typically 32, so I have 15x32 connections to Oracle. I
> have about 20,000,000 documents to process.
>
> After a certain amount of time, I start to get Broken Pipe server socket
> exceptions, of the following:
> <snip/>
I'm not completely sure, but this might be related to this JIRA issue:
http://issues.apache.org/jira/browse/UIMA-821. I ran into this
problem when I had a large number of clients trying to connect to a
Vinci service, just like what you're doing. The Vinci service has a
default thread pool of size 20 - if there are more clients than that,
things didn't work right. The first 20 clients hogged all the threads
and the other clients couldn't get in.
UIMA 2.2.2 will allow you to configure the server thread pool size so
this problem doesn't occur. Hopefully this release will be out soon -
it is currently up for an approval vote from the Apache Incubator.
-Adam
