On Thu, Nov 27, 2008 at 12:06 PM, Vineesh Thomas <[EMAIL PROTECTED]> wrote:
> > Hi, > > I tried executing my bpel (with 3 parallel flows) with the latest version > of > ODE 1.2. As I mentioned it earlier I am using it as a webapp. > > I am consistently getting the following exception : > "java.lang.RuntimeException: java.lang.IllegalArgumentException: No such > channel" followed by some id. > (complete stacktrace attached with the mail) > http://www.nabble.com/file/p20724657/stacktrace.txt stacktrace.txt > I would have to see your process and try to reproduce. > > Sometimes I also get a deadlock exception (am using internal derby db). Is > the usage of an external DB recommended? Also do I need to do any extra > configurations for the setting up adn using an external DB for ODE instead > of Derby? > Yeah, Derby is intended as a testing database, it makes early experimentation with ODE easier. But for concurrent use I would definitely recommend switching to MySQL for example. Derby is just too pessimistic in its locking to be of any use under even minimal load. Cheers, Matthieu > > Can you please help me sort this issue. > > > Alex Boisvert-3 wrote: > > > > On Thu, Nov 20, 2008 at 8:51 AM, Vineesh Thomas <[EMAIL PROTECTED]> > > wrote: > > > >> > >> Is there any preconfigured thread pool size in ODE ? If so where can I > >> change > >> it ? Probably it is because of that. > > > > > > There are 2 important thread pools, > > > > 1. your appserver's (which injects request via HTTP, and other > > transport > > listeners) > > 2. the internal scheduler thread pool, configured using the > > ode-axis2.threads.pool.size property in ode-axis2.properties (default > > is > > unbounded) > > > > alex > > > > > > -- > View this message in context: > http://www.nabble.com/Trouble-with-flows...-tp20575751p20724657.html > Sent from the Apache Ode Dev mailing list archive at Nabble.com. > >
