CA Identity Portal version 14.4. Unable to stop the WildFly service gracefully through the Windows Services tab and instead need to stop java.exe in order to stop the WildFly service.
Error 1053: the Service did not respond to the start or control request in a timely fashion.
Found that the OpenJDK Java service we are using to run WildFly is taking up a lot of CPU resources. In the Windows Task Manager, we have observed that the Java service causes the CPU usage to be 100%.
Found client has 32GB or RAM. Min and max heap size was set to 16GBmin and 25GBmax. Set to 8192min and 8192max.
Release : 14.4 Standalone
Component : Identity Portal
Even though client had high load, lowing the java heap actually made Portal more efficient as it was not stressing the I/O and trying to use all the RAM at once. IP service now started and stopped properly.