Hi Tech Community members, I need some assistance in figuring out the Command Central v9.9 error I am receiving while trying to Start/Stop an Integration Server Instance v9.9 from the CC GUI. I am able Pause/Resume the IS instance after configuring the Quiesce Port. I am not sure if there any other configurations that need to be done to perform these lifecycle operations.

CC GUI Error, when trying to Stop the IS:
“RuntimeException: Error occured while executing lifecycle operation on a remote managed node with alias uslx432. Remote task status is [SPMLCCE0001] Runtime component “integrationServer-default” does not support life cycle oper[b]ation “STOP”. >> UnsupportedOperationException: No ‘stop’ implementation is available for category:ENGINE”

Wrapper Log Entry for this Error:

INFO | jvm 1 | 2016/03/22 14:30:04 | 2016-03-22 14:30:04.406 EDT (com.softwareag.platform.management. … .JobImpl ) [SPM.JobImpl.SPMJOBE0003] ERROR: Job 2 failed!
INFO | jvm 1 | 2016/03/22 14:30:04 | 2016-03-22 14:30:04.406 EDT (com.softwareag.platform.management. … .JobImpl ) [SPM.JobImpl.SPMJOBE0003] ERROR: com.softwareag.platform.management.common.exceptions.PlatformManagerException: Runtime component “integrationServer-default” does not support life cycle operation “STOP”.
INFO | jvm 1 | 2016/03/22 14:30:04 | 2016-03-22 14:30:04.406 EDT (com.softwareag.platform.management. … .JobImpl ) [SPM.JobImpl.SPMJOBE0003] ERROR: at com.softwareag.platform.management.lifecycleoperations.impl.BaseLifecycleOperationsService$LifecycleOperationsRunnable.call(BaseLifecycleOperationsService.java:100)
INFO | jvm 1 | 2016/03/22 14:30:04 | 2016-03-22 14:30:04.406 EDT (com.softwareag.platform.management. … .JobImpl ) [SPM.JobImpl.SPMJOBE0003] ERROR: wraps: java.lang.UnsupportedOperationException: No ‘stop’ implementation is available for category:ENGINE
INFO | jvm 1 | 2016/03/22 14:30:04 | at com.softwareag.platform.management.is.lifecycle.impl.LifecycleOperationsImpl.stop(LifecycleOperationsImpl.java:78)
INFO | jvm 1 | 2016/03/22 14:30:04 | at com.softwareag.platform.management.lifecycleoperations.impl.BaseLifecycleOperationsService$LifecycleOperationsRunnable.call(BaseLifecycleOperationsService.java:90)
INFO | jvm 1 | 2016/03/22 14:30:04 | at com.softwareag.platform.management.lifecycleoperations.impl.BaseLifecycleOperationsService$LifecycleOperationsRunnable.call(BaseLifecycleOperationsService.java:53)
INFO | jvm 1 | 2016/03/22 14:30:04 | at com.softwareag.platform.management.jobmanager.impl.JobCallableWrapper.call(JobCallableWrapper.java:27)
INFO | jvm 1 | 2016/03/22 14:30:04 | at java.util.concurrent.FutureTask.run(FutureTask.java:266)
INFO | jvm 1 | 2016/03/22 14:30:04 | at com.softwareag.platform.management.jobmanager.impl.JobImpl.run(JobImpl.java:96)
INFO | jvm 1 | 2016/03/22 14:30:04 | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
INFO | jvm 1 | 2016/03/22 14:30:04 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
INFO | jvm 1 | 2016/03/22 14:30:04 | at java.lang.Thread.run(Thread.java:745)

Any help is appreciated, thanks in advance

Check below points:

1> Make sure you have the latest fix levels installed on IS and CC
2> Check the status of SPM

http://SPMIP:SPMPort/spm/monitoring/state/

3> Since its a new version 9.9 I assume there might be less customers using this version and most of them would not have encountered this issue (at-least me )

4> Did you contact SAG support?

Thanks for the reply Mahesh. Yes I did apply the latest fixes on IS and CC, but still see this issue.

I have already checked the status of the SPM and its working fine, infact I can perform the stop/start action on the IS instance from http://SPMIP:SPMPort/spm/inventory/components/integrationServer-default successfully.

I think it’s something that needs to do with the CommandCentral. I haven’t reached out to SAG yet, I was just trying to reach out in the techcommunity and see if anyone else is seeing the same error.

This component represents Integration Server running within OSGi container and it does not support STOP or START operation independently from the parent container (JVM).
You need to STOP/START/RESTART parent OSGI-IS_default component instead which will affect not just Integration Server component but all other components running in the same JVM.

IntegrationServer itself supports PAUSE/RESUME operations which translate into Quiesce Mode on/off action on IS.

Hi Sergei,

Thank you very much for the response. Your suggestion works, I am able to perform the lifecycle operations on the OSGI-IS_default component.

Thanks

Ram