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
Workspace WebSphere Liberty
Created by Guest
Created on Oct 7, 2018

Kill on WLP client command should be propagated downstream

Often JEE application clients are used as a gateway between other applications and Liberty (e.g. transforming a proprietary TCP-based protocol into EJB calls).

To start the client the "run" command is being used. When using the "run" command two processes are started (the "client"-command process and a "java" child process that runs the actual code).

There is no "stop/force stop" option available on the client command. Therefore a typical solution is to implement a wrapper script (that calls the client command and stores the process id (pid))) to provide some structured stop possibility to the operations team.

When a kill is being sent to the "client" - process the "java" child process is not being terminated, so the "kill"-signal does not seem to be propagated to the "java" child process from the "client"-command process.

Idea priority High
RFE ID 125677
RFE URL
RFE Product WebSphere Application Server
  • Admin
    Graham Charters
    Aug 27, 2021

    Closing as raiser in not in a position to confirm the issue remains.

  • Admin
    Graham Charters
    Jul 20, 2021

    In our testing, killing the server script causes the server process to also be killed. Could you provide more information that might help us identify the issue and evaluate the request. Many thanks.