The stack trace indicates that all threads are waiting on this condition, but there are no threads which could unset the condition. So it's clearly a real lockup. I've opened a ticket: CONNECTORS-872.
The real question now is why the tests don't demonstrate this failure mode. It is possible that the web connector code is using the throttle service in an incorrect way. I'll have to do some analysis to come up with a hypothesis. Meanwhile, RC5 voting is canceled. Karl On Wed, Jan 29, 2014 at 9:57 AM, Karl Wright <[email protected]> wrote: > Thanks - this shows that threads are all waiting on connection > throttling. How many simultaneous connections did you make available to > the site you are crawling, and can you look at the simple history report to > confirm that there is no activity? I'll dig further through your stack > trace while I await your answer. > > Karl > > > On Wed, Jan 29, 2014 at 9:51 AM, Erlend Garåsen > <[email protected]>wrote: > >> On 1/29/14 3:41 PM, Karl Wright wrote: >> >> Can you get a thread dump from your agents process? >>> >> >> http://folk.uio.no/erlendfg/manifoldcf/threaddump_agent.txt >> >> >
