[midPoint-git] [Evolveum/midpoint] d327aa: Fix CacheCounterManager memleak (MID-6343)

[mederly]

  Branch: refs/heads/support-4.0
  Home:   https://github.com/Evolveum/midpoint
  Commit: d327aade9d84880a5f1f904591fd1296998ffd0e
      https://github.com/Evolveum/midpoint/commit/d327aade9d84880a5f1f904591fd1296998ffd0e
  Author: Pavol Mederly <mederly at evolveum.com>
  Date:   2020-06-23 (Tue, 23 Jun 2020)

  Changed paths:
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/projector/policy/PolicyRuleSuspendTaskExecutor.java
    M repo/repo-api/src/main/java/com/evolveum/midpoint/repo/api/CounterSpecification.java
    M repo/task-quartz-impl/src/main/java/com/evolveum/midpoint/task/quartzimpl/TaskManagerQuartzImpl.java
    M repo/task-quartz-impl/src/main/java/com/evolveum/midpoint/task/quartzimpl/execution/JobExecutor.java

  Log Message:
  -----------
  Fix CacheCounterManager memleak (MID-6343)

This is a TEMPORARY fix for memory leak in CacheCounterManager.

1) Entries in counter manager are now created only if suspendTask
action is present.

2) Entries are cleaned up for all tasks (not only for lightweight
partitioning ones).

3) Storage of whole tasks is avoided. Only name and OID is recorded.

However, the whole fix has to be reviewed thoroughly and carried
over to master. (The state in master is already partially OK;
but not completely.)

Note that thresholds tests are failing. But they were failing
even before this commit.


  Commit: 5241d3a32e9bd6590393f1c9f94fc5a0ba023cad
      https://github.com/Evolveum/midpoint/commit/5241d3a32e9bd6590393f1c9f94fc5a0ba023cad
  Author: Pavol Mederly <mederly at evolveum.com>
  Date:   2020-06-23 (Tue, 23 Jun 2020)

  Changed paths:
    M gui/admin-gui/src/main/java/com/evolveum/midpoint/web/page/self/PageSelfDashboard.java

  Log Message:
  -----------
  Remove loading work items and cases (MID-6344)

The loadWorkItems() and loadMyRequests() methods on PageDashboard
were doing unconstrained searches for work items and cases, leading
to consumption of huge amounts (hundreds of MBs) of heap.

Output of the methods was not used anyway, so here we simple
deleted them. However, the heap consumption issue still needs to
be investigated and fixed, if necessary.


Compare: https://github.com/Evolveum/midpoint/compare/bbffba0e8b0a...5241d3a32e9b