Bug 540636 - NoClassDefFoundError: SSLContextImpl$DefaultSSLContext
Summary: NoClassDefFoundError: SSLContextImpl$DefaultSSLContext
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.10   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-30 18:04 EDT by Ed Willink CLA
Modified: 2022-12-25 18:45 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2018-10-30 18:04:33 EDT
Using 4.10M1, Windows 10, Java 8, I get the following exception while drilling down in the Debugger Variables View.

java.lang.NoClassDefFoundError: Could not initialize class sun.security.ssl.SSLContextImpl$DefaultSSLContext
	at java.base/java.lang.Class.forName0(Native Method)
	at java.base/java.lang.Class.forName(Class.java:291)
	at java.base/java.security.Provider$Service.getImplClass(Provider.java:1848)
	at java.base/java.security.Provider$Service.newInstance(Provider.java:1824)
	at java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:236)
	at java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:164)
	at java.base/javax.net.ssl.SSLContext.getInstance(SSLContext.java:168)
	at java.base/javax.net.ssl.SSLContext.getDefault(SSLContext.java:99)
	at java.base/javax.net.ssl.SSLSocketFactory.getDefault(SSLSocketFactory.java:123)
	at java.base/javax.net.ssl.HttpsURLConnection.getDefaultSSLSocketFactory(HttpsURLConnection.java:335)
	at java.base/javax.net.ssl.HttpsURLConnection.<init>(HttpsURLConnection.java:292)
	at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.<init>(HttpsURLConnectionImpl.java:95)
	at java.base/sun.net.www.protocol.https.Handler.openConnection(Handler.java:62)
	at java.base/sun.net.www.protocol.https.Handler.openConnection(Handler.java:57)
	at java.base/java.net.URL.openConnection(URL.java:1051)
	at java.base/java.net.URL.openStream(URL.java:1117)
	at org.eclipse.m2e.sourcelookup.internal.launch.MavenArtifactIdentifier.identifyCentralSearch(MavenArtifactIdentifier.java:129)
	at org.eclipse.m2e.sourcelookup.internal.launch.MavenArtifactIdentifier.identify(MavenArtifactIdentifier.java:80)
	at org.eclipse.m2e.sourcelookup.internal.launch.MavenSourceContainerResolver.resolveSourceContainers(MavenSourceContainerResolver.java:40)
	at org.eclipse.jdt.launching.sourcelookup.advanced.AdvancedSourceLookupParticipant.getSourceContainer(AdvancedSourceLookupParticipant.java:144)
	at org.eclipse.jdt.launching.sourcelookup.advanced.AdvancedSourceLookupParticipant.lambda$1(AdvancedSourceLookupParticipant.java:134)
	at org.eclipse.jdt.internal.launching.sourcelookup.advanced.BackgroundProcessingJob.run(BackgroundProcessingJob.java:55)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Comment 1 Andrey Loskutov CLA 2018-10-30 18:15:59 EDT
Could be m2e only issue, at least it is coming from m2e.
Is this the full stack and no other exception logged?
Comment 2 Ed Willink CLA 2018-10-31 02:31:06 EDT
The popup dialog had only a useless summary. The original report is all that I could see in the log.

m2e is certainly very odd. Why is m2e wasting time during my Java debugging and why is it wasting more time on https communication?
Comment 3 Eclipse Genie CLA 2020-10-21 08:20:38 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2022-12-25 18:45:40 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.