On Sat, Oct 20, 2018, 2:44 AM <[email protected]> wrote: > > Any idea what might be causing this? My only ideas are a bad > pipeline/user behavior, or a hypervisor issue as this server is virtualized > on vmware. >
It could be either, or both. I would probably consider doing a few things: 1. Upgrade to the latest GoCD version (18.10) and the latest jre (v11). FYI: 18.9 DOES NOT support any jre above 1.8 2. When the jvm locks again, run `kill -3 PID` a few times every second and grab the thread dump(s) from the go-server.log.out file. Attach the thread dump to an issue on GitHub. Do not attach the entire file. 3. (Optional) Point a tool like jvisualvm or jconsole to the running jvm (you may need to set additional jvm args using `GOCD_SERVER_SYSTEM_PROPERTIES` system environment to enable remote monitoring of the jcm, based on what the tool recommends for deeper insight into what code is blocking up... -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
