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 for resolution.

For more information about IBM's Ideas program visit

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