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:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive a notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to email@example.com for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
RPT should not report Dropped Connections as Server Timeouts -- a new Error Condition "Dropped Connection" is needed
A new Error Condition "Dropped Connection" or "Connection Forcibly Closed" needs to be created to account for cases where the System Under Test drops a connection before the configured Server Timeout value. E.g. for cases such as:
"java.io.IOException: An existing connection was forcibly closed by the remote host"
Note that this refers to the Timeout set in either the Test (HTTP Options - Timeout) or in an individual Request within the Test (Request - Advanced - Timeout - Override timeout value).
Currently, this condition is reported as a Server Timeout -- which is incorrect. It should be reported separately, and none of the existing Error Conditions is appropriate. There also need to be an entry in all the Error Handling areas.
* Server Timeout (HTTP Options - Timeout) is set in all of our Tests to 240 seconds.
* We run a Schedule that includes these Tests.
* During the run, the System Under Test sometimes drops connections after 160 seconds.
The Execution Report shows these as Server Timeouts, but we need to be able to tell our system team the difference between when they are dropping connections and when the test has given up.
Do not place IBM confidential, company confidential, or personal information into any field.