You need to increase the number of threads available to the component in the thread pool configuration.
On 7/26/07, Arif Mohd <[EMAIL PROTECTED]> wrote:
Hi, Iam having n number of components deployed as SA's, each component will be directing the message to drools SA where the routing logic is there. My component setup is as follows component1-->drools-->component2-->drools-->component3-->drools-->component4-->drools-->component5-->drools-->component6-->drools-->component7 The problem is the message is not reaching to component7(i.e, if drools is invoked more than 5 times in a message flow) it will just hang up. if i make sure that drools is not invoked more than 5 times in a single message flow it will work i.e it will work with following setups 1) component1-->component2-->drools-->component3-->drools-->component4-->drools-->component5-->drools-->component6-->drools-->component7 2) component1-->drools-->component2-->component3-->drools-->component4-->drools-->component5-->drools-->component6-->drools-->component7 3) component1-->drools-->component2-->drools-->component3-->component4-->drools-->component5-->drools-->component6-->drools-->component7 4) component1-->drools-->component2-->drools-->component3-->drools-->component4--> component5-->drools-->component6-->drools-->component7 I tried with all the combination it works fine, provided drools is not invoked more than 5 times In the above setup drools is deployed as a SA(service:myDrools), each coponents target is given as myDrools Am i doing any thing wrong? Please some body help me out. -- View this message in context: http://www.nabble.com/is-this-a-drools-limitation--tf4151352s12049.html#a11809604 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Principal Engineer, IONA Blog: http://gnodet.blogspot.com/
