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.
Build: NetBeans IDE 7.2 Beta (Build 201205031832) VM: Java HotSpot(TM) Client VM, 22.0-b10, Java(TM) SE Runtime Environment, 1.7.0_02-b13 OS: Windows 7 User Comments: GUEST: starting debug of application GUEST: Starting my application in Debug mode. Stacktrace: java.lang.NullPointerException at com.sun.tools.jdi.EventRequestManagerImpl.request(EventRequestManagerImpl.java:944) at com.sun.tools.jdi.EventSetImpl$EventImpl.<init>(EventSetImpl.java:88) at com.sun.tools.jdi.EventSetImpl$ThreadedEventImpl.<init>(EventSetImpl.java:175) at com.sun.tools.jdi.EventSetImpl$ClassPrepareEventImpl.<init>(EventSetImpl.java:367) at com.sun.tools.jdi.EventSetImpl.createEvent(EventSetImpl.java:741) at com.sun.tools.jdi.EventSetImpl.build(EventSetImpl.java:628)
Created attachment 122451 [details] stacktrace
Not a bug in NetBeans, therefore it can not be fixed. See http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6744127
Please reevaluate the bug because the bug broke debugging. At least show exception reporter with that kind of exception only once.
I do not understand what do you want me to reevaluate. If you want the issue to be fixed, increase the priority of https://bugs.openjdk.java.net/browse/JDK-6744127 The problem of cyclical error reports is a different problem, it's likely similar to issue #194410.
(In reply to Martin Entlicher from comment #4) > I do not understand what do you want me to reevaluate. > If you want the issue to be fixed, increase the priority of > https://bugs.openjdk.java.net/browse/JDK-6744127 > > The problem of cyclical error reports is a different problem, it's likely > similar to issue #194410. I do not want see exception reporter for known jdk bug. It prevent me to debug application. Please do not report exception (if you want exception, print exception in log)
I really doubt that it's the exception *report* that prevents from debugging. The exception likely breaks the loop at com.sun.tools.jdi.InternalEventHandler.run(), which makes further debugging impossible. The only way to proceed is to restart the debugging session, right?
(In reply to Martin Entlicher from comment #6) > I really doubt that it's the exception *report* that prevents from > debugging. The exception likely breaks the loop at > com.sun.tools.jdi.InternalEventHandler.run(), which makes further debugging > impossible. The only way to proceed is to restart the debugging session, > right? No, a lot of functionality still alive and application is alive. In most cases it is enough for me. Why it is a stopper for me? Because I start application by "Debug main project" and "Finish debug session" will kill application.
Created attachment 153084 [details] stacktrace Having problems doing a ((UIInput) toValidate).setSubmitedValue((UIInput) toValidate).getValue(); When the contents of the input are a Primfaces Calendar object. I suspect that the setSubmittedValue method is not working.
Please ignore my previous comment (8). This has nothing to do with a PrimeFaces Calendar object. That just happened to be an issue that I was dealing with when the 'silent' error occurred.
I've discussed a possibility to filter the known JDK exceptions, but the conclusion was, that we still want to be notified about problems that our users run to. Priority of issues that are encountered often, should be increased. If there is an issue that prevents you from a serious work, add -J-Dnetbeans.exception.report.min.level=99999 option. This will just show an error icon in the right bottom corner and you can decide whether to report it or not. But this affects all exceptions. I've increased priority of the JDK bug and also provided a patch. This should make the issue fixed soon.
*** Bug 254311 has been marked as a duplicate of this bug. ***