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.
NB Build:NetBeans IDE Dev 200805150003 Appserver Biuild:GF2.1(b-33) JDk build:jdk1.5.0_13 Steps to reproduce: 1.Install NB and GF2.1 2.Start IDE and register GF2.1 3.Start server in profile mode. 4.Right click on the server select restart On restarting srever getting exception message as: Profiler Agent Error: Exception when trying to send response or command to client: java.net.SocketException: Broken pipe java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1685) at java.io.ObjectOutputStream$BlockDataOutputStream.flush(ObjectOutputStream.java:1630) at java.io.ObjectOutputStream.flush(ObjectOutputStream.java:666) at org.netbeans.lib.profiler.wireprotocol.WireIO.sendSimpleResponse(WireIO.java:354) at org.netbeans.lib.profiler.server.ProfilerServer.sendSimpleResponseToClient(ProfilerServer.java:744) at org.netbeans.lib.profiler.server.ProfilerServer.handleClientCommand(ProfilerServer.java:1550) at org.netbeans.lib.profiler.server.ProfilerServer.listenToClient(ProfilerServer.java:1696) at org.netbeans.lib.profiler.server.ProfilerServer.run(ProfilerServer.java:687) And on stoping server gettign exception message as: Profiler Agent Error: Exception when handling command from client: java.io.IOException: JFluid wire protocol error: code does not correspond to command or response. Value -1
this seems a bit contrived... but...
this looks like it is something to work for 7.0 now...
This also applies to 6.5. The JVM is waiting for the profiler to attach and we call stop-domain... which triggers the exception. Need to look for a way to tell the agent to die quietly. Please update this issue with necessary info about how the GF plugin can shutdown the GF JVM that is waiting for the IDE to attach in an orderly fashion. Then feel free to re-assign it back to me.
The exceptions are totally harmless. Unfortunately, there is currently no way to gracefully shut down a JVM waiting for the profiler to attach. While I was evaluating this issue I noticed something else, may be even more important - it is not possible to restart or stop the GF instance while it is waiting for the profiler client to attach. The menu items are grayed out.
cannot reproduce with 3.1.1 and 7.0.1... marking as worksforme, since I do not know which code change resolved this issue