Hi Have you tried without the WorkManager? Just to see if you can use more routes without it? At least then we have a hint that the WM is causing issues with Camel.
What kind of routes and components are you using? Which version of Camel are you using? What happens when it refuses to start? Nothing is logged and it just hangs? Or what? On Tue, Dec 30, 2008 at 3:21 PM, Nol <a.de....@dnb.nl> wrote: > > Hi All, > > We are trying to get a simple test application running on IBM WS 6.1, but > without luck if our routebuilder contains more than say 6 routes. > > Somehow we have got the feeling this is a thread issue. For that reason > we've modify all thread pool values we find in WS Admin Console (increase > all min and max values). > > In our aplicationContext we have: > > <bean id="taskExecutor" > class="org.springframework.scheduling.commonj.WorkManagerTaskExecutor" > > <property name="workManagerName" value="java:comp/env/WorkManagerAVB" /> > <property name="resourceRef" value="true" /> > </bean> > > Our threadpool named "Default" should contain between 5 and 40 threads. > However when debugging the application only 10 threads of name > "WorkManager.DefaultWorkManager..." show up. > > When we start our application with a reduced number of routes everything > works fine. > However when we increase the number above a certain threshold the server > refuses to start up. > > Thanks, > Nol > > -- > View this message in context: > http://www.nabble.com/threads-in-WS-using-spring-camel-and-multiple-routes-tp21217763s22882p21217763.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- /Claus Ibsen Apache Camel Committer Blog: http://davsclaus.blogspot.com/