On Sun, Mar 1, 2009 at 5:29 PM, Alex Boisvert <[email protected]> wrote:
> How many threads do you need? How many threads do you have configured? I think more than I"m currently using ;) And I'm not sure how many are configured, I guess thats my questions, which properties do I need to set to configure the available threads? (tomcat is ok as I don't have this problem with the same BPEL on the same container but on different engines ;) ) - Cj. > > > alex > > On Sat, Feb 28, 2009 at 8:36 AM, Ciaran <[email protected]> wrote: > > > On Sat, Feb 28, 2009 at 3:37 PM, Alex Boisvert <[email protected]> > > wrote: > > > > > It's a good question. I'm guessing you're talking about persistent > > > processes and I'm also guessing that you run into some kind of deadlock > > > issue at the database level. We would need to diagnose the situation > to > > > determine which tables/rows are being locked and try to change the code > > > such > > > that we reduce contention on these tables/rows to avoid the deadlock > (if > > > possible). It's not an easy task but it's surely worthwhile. > > > > I don't think this is the case we're running in-memory, and I'm not > seeing > > deadlock errors in the db, it *appears* as though there aren't enough > > threads available to execute the nested process calls? > > -cj > > > > > > > > > > > > > alex > > > > > > > > > On Sat, Feb 28, 2009 at 12:33 AM, Ciaran <[email protected]> wrote: > > > > > > > We currently have two BPEL processes A + B, sometimes a step in A > will > > > > (in-directly, but in-process) call B via an intermediary web service > > > > invocation. Currently, it seems as though i can only call A > > successfully > > > > from two con-current loading/testing threads, as soon as I ramp it up > > to > > > 3 > > > > threads we start to get connection timeouts (very reliably, at 2 > > threads > > > we > > > > see 0 problems, after 2 threads everything other than the first 2 > > things > > > we > > > > push through fail :( ) . Now I suspect this is because I've used up > > all > > > > my > > > > available threads-of-execution and because B can't be *received* by > the > > > > engine, A times-out. I've read around the docs and mailing list and > > seen > > > > the ode.axis2.properties comments, but these don't appear to help me, > > > apart > > > > from the fact that I should probably being using correlated invokes, > > > could > > > > anyone point me in the right direction to increase the size of the > > > availble > > > > pool of threads (the THREAD_POOL_SIZE appears to be hardcode to 8, > but > > I > > > > think thats JBI not axis ? ) > > > > > > > > Many thanks, sorry if this question is entirely inane! > > > > - Cj. > > > > > > > > > >
