Return
-
Title
Job service stops working when application server is used for database connectivity -
Description
Two Application Servers are used behind a Load Balancer with Cookie Session Stickiness configured on Load Balancer. The Application Server uses the same Session Token Certificate. Two Job Servers are installed on different machines. These Job Servers work for five minutes and then throw an error:
"[2538001] Error requesting queue \RemoteJobServer1."
"[810321] Your session has expired. Log on again."
When the services are restarted they work again for three to four minutes and after that the same error is thrown again.
The session timeout on the local IIS instance is configured to 60 minutes and for the Load Balancer the default timeout value (60 seconds) is used.
The Job servers don't use a direct connection to the One Identity Manager (1IM) Database. The connection is created via the Load Balancer URL and is used as an indirect Application Server connection. -
Cause
The default timeout value for the Load Balancer (60 seconds) is too small (as configured in IIS).
-
Resolution
Change the timeout values for the IIS to the default value (20 minutes), if possible.
The interval for the Job Calls is configured in Jobservice.cfg (the job service configuration) and the default value is 90 seconds. Timeout values shouldn't be less then this default value.
Change the timeout value for the Load Balancer to at least 90 seconds.