We're having a situation on some weblogic managed servers. It seems that it takes more time to start when having OneAgent monitoring enabled than when it's disabled and running without monitoring.
Java version 1.6.0_31, Weblogic 220.127.116.11
We did some testing and without OneAgent it takes ~6.5 minutes to start. With OneAgent it takes more than 10 minutes to start.
I can understand that instrumenting the java process could impact the start time a little bit, but why this much (>50%)?
Answer by Julius L. ·
Do you have any custom services defined?
I think it is related to parts of deep monitoring instrumentation. Can you try to turn off all individual features in deep monitoring settings for this server and see if this makes any difference?
Startup time of 6.5 minutes without OneAgent is definitely not fast anyway. How many applications are deployed in this Application Server and how big is the code part in the deployed wars/ears?
Answer by Sebastian K. ·
This is something interesting in this example:
20:18:22.159 UTC [7b3ff850] info [native] URL <a href="https://xxx.xxx.xxx.xxx:9999/communication">https://xxx.xxx.xxx.xxx:9999/communication</a> not working (Connection timed out after 2000 milliseconds)
There is problem with communication between your server and ActiveGate / Cluster. But this not be reason of delay in startup.
I think here should talk somebody from Dynatrace side. I have client with weblogic and appmon and I know that there is some impact while starting but actually I don't know how big because they didn't report me this as an issue. If it is urgent for you, you can alway open support ticket.
Memory Utilization vs Used memory 0 Answers
Hiding Application/Service? 1 Answer