Https and Java 8

[remi-parain]

It seems that Java 8 break the Https certificate keystore initialization/generation. (It work great on java 7, same platform )

Platform :

• Ubuntu server 14.04

Java Info :

• java version "1.8.0_05"
• Java(TM) SE Runtime Environment (build 1.8.0_05-b13)
• Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed mode)

exception :

[ERROR]  wisdom-engine {nioEventLoopGroup-3-5} - Cannot generate or read the fake key store 
java.security.cert.CertificateException: Subject class type invalid.
    at sun.security.x509.X509CertInfo.setSubject(X509CertInfo.java:888) ~[na:1.8.0_05]
    at sun.security.x509.X509CertInfo.set(X509CertInfo.java:415) ~[na:1.8.0_05]
    at org.wisdom.engine.ssl.FakeKeyStore.createSelfSignedCertificate(FakeKeyStore.java:127) ~[wisdom-engine-0.5.1.jar:na]
    at org.wisdom.engine.ssl.FakeKeyStore.generateAndStoreKeyStore(FakeKeyStore.java:96) ~[wisdom-engine-0.5.1.jar:na]
    at org.wisdom.engine.ssl.FakeKeyStore.keyManagerFactory(FakeKeyStore.java:58) ~[wisdom-engine-0.5.1.jar:na]
    at org.wisdom.engine.ssl.SSLServerContext.getFakeKeyManagerFactory(SSLServerContext.java:144) [wisdom-engine-0.5.1.jar:na]
    at org.wisdom.engine.ssl.SSLServerContext.<init>(SSLServerContext.java:60) [wisdom-engine-0.5.1.jar:na]
    at org.wisdom.engine.ssl.SSLServerContext.getInstance(SSLServerContext.java:93) [wisdom-engine-0.5.1.jar:na]
    at org.wisdom.engine.server.WisdomServerInitializer.initChannel(WisdomServerInitializer.java:55) [wisdom-engine-0.5.1.jar:na]
    at org.wisdom.engine.server.WisdomServerInitializer.initChannel(WisdomServerInitializer.java:39) [wisdom-engine-0.5.1.jar:na]
    at io.netty.channel.ChannelInitializer.channelRegistered(ChannelInitializer.java:69) [netty-transport-4.0.19.Final.jar:4.0.19.Final]
    at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRegistered(DefaultChannelHandlerContext.java:166) [netty-transport-4.0.19.Final.jar:4.0.19.Final]
    at io.netty.channel.DefaultChannelHandlerContext.fireChannelRegistered(DefaultChannelHandlerContext.java:152) [netty-transport-4.0.19.Final.jar:4.0.19.Final]
    at io.netty.channel.DefaultChannelPipeline.fireChannelRegistered(DefaultChannelPipeline.java:730) [netty-transport-4.0.19.Final.jar:4.0.19.Final]
    at io.netty.channel.AbstractChannel$AbstractUnsafe.register0(AbstractChannel.java:443) [netty-transport-4.0.19.Final.jar:4.0.19.Final]
    at io.netty.channel.AbstractChannel$AbstractUnsafe.access$100(AbstractChannel.java:375) [netty-transport-4.0.19.Final.jar:4.0.19.Final]
    at io.netty.channel.AbstractChannel$AbstractUnsafe$1.run(AbstractChannel.java:419) [netty-transport-4.0.19.Final.jar:4.0.19.Final]
    at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:370) [netty-common-4.0.19.Final.jar:4.0.19.Final]
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:353) [netty-transport-4.0.19.Final.jar:4.0.19.Final]
    at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) [netty-common-4.0.19.Final.jar:4.0.19.Final]
    at java.lang.Thread.run(Thread.java:745) [na:1.8.0_05]

[remi-parain]

Here is the reason (same issue on openJDK) :
https://bugs.openjdk.java.net/browse/JDK-8040820

[remi-parain]

it looks great. Thanks !