After an upgrade to Performance Center services won't start.
Performance Center services fail to start.
No errors are seen, the start command returns to the command line simply stating it failed to start the service.
Incorrectly configured wrapper.java.maxmemory value in the wrapper.conf for the affected service(s).
This can be seen for any of the four Performance Center services.
Release : 3.7
Component : PERFORMANCE MANAGEMENT INSTALLATIONS/UPGRADES
When this problem is observed, the normal service logs don't write messages and the command line start doesn't reveal a specific error.
We'll use the Event Manager service as an example.
When we go to the (default path) /opt/CA/PerformanceCenter/EM/bin we see files named hs_error_pid<PID#>.log. The PID represents the PID the service was assigned by the OS before it failed to start. A new one is written with each failed start attempt.
Reviewing the logs we see these messages at the start of the file.
How to configure Performance Center maximum memory settings.