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 206435 - NullPointerException at org.eclipse.core.internal.net.ProxyManager.getPluggedInAuthenticator
Summary: NullPointerException at org.eclipse.core.internal.net.ProxyManager.getPlugged...
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Netigso (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
: 206436 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-12-15 11:56 UTC by ray_ww
Modified: 2013-05-17 06:54 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 182673

Attachments
stacktrace (4.62 KB, text/plain)
2011-12-15 11:56 UTC, ray_ww 		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 ray_ww 2011-12-15 11:56:07 UTC 
This issue was reported manually by ray_ww.
It already has 4 duplicates 


Build: NetBeans IDE 7.1 RC2 (Build 201111302200)
VM: Java HotSpot(TM) Client VM, 21.1-b02, Java(TM) SE Runtime Environment, 1.7.0_01-b08
OS: Windows XP

User Comments:
ray_ww: Starting up Netbeans

ray_ww: Starting Netbeans

ray_ww: Starting up Netbeans




Stacktrace: 
java.lang.NullPointerException
   at org.eclipse.core.internal.net.ProxyManager.getPluggedInAuthenticator(ProxyManager.java:390)
   at org.eclipse.core.internal.net.ProxyManager.registerAuthenticator(ProxyManager.java:383)
   at org.eclipse.core.internal.net.ProxyManager.initialize(ProxyManager.java:284)
   at org.eclipse.core.internal.net.Activator.start(Activator.java:179)
   at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)
   at java.security.AccessController.doPrivileged(AccessController.java:0)
Comment 1 ray_ww 2011-12-15 11:56:10 UTC 
Created attachment 114220 [details]
stacktrace
Comment 2 Marian Mirilovic 2011-12-16 13:23:39 UTC 
*** Bug 206436 has been marked as a duplicate of this bug. ***
Comment 3 Jaroslav Tulach 2012-01-17 12:26:04 UTC 

*** This bug has been marked as a duplicate of bug 206468 ***
Comment 4 pankajkaushik 2013-03-21 08:38:39 UTC 
I think this issue is not yet resolved. I am facing the same on NetBeans 7.3. Once this exception come after that Start Screen goes off silently, and my application ends with "Result: 50346"

Stacktrace:

SEVERE [org.netbeans.modules.netbinox]: framework event org.eclipse.mylyn.commons.core type 2
java.lang.NullPointerException
	at org.eclipse.core.internal.net.ProxyManager.getPluggedInAuthenticator(ProxyManager.java:382)
	at org.eclipse.core.internal.net.ProxyManager.registerAuthenticator(ProxyManager.java:375)
	at org.eclipse.core.internal.net.ProxyManager.initialize(ProxyManager.java:276)
	at org.eclipse.core.internal.net.Activator.start(Activator.java:181)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
Caused: org.osgi.framework.BundleException: Exception in org.eclipse.core.internal.net.Activator.start() of bundle org.eclipse.core.net.
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
	at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300)
	at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
	at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:263)
	at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:
Comment 5 Jaroslav Tulach 2013-05-17 06:54:19 UTC 
Exception reporter does not show any failure coming from 7.2 or 7.3. Looks like this issue is fixed.