-
Sep 15th, 2008, 09:47 AM
#1
Threading behavior and configuration in SI
My original posting from Friday seems to have vanished, so here it goes again.
I am trying to find out how to configure the maximum number of threads for the Spring Integration (SI) message-bus.
Specifically, what is the default number of pooled threads used by the message bus and how do I configure the max number of threads spawned by SI?
One of our teammates has the following question:
If you put a hundred messages on a queue (via an SI channel) does SI spawn a hundred threads to process them or do they handle them sequentially or does it create a number of threads up to the default setting and process that way?
Thanks!
-
Sep 17th, 2008, 07:39 AM
#2
You can define a TaskExecutor bean and give it as a reference to the <poller/> element. If you reuse the same taskExecutor everywhere controlling the number of total threads is trivial.
To answer you team mate's question: I don't know the exact default from the top of my head. But if you want to can create a TaskExecutor that does it the exact way you like.
What would be the way you expect SI to behave by default?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules