Skip to Main Content
Cloud Platform

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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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 ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Planned for future release
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
    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