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 Needs more information
Workspace WebSphere Liberty
Created by Guest
Created on Apr 16, 2026

Graceful pause of CICS liberty port to prevent transaction loss

When a CICS liberty port was paused, we found that some API transactions are abended.  We understand that when the port was paused, the TCP listener stops accepting NEW connections immediately. The channel destruction happens quickly which means that the server couldn't send response back.

During CICS and JVMSERVER shutdown, the jvmserver coordinate a shutdown that waits for active requests to complete before stopping so no transactions will be lost.

We would like the CICS liberty port pause action has the same coordination as jvmserver shutdown and ensure the transactions that enter to the jvmserver was processed successfully. We want to avoid transaction loss during port pause process.

Idea priority High
  • Admin
    Jahnvi Bedia
    Jul 23, 2026

    Hi, thanks for submitting your idea with us. We would suggest working with a workaround solution on this request.
    The suggested workaround solution is to configure a second, separate endpoint exclusively for the JMX REST connector.

    This will help to have the JMX pause request runs on its own independent channel that is completely isolated from defaultHttpEndpoint. which they are trying to pause.
    If they have separate JMX endpoint, through which they can send the "Pause" JMX request to pause the defaultHttpEndpoint, the server make sure all the requests are completed and will complete the pause. They will no longer see the Exception that they were seeing previously.

    Sample Server Configuration:
    Add the following to your server.xml:

    <!-- Your existing application endpoint (unchanged) -->
    
    <httpEndpoint id="defaultHttpEndpoint"
    httpPort="9080"
    httpsPort="9443"
    host="*"/>

    <!-- NEW: dedicated management endpoint for JMX only -->
    <httpEndpoint id="managementHttpEndpoint"
    httpPort="-1" <!-- no plain HTTP -->
    httpsPort="9444" <!-- HTTPS only -->
    host="127.0.0.1"/> <!-- Set this to the host which originates the JMX Pause call -->

    <!-- Bind the JMX REST connector to the management endpoint -->
    <restConnector id="managementConnector"
    httpsPort="9444"/>
  • Guest
    Apr 16, 2026

    The Liberty support team requested in the referenced case that this idea get raised.

    This idea is being transferred from CICS Transaction Server to WebSphere Liberty.