Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.


Status Not under consideration
Categories Performance Tester
Created by Guest
Created on Jun 24, 2019

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.

Idea priority High
RFE ID 134089
RFE URL
RFE Product Rational Performance Tester
  • Guest
    Aug 1, 2022

    As part of the review process, we strive to be transparent about our intentions with each enhancement suggestion. The offering team has carefully reviewed this idea and has decided that it does not fit into our current plans, so the idea will be closed. The idea will be kept in IBM's ideas repository and may still be voted on. It might be reassessed or reopened for additional feedback in the future. We value your feedback and thank you for allowing us the privilege of partnering with you in developing our products.

  • Guest
    Jul 17, 2020

    Has there been any progress on this request?

  • Guest
    Jul 24, 2019

    The feature that is described in this request based on the updated description is a candidate for a future release.

  • Guest
    Jun 27, 2019

    Looks like we really need three new Error Conditions:
    * Connection Timeout
    * Server Request Failure
    * Dropped Connection

    And contrary to the original RFE description, Dropped Connection should be associated with "unexpectedly closed", but NOT be associated with "forcibly closed".

    This is due to the latest comments in the associated Case. Here's a summary:

    1) Connection Failure is reported when the socket-level connection gets no response from the Server within 25 seconds and is logged as:
    a) Connection timed out: no further information

    2) Server Timeout is reported after the connection has been made, but the server closes the connection without any response, and one of the following is logged:
    a) Unable to successfully establish a connection to web-server
    b) An existing connection was forcibly closed by the remote host

    3) Server Timeout is reported when the server closes the connection after sending a partial response:
    a) unexpectedly closed the connection while in the process of retrieving

    It would seem that the sequence of potential failures should have the following Error Conditions reported as follows:

    * 1.a is really a "Connection Timeout" since that's what's logged (this would require a new Error Condition, or rename Connection Failure)
    * 2.a is really a "Server Request Failure" not a Server Timeout (this would require a new Error Condition)
    * 2.b is really a "Server Request Failure" not a Server Timeout (this would require a new Error Condition)
    * 3.a is really a "Dropped Connection" not a Server Timeout (this would require a new Error Condition)
    * A "Server Timeout" should only be reported when the server does not complete transmission of the response before RPT gives up due to the value set in either the Test (HTTP Options - Timeout) or in an individual Request within the Test (Request - Advanced - Timeout - Override timeout value).

    A "Server Request Failure" could instead be named "Server Response Failure", but "Request" makes more sense since it seems like it's the "Request" that failed.

    Do I need a new RFE, or can someone update this one?

  • Guest
    Jun 27, 2019

    Testing