Hi,
I've been onboard for several years without upgrade issue but hit a wall when moving from 52.17 to 53.1. IA64 jar style updates using NSSM as a service tool. this has been rock solid for me.. In this upgrade case I watch the cpu utilization and it never settles down as usual with an upgrade.
Was there anything in particular with this update I should know?
Thanks,
Regis
1G is extremely low, use 2-3G at least
Did that, -Xmg3g (its a 16gb system memory). still goes into infinite cpu utilization loop. Is there a log that can be reviewed during the upgrade? If you can provide where to access it. Thank you.
Regis
Send the application logs when the spike starts. I don’t know how is the logging configured in the windows machine
I cannot get Metabase running to see the logs. Can you please refer me to someone familiar with x64 architecture where i can see the logs on disk? I tried from java help but no success.
@crwheelr when Metabase starts, it outputs the logs, so you should have the logs in the service console in windows, a text file or something. This is not about x64, amd64, risc or anything related, you need to find the person who configured Metabase in that windows server to know where the logs are being streamed to and send those to pinpoint the issue
