We continue to try and get to the bottom of some GC issues but suspect the underlying issue is somewhere else (network?) We're pretty green with Dynatrace - I'm thinking someone with more knowledge of the tools would peg this quickly. I'm trying to determine what is causing the suspension in the screen shot. We know we are leading into a period where the GC will spin out of control, but I thought that would suspend all execution. It looks like calls out to the database are getting suspended - leading to suspect network, but I'm not sure. Can someone tell from the attached screenshot? thx
This just looks like your GC process took place when this call to your DB happened, your actual socket read doesn't have any GC time and looks to have executed correctly. What my guess would be is when your code got to the executeQuery method your JVM or CLR had to trigger GC at this time leading to the higher response time of this method.