Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management and AIOps products. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
  • Cloud Pak for Multicloud Management

  • Cloud Pak for Network Automation - including Orchestration and Performance Management

  • Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio

  • Edge Application Manager

  • IBM Observability with Instana

  • IBM Turbonomic ARM

  • Instana

  • ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8

  • Workload Automation - including Workload Scheduler

  • Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)

  • Tivoli Application Dependency Discovery Manager - TADDM


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.


Status Is a defect
Created by Guest
Created on Sep 19, 2021

In case of Timeout JRExecAction is retrying to execute the command. We need to disable Retry behavior

Dear IBM Support Team, Please find below description about the scenario we have executed in IBM Tivoli Netcool/Impact 7.1 1) We executed below code in our Impact Policy and our observation from nci_jrexec.log file is, when Timeout occurs (based on configured Timeout value), it's retrying again the same operation again that is defined in the parameter/argument "Command_To_Fire". Sample Policy Code TimeOut = 4; JRExecActionResult = JRExecAction(Script_To_Run, Command_To_Fire, false, TimeOut); 2) Script_To_Run is a shell script that does SSH connection to Customer HPNA Custom Linux Appliance Server. Command to execute on Customer server is passed to the script in the parameter Command_To_Fire 3) After triggering the Command_To_Fire, if Timeout occurs we are receiving below error message in Impact Policy Log 08 Sep 2021 00:26:15,240: [Ngen_Framework_Alarm_Notif_CIC][MessageProcessor-Dog#4756]!(Module: Log): 0 ms 08 Sep 2021 00:26:23,352: [Ngen_Framework_Alarm_Notif_CIC][MessageProcessor-Dog#4756]Parser log: LangException ERROR: Exception in policy: RunRemoteCommand at line: 183.JRExecAction: Error while executing external action {/home/netcool/ssh_hpna_connect_failover.sh, deploy change plan -ip 192.168.96.112 -name "Cisco_S ingle_Homed_Device_ReportV2" -parameters "" -variables "stc_inputhosts=RTPE1-Khu-107-3\nCoreNCS-Maa-108-1,stc_ticket_num=PR00022535653" -comment "Auto task by netcool" -priority 1 -postsnapshot false} ExceptionMessage: com.micromuse.common.parser.PolicyException: JRExecAction: Error while executing external action { /home/netcool/ssh_hpna_connect_failover.sh, deploy change plan -ip 192.168.96.112 -name "Cisco_Single_Homed_Device_ReportV2" -parameters "" -variables "stc_inp uthosts=RTPE1-Khu-107-3\nCoreNCS-Maa-108-1,stc_ticket_num=PR00022535653" -comment "Auto task by netcool" -priority 1 -postsnapshot false}. getCause: java.rmi. ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.RemoteException: External command did not return within 4 seconds. Edit the Timeout value in the policy to change this value.; nested exceptio n is: java.util.concurrent.TimeoutException 4) In nci_jrexec.log file we are receiving error message representing the Timeout behavior 09 Sep 2021 10:40:19,037 ERROR [JRExecServer] External command did not return within 4 seconds. Edit the Timeout value in the policy to change this value. java.util.concurrent.TimeoutException: null 5) After Timeout, same command in "Command_To_Fire" gets triggered again. This is against to what we need. Requirement is stop/disable retry behavior in case of timeout. Note: Kindly provide a configurable way to stop/disable retry behavior in case of Timeout while using JRExecAction .
Idea priority Urgent