Hi.

We installed the Command Central in our QA environment. Everything went ok.

Reading the docs, we needed to integrate another Software AG product in the same environment. So I went to /profiles/SPM/bin and I executed the “startup.sh” file.

The service started and the Command Central could monitor this SPM.

But, for an unknown reason, this SPM suddently stopped and even using the “shutdown.sh” and then “startup.sh” he doesn’t go up again. The Command Central can’t monitor this SPM anymore.

Please, what should I do to fix this?

In our logs, this information repeats:

“jvm 1 | 2019/08/07 09:16:46 DEBUG # NirvanaRuntimeStateProvider NirvanaRuntimeStateProvider.getQueuedTaksKPI() high watermark queued tasks max value is: 100
jvm 1 | 2019/08/07 09:16:46 DEBUG # BasicMonitoringServiceImpl Runtimate State SPI not found: No available implementation for TaskEngineRuntime-default.
jvm 1 | 2019/08/07 09:16:46 DEBUG # CommonRuntimeMonitor Getting runtime status for OSGI-IS_default-WmJDBCAdapter.
jvm 1 | 2019/08/07 09:16:46 DEBUG # JMXUtil Querying a subsystem for name “com.softwareag:type=subsystem,*,name=webMethods Adapter for JDBC,subsystemId=WmJDBCAdapter”.
jvm 1 | 2019/08/07 09:16:46 DEBUG # JMXUtil Found a subsystem for runtime component with id OSGI-IS_default-WmJDBCAdapter.
jvm 1 | 2019/08/07 09:16:46 DEBUG # CommonRuntimeMonitor The runtime status of OSGI-IS_default-WmJDBCAdapter is ONLINE.
jvm 1 | 2019/08/07 09:16:46 DEBUG # BasicMonitoringServiceImpl Runtimate State SPI not found: No available implementation for OSGI-IS_default-WmJDBCAdapter.”

Hi again.

I solved the problem.

I reinstalled the Command Central and then I recreated the connection with our other Software AG Installation and it worked.