This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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
Post 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
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.
IBM Employees should enter Ideas at https://ideas.ibm.com
See this idea on ideas.ibm.com
Customer largest production cluster PG1 had an incident on March 13. PG1 span over 2 ~ 3 DCs. There was a network failure between two DCs in the morning. VEMKD and SSM were running at different DCs. Customer tried to disable the app so they can restart SSM at a different management host. The action failed because SD was in process disabling SSM. SSM process was not terminated for many hours until they contact IBM. Support asked them to kill the process and then SSM could be started at another host, workload was then able to resume.
The incident was caused by network failure. But one request from customer is to enhance the feature to forcefully terminating lingering SSM and restarting on another management host.
There is a app profile parameter to do similar things. But if SSM process was hanging (for example, kill -STOP pid), EGO cannot terminate the process actually.
shutDownTimeout
Description: Number of seconds to wait for the session manager to shut down before the session director considers it as timed out and restarts the session manager.
The session manager should shut down within the timeout period when the related application is unregistered or disabled.
Where used: SOAM > SSM
Required or optional: Optional
Valid values: 1 to 4294967295
Default value: 300
Need enhancement to forcefully terminate lingering SSM and restart on another management host regardless of current SSM process state.
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
.Information has been provided, to close the RFE request.
.Information has been provided and agreed to close this request.