Integration
This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Idea / RFE Review. Apologies for the length of time this idea has been in the status of Uncommitted Candidate / Future Consideration. The AggregateReply node does not have a node property to provide additional instances for dealing with completed aggregations ... although the existing operational model for this node provides a performance optimization which causes the same thread which delivers the final message which completes the aggregation to then be used to carry the aggregated data downstream to later nodes downstream in the flow. This means that if there are multiple aggregations in flight, being closed all at once, they will naturally all have their own threads (coming from the last arriving message in each aggregation) so can be handled in parallel. We also have the Aggregation policy type which has a property controlling the "Number of timeout threads" which causes a separate sweeper thread pool to be assigned. Unfortunately the Collector node doesn't have the equivalent policy setting, and in any case this is currently a polocy property rather than a property on the message flow node itself. Given this slight difference with the stated aim we feel the suggestion should remain open at this review, but note that there has not been high demand in this area recently, which potentially could be due to the emergence of the newer Group nodes (which use in-memory queues rather than MQ for state storage). Status maintained for now as Future Consideration.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Connectivity and Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB
Agreed - thanks for raising. We accept that allowing more control over the configuration of the event-driven architecture nodes is desirable for high volume scenarios.