It does look like AMP’s failure to query Forge version data might be part of the problem, along with a potential connectivity issue or timeouts affecting other services. Here’s what you can try:
-
Check Network Connectivity: Make sure your server can reach external sites. Ping some known URLs and make sure there are no drops. Sometimes network issues can mess with external data fetching.
-
Increase JVM Memory Pre-allocation: The
Memory pre-allocation (MB)
being set to256
might be too low. Try increasing it to around1024 MB
(1 GB) to see if it helps with stability. -
Debug Mode: We still need the Debug mode logs. Enable Debug mode in AMP if you haven’t already, and share the logs after the next backup cycle.
You can find the Debug mode by searching “Debugging” in AMP’s web interface. Let’s see if it uncovers anything more specific. If you continue to see slow method invocation warnings, there might be a deeper resource contention issue we need to address.