quarkus: "VertxException: Thread blocked" when running quarkus in ssl-only mode

Describe the bug If I disable http and enable https a lot of warnings about blocked vertex threads are shown. This happens only if I set quarkus.http.ssl-port to 0.

Expected behavior Startup shows no warnings

Actual behavior see attached log file

To Reproduce Steps to reproduce the behavior:

  1. git clone https://github.com/quarkusio/quarkus-quickstarts.git
  2. cd quarkus-quickstarts/openapi-swaggerui-quickstart
  3. change application.properties
  4. run mvn quarkus:dev log.txt

I’m not sure if that’s the right property but settingquarkus.vertx.max-worker-execute-timeto a higher value did not have any effects.

Configuration

quarkus.http.ssl-port=0
quarkus.http.insecure-requests=disabled
quarkus.http.ssl.certificate.file=localhost.crt
quarkus.http.ssl.certificate.key-file=localhost.key
# you may use server.pem and server.key file in grpc-tls-quickstart/src/main/resources/tls/ instead

Environment (please complete the following information):

  • Output of uname -a or ver: Darwin xxx 19.4.0 Darwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64 x86_64
  • Output of java -version:
java version "11.0.7" 2020-04-14 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.7+8-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.7+8-LTS, mixed mode)
  • Quarkus version or git rev: master
  • Build tool (ie. output of mvnw --version or gradlew --version):
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /Users/thf/bin/apache-maven-3.6.3
Java version: 11.0.7, vendor: Oracle Corporation, runtime: /Users/thf/bin/jdk-11.0.7.jdk/Contents/Home
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.15.4", arch: "x86_64", family: "mac"

cc @famod

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 1
  • Comments: 15 (10 by maintainers)

Most upvoted comments

Yes, this should be fixed now.

thanks, I think the patch you provided is the most appropriate way to go @stuartwdouglas

@vietj It looks like this might be a vert.x issue. It seems that it is really slow to initialize the keystore, and this happens in a sync block so it blocking all the threads.