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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
Inbound HTTP requests are accepted on the listener despite the Int. Server in a stopping state. See Case TS010520197 for details of a user case for wanting to limit the inbound requests once we know the flow/server is stopping.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Idea Review. Thank you for taking the time to raise this idea which we agree would bring value to the product. Whilst updating the status to Future Consideration we note that this area is not currently a business priority for us but we'd be open to feedback from the community to help us determine what level of support there would be for this improvement. In terms of functional implementation, whilst not straight forward (due to complications arising from multiple flows sharing the same in-memory queue), it would be possible to implement, as the in memory queue used by the listener could continue to be drained before the listener is shut down, even though the listener is told to not accept new workload in the interim.