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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Planned for future release
Categories Performance Tester
Created by Guest
Created on Aug 30, 2019

need enhanced error messaging for not able to bind to agent port in RPT

when RPT is configured to listen to an agent, say default port 7080, and another instance of RPT is running and also configured to accept connections on the same port say 7080 (default), then when the second instance of RPT is started it won't be able to bind to port 7080 because it's in use.

There's a cryptic error message in the Error log but the Error log isn't part of the default Performance Test perspective.

The user will assume the agent is in contact because maybe it was working OK before, then launch a schedule.

They'll get an error that agent can't be contacted or the launch will just hang. This results in a support ticket being opened.

Idea priority Medium
RFE ID 135938
RFE Product Rational Performance Tester
  • Guest
    Aug 1, 2022

    The feature that is described in this request is a candidate for a future release

  • Guest
    Mar 30, 2021

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

  • Guest
    Oct 29, 2019

    A preliminary evaluation of this request indicates that it is consistent with our business strategy. Further evaluation of this RFE is underway.

  • Guest
    Sep 4, 2019

    more I think about this the more I'm convinced this check should be done when RPT starts just like it
    checks for a license and gives a going into starter edition mode warning.

    Something like:

    "Not able to bind to the agent listener port 7080. Another process is listening on port 7080. This means agent status will fail and no agents will be usable in a schedule. To resolve the issue use a different port in Windows -> Preferences -> Test -> Server and configure the majordomo.config to use that port"

    If wanted to be more specific, the other process can be identified if it's RPT if the request
    http://localhost:7080/Hello returns a 200

  • Guest
    Aug 30, 2019

    Attachment (Description)

  • Guest
    Aug 30, 2019

    Attachment (Description)