1 Reply Latest reply on Mar 23, 2009 2:15 PM by davsclaus

    Pooling Camel in OSGi

    tpurcell

      Hello

       

      I have the following camel context and everything works great:

       

      <camel:camelContext>

          <camel:endpoint id="sqsConsumer"

                          uri="sqs:sqsConsumer?accessId=${aws.accessId}&amp;secretKey=${aws.secretKey}&amp;queueName=${queue.name}&amp;consumer.initialDelay=${consumer.initialDelay}&amp;consumer.delay=${consumer.delay}"/>

       

          <camel:endpoint id="jms-amq"

                          uri="activemq:queue:${jms.queue.name}"/>

       

          <camel:route id="SQS-To-AMQ">

            <camel:from id="SQS-Consumer" ref="sqsConsumer"/>

            <camel:to id="Log-Entry" uri="log:ObjectFromSQSLog"/>

            <camel:process id="Message-Processor" ref="sqsMessageProcessor"/>

            <camel:to id="Velocity-Transformer" uri="velocity:classpath:/sqsXML.vm"/>

            <camel:to id="AMQ-Destination" ref="jms-amq"/>

          </camel:route>

       

      The only problem is that it appears to run single threaded. I would like to have multiple threads running the same route. I have not been able to figure out how to do that.

       

      Message order is NOT an issue. I'm running Fuse 4.0.0.4.

       

      Thanks

      Tom