Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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 (

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

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

IBM Employees should enter Ideas at

Status Delivered
Workspace Spectrum Symphony
Components Version 7.3.2
Created by Guest
Created on Mar 11, 2024

SSM restart by SD

Use case: we should ask SD try to restart SSM should it detect non-responsive SSM after a certain time of period (or after tried a number of times). Not only after detecting SSM's PID is gone or the underlying network connection is broken.

The length of the waiting time or the number of times it should try (and the waiting time between the tries) should be tunables which user can customize according to own situation.

Also after the waiting time expires or the number of re-tries exhausted, SD should log a final error and ask for Admin intervention. Business justification: I have made some further research and discussed with the team. It has been found out it is only the following 2 conditions will trigger SD to failover (restart) SSM. I have also tested the conditions in a test cluster in which both situations SSM was restarted.

Previous SSM pid disappeared Physical network connection to SSM from SD broke at TCP connection level In our case here, for the following error message we see: [...] It was the API connection from SD to SSM querying information failed. However, the TCP connection is still alive. This is very much likely to be the case why the error message reported by SSM was not restarted by SD.

it should be the SD's responsibility to detect whether to restart SSM and under what circumstances. So far we've found SD will only do this for broken connection or missing SSM PID. It must have been designed this way for a reason in the first place. We might need your help to log an RFE if you think there are some situation you would like SD to have SSM restarted.

Needed By Quarter