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.
See these reports... http://forums.java.net/jive/thread.jspa?threadID=21875&tstart=0 https://glassfish.dev.java.net/servlets/ReadMsg?list=dev&msgNo=3140 The issue appears to be more critical with JDK6.
This issue seems to be already fixed in b31 and for the second one: isn't it https://glassfish.dev.java.net/issues/show_bug.cgi?id=2048 ?
It may be... I logged this to make sure....
jdk 5_10 nb 6.0 recent pull gf v2 b31 starting the server from inside netbeans produces stack traces as described ON FIRST START UP... secondard
jdk6 nb 6 gf v2 b31 same issue
Looks like it related to creating the nodes for runtime explorer... If ContainerChildFactory.getChildrenObject is only asked to return a NodeTypes.DOMAIN the exception goes away. Once the getChildObject methods gets called with NodeTypes.JDBC_RESOURCES.equals(type)... the exceptions are generated. [Probably other NodeTypes will cause an issue. i am just using the NodeTypes.JDBC_RESOURCES as an example]
actually an issue in PortDetector... diff : http://www.netbeans.org/source/browse/serverplugins/sun/appsrv/src/org/netbeans/modules/j2ee/sun/appsrvapi/PortDetector.java?r1=1.9&r2=1.10 Needs 8.2 (PE & EE), V2 (setup, setup-cluster) verification.
Verified fix againt 9.1 PE, EE and 8.2 PE, EE
Checking in PortDetector.java; /cvs/serverplugins/sun/appsrv/src/org/netbeans/modules/j2ee/sun/appsrvapi/PortDetector.java,v <-- PortDetector.java new revision: 1.1.16.2.2.2.26.2; previous revision: 1.1.16.2.2.2.26.1 done
verified with NB 5.5.1 from 13 Feb and GF b33. thanks.