Hey Sean,
(CC'ing dev@oodt.a.o on my reply with your permission)
We are seeing this same issue in 0.5 wengine in the trunk for Apache OODT. I've
also noticed
that though it eats up 99% of the CPU, it doesn't seem to hamper the machine at
all. I think it
might have something to do with the threa
just put a configurable wait seconds between handling each workflow so the thread doesn't run amuck... we really just need to add "dirty" workflow concept... never got a chance when working on wengine-brianOn Oct 25, 2012, at 02:19 PM, "Mattmann, Chris A (388J)" wrote:Hey Sean, (CC'ing dev@oodt.a
Hey Brian,
Yep we have that in wengine in OODT 0.5 trunk right now too.
The dirty workflow concept sounds neat -- could you elaborate?
Cheers,
Chris
On Oct 25, 2012, at 2:31 PM, Brian Foster wrote:
> just put a configurable wait seconds between handling each workflow so the
> thread doesn't r
