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.

Bug 135309 - Profiler Agent Error: Exception when trying to send response or command to client
Summary: Profiler Agent Error: Exception when trying to send response or command to cl...
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-19 13:12 UTC by dpkumar
Modified: 2011-10-31 22:11 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dpkumar 2008-05-19 13:12:47 UTC
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
Comment 1 Vince Kraemer 2008-06-20 23:08:35 UTC
this seems a bit contrived... but...
Comment 2 Vince Kraemer 2008-10-25 03:55:15 UTC
this looks like it is something to work for 7.0 now...
Comment 3 Vince Kraemer 2008-11-14 20:55:52 UTC
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.
Comment 4 J Bachorik 2011-10-05 17:29:36 UTC
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.
Comment 5 Vince Kraemer 2011-10-31 22:11:32 UTC
cannot reproduce with 3.1.1 and 7.0.1...

marking as worksforme, since I do not know which code change resolved this issue