[
https://issues.apache.org/jira/browse/SCB-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563306#comment-16563306
]
YaoHaishi commented on SCB-711:
-------------------------------
About the error log "io.vertx.core.VertxException: ALPN not available for JDK
SSL/TLS engine", this page
[https://groups.google.com/forum/#!topic/vertx/loUax_Twx8s|https://groups.google.com/forum/#!topic/vertx/loUax_Twx8s]]
says that we can resolve this problem by importing dependency
_io.netty:netty-tcnative-boringssl-static._ And we have imported this
dependency in SCB-368. So generally speaking users should not meet this error.
One case I've met is that a user runs a microservice developed by ServiceComb.
Her operating system is Windows7 64-bit, but a 32-bit JDK is installed to run
java application. Maven downloaded the netty-tcnative-boringssl-static jar file
with 64-bit ddl file. But when the microservice application runs, it gets
"x86_32" as system architecture and tries to load 32-bit ddl file and fails.
> HTTP2 and other client should be lasy initialized
> --------------------------------------------------
>
> Key: SCB-711
> URL: https://issues.apache.org/jira/browse/SCB-711
> Project: Apache ServiceComb
> Issue Type: Improvement
> Reporter: liubao
> Assignee: YaoHaishi
> Priority: Major
> Fix For: java-chassis-1.1.0
>
>
> There are some drabacks now
> # unnecessary resource
> # Now throws exception
> [2018-07-03
> 20:16:39,703/CST][transport-vert.x-eventloop-thread-3][ERROR]deploy vertx
> failed, cause
> org.apache.servicecomb.foundation.vertx.VertxUtils.lambda$blockDeploy$0(VertxUtils.java:102)
> io.vertx.core.VertxException: ALPN not available for JDK SSL/TLS engine
> at io.vertx.core.net.impl.SSLHelper.resolveEngineOptions(SSLHelper.java:90)
> at io.vertx.core.net.impl.SSLHelper.<init>(SSLHelper.java:151)
> at io.vertx.core.http.impl.HttpClientImpl.<init>(HttpClientImpl.java:131)
> at io.vertx.core.impl.VertxImpl.createHttpClient(VertxImpl.java:296)
> at
> org.apache.servicecomb.foundation.vertx.client.http.HttpClientPoolFactory.createClientPool(HttpClientPoolFactory.java:36)
> at
> org.apache.servicecomb.foundation.vertx.client.http.HttpClientPoolFactory.createClientPool(HttpClientPoolFactory.java:27)
> at
> org.apache.servicecomb.foundation.vertx.client.ClientPoolManager.createClientPool(ClientPoolManager.java:60)
> at
> org.apache.servicecomb.foundation.vertx.client.ClientVerticle.start(ClientVerticle.java:35)
> at io.vertx.core.AbstractVerticle.start(AbstractVerticle.java:111)
> at
> io.vertx.core.impl.DeploymentManager.lambda$doDeploy$10(DeploymentManager.java:481)
> at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:344)
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404)
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:463)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:748)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
