java.lang.SecurityException: Can not initialize cryptographic mechanism

Support for Ubuntu and other Desktop Linux distributions
Post Reply
chriscrutch
Posts: 1
Joined: 13 Sep 2016, 05:10

java.lang.SecurityException: Can not initialize cryptographic mechanism

Post by chriscrutch »

This problem has just popped up in the last couple days. Was previously working just fine. Filebot 4.7.2 on Ubuntu 14.04, Java version 9b134

Console output:

Code: Select all

NoClassDefFoundError: Could not initialize class sun.security.ssl.SSLContextImpl$DefaultSSLContext
java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: Could not initialize class sun.security.ssl.SSLContextImpl$DefaultSSLContext
	at net.filebot.ui.rename.RenamePanel$AutoCompleteAction$1.done(RenamePanel.java:843)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class sun.security.ssl.SSLContextImpl$DefaultSSLContext
	at net.filebot.web.WebRequest.fetch(WebRequest.java:120)
	at net.filebot.CachedResource.lambda$fetchIfModified$8(CachedResource.java:186)
	at net.filebot.CachedResource.lambda$null$0(CachedResource.java:83)
	at net.filebot.CachedResource.retry(CachedResource.java:112)
	at net.filebot.CachedResource.lambda$get$1(CachedResource.java:83)
	at net.filebot.Cache.computeIf(Cache.java:85)
	at net.filebot.CachedResource.get(CachedResource.java:78)
	at net.filebot.media.ReleaseInfo.lambda$resource$18(ReleaseInfo.java:489)
	at net.filebot.MemoizedResource.get(Resource.java:36)
	at net.filebot.media.ReleaseInfo.getExcludePattern(ReleaseInfo.java:358)
	at net.filebot.media.ReleaseInfo.getClutterFileFilter(ReleaseInfo.java:407)
	at net.filebot.media.MediaDetection.getClutterFileFilter(MediaDetection.java:87)
	at net.filebot.ui.rename.EpisodeListMatcher.match(EpisodeListMatcher.java:77)
	at net.filebot.ui.rename.RenamePanel$AutoCompleteAction$1.doInBackground(RenamePanel.java:828)
	at net.filebot.ui.rename.RenamePanel$AutoCompleteAction$1.doInBackground(RenamePanel.java:824)
filebot -script fn:sysinfo output:

Code: Select all

null
java.lang.ExceptionInInitializerError
	at net.filebot.web.WebRequest.fetch(WebRequest.java:120)
	at net.filebot.CachedResource.lambda$fetchIfModified$8(CachedResource.java:186)
	at net.filebot.CachedResource.lambda$null$0(CachedResource.java:83)
	at net.filebot.CachedResource.retry(CachedResource.java:112)
	at net.filebot.CachedResource.lambda$get$1(CachedResource.java:83)
	at net.filebot.Cache.computeIf(Cache.java:85)
	at net.filebot.CachedResource.get(CachedResource.java:78)
	at net.filebot.MemoizedResource.get(Resource.java:36)
	at net.filebot.cli.ScriptBundle.getScript(ScriptBundle.java:34)
	at net.filebot.cli.ScriptShell.runScript(ScriptShell.java:72)
	at net.filebot.cli.ArgumentProcessor.runScript(ArgumentProcessor.java:113)
	at net.filebot.cli.ArgumentProcessor.run(ArgumentProcessor.java:28)
	at net.filebot.Main.main(Main.java:124)
Caused by: java.lang.SecurityException: Can not initialize cryptographic mechanism
	... 13 more
Caused by: java.lang.NullPointerException
	... 13 more
Failure (°_°)
Ideas? Thanks to all.

--chriscrutch
User avatar
rednoah
The Source
Posts: 22986
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Filebot cannot connect to internet

Post by rednoah »

java wrote:java.lang.SecurityException: Can not initialize cryptographic mechanism
Google is your friend when dealing with obscure Java issues. ;)

PS: You're using Java 9 which won't be released until next year. If you're using pre-alpha software, expect things to not work. ;)
:idea: Please read the FAQ and How to Request Help.
UrstMcRedHead
Posts: 1
Joined: 23 Jul 2017, 02:11

Re: java.lang.SecurityException: Can not initialize cryptographic mechanism

Post by UrstMcRedHead »

I just got a similar error on a bone stock KUbuntu install and this is the #2 entry for my error in a Google search.

Also I made a forum account Just to let everyone know just how helpful rednoah's answer to this issue was.
Thanks man. I wouldn't know what to do with my free time without you.


EDIT: after 5 more minutes of Google searching.
This may be related to the following bug with JDK9
https://bugs.debian.org/cgi-bin/bugrepo ... bug=866924


I for some reason I had both jdk8, and jdk9 installed at the same time, and removing jdk8 fixed the issue.
Post Reply