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 175677 - exceptions starting debugger; don't use j2ee
Summary: exceptions starting debugger; don't use j2ee
Status: RESOLVED FIXED
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: 2009-10-29 16:15 UTC by err
Modified: 2009-11-04 03:12 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
messages.log (42.63 KB, text/plain)
2009-10-29 16:16 UTC, err 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description err 2009-10-29 16:15:38 UTC 
Noticed exceptions in messages.log that appeared when starting debugger. I was debugging a NB module using default
platform. I shouldn't have any glassfish stuff running. I used a large install with Feature on request and never should
have requested JEE.

Attaching messages.log.


INFO [glassfish]
java.net.SocketException: Connection reset
	at java.net.SocketInputStream.read(SocketInputStream.java:168)
	at java.net.SocketInputStream.read(SocketInputStream.java:90)
	at org.netbeans.modules.glassfish.spi.Utils.isSecurePort(Utils.java:213)
	at org.netbeans.modules.glassfish.spi.Utils.isSecurePort(Utils.java:179)
	at org.netbeans.modules.glassfish.spi.Utils.getHttpListenerProtocol(Utils.java:146)
	at org.netbeans.modules.glassfish.spi.Utils.getHttpListenerProtocol(Utils.java:132)
	at org.netbeans.modules.glassfish.javaee.Hk2DeploymentManager.constructServerUri(Hk2DeploymentManager.java:536)
	at org.netbeans.modules.glassfish.javaee.Hk2DeploymentManager.getTargets(Hk2DeploymentManager.java:469)
	at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.getTargetMap(ServerInstance.java:543)
	at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.getTargets(ServerInstance.java:501)
        ...
Comment 1 err 2009-10-29 16:16:27 UTC 
Created attachment 90218 [details]
messages.log
Comment 2 Vince Kraemer 2009-10-29 20:21:30 UTC 
I can get rid of the ST easy enough... but that still doesn't answer why the Java EE features were enabled...  that may be a tad bit trickier.
Comment 3 err 2009-10-29 20:38:21 UTC 
So you are saying that since I saw that exception when I started the debugger, that does in fact imply that jEE was enabled.

I just finished install a java only NB, to make sure there are no jEE issues for some other problems, and during startup
I got a dialog with:
    Warning - could not install some modules: Entity Relationship Diagram Support
    - The module named org.netbeans.modules.j2eeserver/4 was needed and not found.

(filed Issue 175710 about that dependency)

I think ERD was recently put back in, do you think there could be some relationship with jEE getting enabled with
previous full install?
Comment 4 Vince Kraemer 2009-11-04 03:12:41 UTC 
this commit includes a change that squashes the exception  http://hg.netbeans.org/web-main/rev/b6def7ce4cc7

I need to look at the other part of this issue... but will open a different bug to track anything that I find.