Error: Invalid spaceKey on retrieving a related space config.

Setting timeout options

Use the Timeouts tab to set the timeouts for the selected server.

To set timeouts

  1. In a browser, open the AR System Administration Console, and click System > General > Server Information.
    The AR System Administration: Server Information form appears.
  2. Click the Timeouts tab.

    AR System Administration: Server Information form — Timeouts tab
    (Click the image to expand it.)
  3. Edit the options, as needed:

    Timeouts tab fields

    Area name

    Field Name

    Description

    Process Timeout (seconds)

    Prevents a server from being blocked when a process requested in a Set Fields filter or escalation action does not return a value soon enough.
    The server waits a specified interval and then returns a $NULL$ value even if the process is incomplete. The default is 5 seconds. The minimum is 1, and the maximum is 60. Specifying long intervals can increase the response time for users.

    Alert API Send Timeout (seconds)

    Sets the time limit for making contact with alert clients.
    Two attempts are made to deliver an alert and if the second attempt fails, the alert registration is removed. The default is 7 seconds.

    Filter API RPC Timeout (seconds)

    Sets the time limit (in seconds) for the Filter API RPC to respond to the server's request.
    The default is 40 seconds. The minimum is 1, and the maximum is 300.

    Floating License Timeout (hours)

    Write

    Sets a time limit for how long a floating license remains reserved if the user is not accessing AR System.
    When a user is using a floating license, a license is reserved while the user is connected to the server. If the user does not perform an AR System operation for the period of time specified in this field, the license is automatically released back to the pool of available licenses. The client tool must acquire a license for the user again when the next licensable operation occurs. The default is 2 hours. The minimum is 1, and the maximum is 99.

    Note: To ensure that all servers in a server group are notified when a user logs out or remains idle, set the Suppress-Logoff-Signals parameter in Centralized Configuration to False. If Suppress-Logoff-Signals is not added to the Centralized Configuration, add it manually. 

    Currency Ratio Cache Refresh Interval (minutes)

    Client Refresh Interval

    Sets the interval (in minutes) that clients (for example, the Web) use when refreshing currency conversion ratios stored on the server.
    This refresh action makes sure that calculations for functional currencies are up to date.

  4. Click Apply.
Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Leonard Warren

    There is not a definition entry for Email Timeout (seconds).  I take it that the default is 10 and the range is from 1 to 60 seconds???

    Also in the table field section, Alert Send Timeout (seconds) should read "Alert API Send Timeout (seconds)."

    Aug 08, 2016 01:07
    1. Prachi Kalyani

      Hello Leonard,

      Thank you for bringing this to our notice.

      The Entry Timeout field is no longer on the screen. I have updated the screenshot. Also I have updated the field name to Alert API Send Timeout.

      Thanks,

      Prachi

      Aug 09, 2016 04:59
      1. Leonard Warren

        Thanks for updating the Alert entry.

         

        However, it is the Email Timeout field that is not described in the table. You removed the item when it still appears in v9.1.  Can you put it back in on the screen and provide the definition and range options for the Email Timeout field?

        Aug 09, 2016 06:24
        1. Prachi Kalyani

          Hello Leonard,

          I got this confirmed from the SME and the Email Timeout field is not displayed for the BMC Remedy AR System version 9.1.

          If you still see the field, could you please contact BMC Customer Support to raise a formal ticket. To contact BMC Customer Support, click here.

          Thanks,

          Prachi

          Aug 09, 2016 06:54
          1. Leonard Warren

            My environment is 9.0.01 201605091238.  So it is there.  I don't recall seeing it there before in older versions.  But it is there.

            However, I do have access to another environment of 9.1.00 201607240258 and it is no longer there.  I will remove it from my snap shot to avoid confusion.  Thanks

            Aug 09, 2016 07:16
  2. Martin Penev

    Hello,

     

    Which of these timeout parameters sets the timeout for calling BMC Atrium Orchestrator processes via a Set Fields action? I have tried different settings and none of them seems to change the timeout for calling BAO processes. No matter what I do, the BAO processes always time out at 40 seconds.

     

    Best Regards,

    Martin

    Feb 27, 2017 02:24
    1. Prachi Kalyani

      Hello Martin,

      We will verify this and get back to you. 

      Thanks,

      Prachi

      Feb 27, 2017 03:33
      1. Anagha Deshpande

        Hello Martin,

        Apologies for late response.

        Could you please share the error messages that you are getting from this process?

        Regards,

        Anagha 

        Jul 28, 2017 02:27
        1. Martin Penev

          Hello,

          I do not get any error. My calls were just timing out at 40 seconds, so I thought that this is some kind of a default value that cannot be changed. However, it turned out that there is a setting for this. This setting is called "timeout" and it can be found under com.bmc.arsys.server.extension.webservice in Centralized Configuration.

          Best Regards, Martin Penev

          Aug 15, 2017 01:30
        1. Martin Penev

          Hello,

          I do not get any error. My calls were just timing out at 40 seconds, so I thought that this is some kind of a default value that cannot be changed. However, it turned out that there is a setting for this. The setting is called "timeout" and it can be found under com.bmc.arsys.server.extension.webservice in Centralized Configuration.

          Best Regards,

          Martin Penev

          Aug 15, 2017 01:31
          1. Anagha Deshpande

            Hello Martin,

            I am verifying this with the SME.

            Regards,

            Anagha 

            Aug 16, 2017 04:16
            1. Alejandro Vidaurri de la cruz

              Hello We have just tested this and AR server restart was required to make this change visible.


              Oct 11, 2017 01:41
            1. Anagha Deshpande

              Hello Martin,

              Apologies for the late response.

              Could you tell us which calls are timed out in 40 seconds?

              Regards,

              Anagha

              Jul 03, 2018 04:00
              1. Anagha Deshpande

                Hello Martin,

                Please check the value for Filter API RPC Timeout (seconds) field.

                Regards,

                Anagha

                Jul 04, 2018 12:51
  3. Shrihari Nirdude

    Unable to retrieve data from CMDB: Request info: Form name: Namespace: BMC.CORE className: BMC_PhysicalLocation datasetName: BMC.ASSET attributes: [Ljava.lang.String;@d420d42 queryString: 'ATTAssetLifecycleStatus'="Deployed" qualifierString: null [2017-08-10 03:39:38,096] 3808494 FATAL - ERROR (91): Message not in catalog; Message number = 91; ONC/RPC call timed out ERROR (91): Message not in catalog; Message number = 91; ONC/RPC call timed out at com.bmc.cmdb.api.CMDBProxyJRpcBase.convertException(Unknown Source) at com.bmc.cmdb.api.CMDBProxyJRpcBase.convertException(Unknown Source) at com.bmc.cmdb.api.CMDBProxyJRpcBase.cmdbCall(Unknown Source) at com.bmc.cmdb.api.CMDBProxyJRpcBase.cmdbCall(Unknown Source) at com.bmc.cmdb.api.CMDBProxy.CMDBGetListInstance(Unknown Source) at com.bmc.cmdb.api.CMDBProxy.CMDBGetListInstanceWithAttributes1(Unknown Source) at com.bmc.cmdb.api.CMDBInstance.findObjects(Unknown Source)

    [2017-08-10 03:39:38,101] 3808499 FATAL - Exception:runProgram() An error occurred while processing the runProgram method An error occurred while retrieveing data from CMDB ERROR (91): Message not in catalog; Message number = 91; ONC/RPC call timed out

    • An error occurred while retrieveing data from CMDB ERROR (91): Message not in catalog; Message number = 91; ONC/RPC call timed out java.lang.Exception: An error occurred while retrieveing data from CMDB ERROR (91): Message not in catalog; Message number = 91; ONC/RPC call timed out

    I'm getting above TIMOUT Exception while calling BMC AR API, can you please check on this one.

    Aug 11, 2017 04:18
    1. Anagha Deshpande

      Hello Shrihari,

      I will check this case with the SME and will write back to you.

      Regards,

      Anagha 

      Aug 16, 2017 04:14
      1. Anagha Deshpande

        Hello Shrihari,

        Please raise a support ticket because your calls are getting timed out. Click here to raise a support ticket.

        Regards,

        Anagha

        Aug 17, 2017 03:39
  4. Leonard Warren

    This sounds more like a Support Issue and not something that the documentation team can fix or research. Suggest you put in a support ticket or post it on BMC Communities to see if anyone has any information to help.

    I know that ERROR 91 is a mismatch between the client and the server's protocol definitions. The following link provides some information as to what could be happening - https://communities.bmc.com/thread/157307?start=0&tstart=0.

    Aug 11, 2017 05:49
  5. Shrihari Nirdude

    Thanks Team for your comments ... Let me create a support ticket..

    Sep 27, 2017 11:24