This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
The exception is thrown during 'get snapshot' of finished application. Profiler Engine: connection with agent closed Profiler Engine: connection with agent closed Profiler Engine: exception when trying to send response or command to client: java.net.SocketException: Socket closed java.net.SocketException: Socket closed at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:105) at java.net.SocketOutputStream.write(SocketOutputStream.java:137) at java.io.ObjectOutputStream$BlockDataOutputStream.writeBlockHeader(ObjectOutputStream.java:1691) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1676) at java.io.ObjectOutputStream$BlockDataOutputStream.flush(ObjectOutputStream.java:1622) at java.io.ObjectOutputStream.flush(ObjectOutputStream.java:656) at com.sun.tools.profiler.wireprotocol.WireIO.sendComplexCommand(WireIO.java:55) at com.sun.tools.profiler.server.ProfilerServer.sendComplexCmdToClient(ProfilerServer.java:513) at com.sun.tools.profiler.server.ProfilerInterface.firstTimeMethodInvokeHook(ProfilerInterface.java:754) at com.sun.tools.profiler.server.ProfilerInterface.access$000(ProfilerInterface.java:25) at com.sun.tools.profiler.server.ProfilerInterface$1.handleFirstTimeMethodInvoke(ProfilerInterface.java:91) at com.sun.tools.profiler.server.ProfilerRuntimeCPUFullInstr.methodEntry(ProfilerRuntimeCPUFullInstr.java:95) at java.lang.Shutdown.halt(Shutdown.java:144) at java.lang.Shutdown.exit(Shutdown.java:220) at java.lang.Runtime.exit(Runtime.java:91) at java.lang.System.exit(System.java:869) at org.netbeans.test4u.tests.request.TestRequestProcessor.responseRequest(TestRequestProcessor.java:67) at org.ehucka.core.api.request.RequestServer$DispatchThread.run(RequestServer.java:144) Profiler Engine: connection with agent closed
How often does this happen, is it reproducible?
I found it is thrown when the profiled application is frozen. The profiler than get to state 'NOT RUNNING' (Detach button is disabled) but the port 5140 is still bound. The application is still present in Runtime|Processes node.
Created attachment 25856 [details] threaddump
Created attachment 25857 [details] application's threaddump
Another reproduction: The exception is thrown after taking snapshot of a finished uni test too.
Profiler probably tries to instrument Shutdown methods: event thread of blocked application: "AWT-EventQueue-0" prio=1 tid=0x081d3448 nid=0x4777 in Object.wait() [0xa9a70000..0xa9a71030] at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:474) at com.sun.tools.profiler.server.ProfilerServer.getLastResponse(ProfilerServer.java:931) - locked <0xaad279c8> (a java.lang.Object) - locked <0xae8b6528> (a java.lang.Class) at com.sun.tools.profiler.server.ProfilerInterface.getAndInstrumentClasses(ProfilerInterface.java:402) at com.sun.tools.profiler.server.ProfilerInterface.firstTimeMethodInvokeHook(ProfilerInterface.java:755) - locked <0xaad26850> (a java.lang.Object) at com.sun.tools.profiler.server.ProfilerInterface.access$000(ProfilerInterface.java:25) at com.sun.tools.profiler.server.ProfilerInterface$1.handleFirstTimeMethodInvoke(ProfilerInterface.java:91) at com.sun.tools.profiler.server.ProfilerRuntimeCPUFullInstr.methodEntry(ProfilerRuntimeCPUFullInstr.java:95) at java.lang.Shutdown.halt(Shutdown.java:144) at java.lang.Shutdown.exit(Shutdown.java:220) - locked <0xae964b60> (a java.lang.Class) at java.lang.Runtime.exit(Runtime.java:91) at java.lang.System.exit(System.java:869) ...
Fixed
v