Issue after upgrading form 9802 to 10001. Service crashes/stucks, when checking HA

Issue after upgrading form 9802 to 10001. Service crashes/stucks, when checking HA

Specs:
-Win 2012R2 with latest updates
-4 vCPU
-8 GB RAM

The pmp-service dies/stucks when clicking on 'High Availability' in Admin section.
CPU Usage goes up to 60%, RAM Usage stays at about 20%.

In the startup log, I get events like:


  1. INFO   | jvm 1    | 2019/04/23 08:45:35 | WrapperManager Error: Server daemon died!
  2. INFO   | jvm 1    | 2019/04/23 08:45:37 | 
  3. INFO   | jvm 1    | 2019/04/23 08:45:52 | WrapperManager Error: java.lang.OutOfMemoryError: GC overhead limit exceeded
  4. INFO   | jvm 1    | 2019/04/23 08:46:00 | WrapperManager Error: The backend was closed unexpectedly.  Restart to resync with the Wrapper.
  5. STATUS | wrapper  | 2019/04/23 08:46:05 | JVM appears hung: Timed out waiting for signal from JVM.  Restarting JVM.
  6. ERROR  | wrapper  | 2019/04/23 08:46:43 | Shutdown failed: Timed out waiting for signal from JVM.
  7. ERROR  | wrapper  | 2019/04/23 08:46:43 | JVM did not exit on request, termination requested.
  8. STATUS | wrapper  | 2019/04/23 08:46:43 | JVM exited after being requested to terminate.
Or:


  1. STATUS | wrapper  | 2019/04/23 10:29:49 | Pinging the JVM took 31 seconds to respond.
  2. STATUS | wrapper  | 2019/04/23 10:29:51 | Pinging the JVM took 28 seconds to respond.
  3. STATUS | wrapper  | 2019/04/23 10:29:53 | Pinging the JVM took 26 seconds to respond.
  4. STATUS | wrapper  | 2019/04/23 10:29:53 | Pinging the JVM took 22 seconds to respond.
  5. STATUS | wrapper  | 2019/04/23 10:29:57 | Pinging the JVM took 22 seconds to respond.
  6. STATUS | wrapper  | 2019/04/23 10:30:09 | Pinging the JVM took 29 seconds to respond.
  7. STATUS | wrapper  | 2019/04/23 10:30:09 | Pinging the JVM took 25 seconds to respond.
  8. STATUS | wrapper  | 2019/04/23 10:30:09 | Pinging the JVM took 20 seconds to respond.
  9. STATUS | wrapper  | 2019/04/23 10:30:14 | Pinging the JVM took 21 seconds to respond.
  10. STATUS | wrapper  | 2019/04/23 10:30:16 | Pinging the JVM took 18 seconds to respond.
  11. STATUS | wrapper  | 2019/04/23 10:30:53 | JVM appears hung: Timed out waiting for signal from JVM.  Restarting JVM.
  12. ERROR  | wrapper  | 2019/04/23 10:31:31 | Shutdown failed: Timed out waiting for signal from JVM.
  13. ERROR  | wrapper  | 2019/04/23 10:31:31 | JVM did not exit on request, termination requested.
  14. STATUS | wrapper  | 2019/04/23 10:31:31 | JVM exited after being requested to terminate.
  15. STATUS | wrapper  | 2019/04/23 10:31:32 | <-- Wrapper Stopped
Thanks in advance for your help

Kind regard
Danny

                  New to ADSelfService Plus?