Agent Disconnect on Memory Dump
Hi Team,
I'm Facing issue while having deep memory snapshot,here WebLogic Agent gets disconnected.
Also it impacts application as in this case application break down.
In this scenario we have to restart application to resolve issue.
I'm trying to take dump on UAT environment where we have embedded collector.
Please suggest.
Regards,
Amol
Below are the entries found in collector log files,
"WARNING Controller Connection between controller and agent WeblogicUATPORTALAPP_MNGD1@rbvs021:28120 closed.: com.dynatrace.diagnostics.collector.agentcenter.Controller a:612
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at java.io.DataInputStream.readInt(DataInputStream.java:370)
at com.dynatrace.diagnostics.core.serialization.buffer.wrapper.DataInputStreamWrapper.readInt(SourceFile:93)
at com.dynatrace.diagnostics.collector.protocol.agent.ControllerProtocol30.b(SourceFile:373)
at com.dynatrace.diagnostics.collector.protocol.agent.ControllerProtocol30.sendNOOPCommand(SourceFile:1597)
at com.dynatrace.diagnostics.collector.agentcenter.Controller.sendNOOPCommand(SourceFile:646)
at com.dynatrace.diagnostics.collector.agentcenter.Controller.run(SourceFile:813)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
2012-12-13 12:34:23 INFO Controller Controller closed connection to agent WeblogicUATPORTALAPP_MNGD1@rbvs021:28120"
Please suggest.
Regards,
Amol
I suggest opening a suppport ticket for this
Thanks for reply.
We have max 4GB of heap and try to have full dump when Used memory passed 3GB.I want to know what is recomended additional approximately native memory required to fasten the dump.
Regards,
Amol
I think that shouldnt be a problem at all. When we request a memory dump the JVM needs some extra native memory to tag the objects on the heap. It shouldnt be a problem in your case - please give it a try
As for your problem you posted earlier - have a look at the agent log file. It seems you loose the connection to the agent while we are colleting the memory information. would be interesting to explore the agent log file for any root cause information
Andi
