Re: understanding SEDA and Thread processor

2009-02-05 Thread Doug Douglass
Thanks Roman for the JIRA link.

My question initially came from experimenting with trying to provide
multiple threads around the http component to increase throughput. I admit
I'm having some general confusion trying to get the thread processor to
behave the way I think it should. Since I was attempting a premature
performance optimization for my project, I've since removed the thread
processor, but may need to revisit after observing the system with real
world loads.

Cheers,
Doug

On Wed, Feb 4, 2009 at 9:35 AM, Roman Kalukiewicz 
roman.kalukiew...@gmail.com wrote:

 2009/2/3 huntc hu...@mac.com:
 
  I think that what you're looking for is something akin to the
  concurrentConsumers parameter for a JMS endpoint.

  My recommendation is to raise a JIRA request for an enhancement so that
 the
  SEDA endpoint can receive a concurrentConsumers parameter. After all
 seems
  to me that using SEDA is a poor-mans JMS endpoint.

 I even created such a JIRA:

 https://issues.apache.org/activemq/browse/CAMEL-1297

 In fact it is almost done, but I have to access a box that I was
 working on to commit this thing ;)

 Roman



Re: understanding SEDA and Thread processor

2009-02-04 Thread Roman Kalukiewicz
2009/2/3 huntc hu...@mac.com:

 I think that what you're looking for is something akin to the
 concurrentConsumers parameter for a JMS endpoint.

 My recommendation is to raise a JIRA request for an enhancement so that the
 SEDA endpoint can receive a concurrentConsumers parameter. After all seems
 to me that using SEDA is a poor-mans JMS endpoint.

I even created such a JIRA:

https://issues.apache.org/activemq/browse/CAMEL-1297

In fact it is almost done, but I have to access a box that I was
working on to commit this thing ;)

Roman


Re: understanding SEDA and Thread processor

2009-02-03 Thread huntc

I think that what you're looking for is something akin to the
concurrentConsumers parameter for a JMS endpoint.

My recommendation is to raise a JIRA request for an enhancement so that the
SEDA endpoint can receive a concurrentConsumers parameter. After all seems
to me that using SEDA is a poor-mans JMS endpoint.

Anyone agree/disagree?
-- 
View this message in context: 
http://www.nabble.com/understanding-SEDA-and-Thread-processor-tp21612576s22882p21817985.html
Sent from the Camel - Users mailing list archive at Nabble.com.