[ 
https://issues.apache.org/jira/browse/SCB-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387158#comment-16387158
 ] 

ASF GitHub Bot commented on SCB-365:
------------------------------------

wujimin commented on issue #567: [SCB-365]when configured ssl certificates not 
exists, startup will hang and no error messages
URL: 
https://github.com/apache/incubator-servicecomb-java-chassis/pull/567#issuecomment-370636920
 
 
   submit a vertx issue, waiting for response.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> when configured ssl certificates not exists, startup will hang and no error 
> messages
> ------------------------------------------------------------------------------------
>
>                 Key: SCB-365
>                 URL: https://issues.apache.org/jira/browse/SCB-365
>             Project: Apache ServiceComb
>          Issue Type: Bug
>          Components: Java-Chassis
>    Affects Versions: java-chassis-1.0.0-m1
>            Reporter: liubao
>            Assignee: liubao
>            Priority: Major
>
> runnging demo of springmvc-server
>  # modify ssl.keystore to a wrong file name;
>  # start springmvc-server demo
> we will see startup is hang and no error messages is printed
>  
> Root cause anaylse:
> For HttpServer in Verticals, vert.x will create a CloseHook and execute 
> deploy callback. But HttpServer CloseHook will check if httpserver is created 
> and listen is successful. if not it will not execute deploy callback and 
> VertexUtils.blockDeploy will hang.
>  
> Solutions:
> This is not a valid scenario, so just print the exceptions and give user 
> diagnosis information is enough now. We will future to feedback to vert.x to 
> see better solution.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to