Our Active Essbase server has started seeing a high activity of lease manager renewals requests (every 15 seconds). In an effort to try to see if our Passive Essbase server was the root cause, we shut down OPMN on the passive and the issue still remains on our active server. We do have a split environment whereby our Essbaser servers reside on 2 Linux boxes and the rest of our EPM suite (Planning, HFM, shared services, etc) reside on 2 Windows VMs. From what I understand, the lease manager configuration works in conjunction with weblogics, but that's second hand knowledge passed on to me.
Example of the spam we are seeing in the lease manager log:
[2019-05-28T17:07:14.887-07:00] [ESSBASE0] [NOTIFICATION:16] [LM-60] [LM] [ecid: 1559085162137,0] [tid: 140452126250752] [15]sec is the time taken for [Wait-for-Lease-renewal] operation.
[2019-05-28T17:07:14.887-07:00] [ESSBASE0] [NOTIFICATION:16] [LM-61] [LM] [ecid: 1559085162137,0] [tid: 140452126250752] Going to call [Lease-renewal] operation.
[2019-05-28T17:07:14.889-07:00] [ESSBASE0] [NOTIFICATION:16] [LM-27] [LM] [ecid: 1559085162137,0] [tid: 140452126250752] Lease manager has a current lease.
[2019-05-28T17:07:14.890-07:00] [ESSBASE0] [NOTIFICATION:16] [LM-60] [LM] [ecid: 1559085162137,0] [tid: 140452126250752] [0]sec is the time taken for [Lease-renewal] operation.
[2019-05-28T17:07:14.890-07:00] [ESSBASE0] [NOTIFICATION:16] [LM-7] [LM] [ecid: 1559085162137,0] [tid: 140452126250752] Lease Manager successfully acquired/renewed its lease.
[2019-05-28T17:07:14.890-07:00] [ESSBASE0] [NOTIFICATION:16] [LM-61] [LM] [ecid: 1559085162137,0] [tid: 140452126250752] Going to call [Wait-for-Lease-renewal] operation.
I'm trying to identify where this request is originating from to hunt from there, but I'm not familiar enough with the lease manager configuration to identify where to look beyond the essbase.cfg and log files.
Does anyone have any good input on where I can point myself to hunt down this issue?