quarkus: Unable to run two CLI processes in parallel

Describe the bug

When using Quarkus with PicoCLI combo and having one process running in development mode - I’m unable to run another process of the same application from a native binary. It just exits with return code 1. Nothing else is printed, I cannot even get output from --help.

Expected behavior

I should be able to run the second instance without problems.

Actual behavior

Parallel run exists without any output with return code 1.

To Reproduce

I can probably work on a reproducer, opening this ticket so that I do not forget to do so.

Screenshots

(If applicable, add screenshots to help explain your problem.)

Environment (please complete the following information):

Output of uname -a or ver

❯ uname -a Linux mistress 5.12.11-200.fc33.x86_64 #1 SMP Wed Jun 16 16:10:53 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Output of java -version

❯ java -version
openjdk version "11.0.11" 2021-04-20
OpenJDK Runtime Environment 18.9 (build 11.0.11+9)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.11+9, mixed mode, sharing)

GraalVM version (if different from Java)

-Dquarkus.native.builder-image=quay.io/quarkus/ubi-quarkus-native-image:21.1-java11

Quarkus version or git rev

-Dquarkus.native.builder-image=quay.io/quarkus/ubi-quarkus-native-image:21.1-java11

Build tool (ie. output of mvnw --version or gradlew --version)

❯ ./mvnw --version
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /home/goldmann/.m2/wrapper/dists/apache-maven-3.6.3-bin/1iopthnavndlasol9gbrbg6bf2/apache-maven-3.6.3
Java version: 11.0.11, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-11-openjdk-11.0.11.0.9-4.fc33.x86_64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.12.11-200.fc33.x86_64", arch: "amd64", family: "unix

Additional context

(Add any other context about the problem here.)

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 19 (9 by maintainers)

Most upvoted comments

Should we change the topic of this issue to “Mysterious port opened in native mode” ? =)

Closing this as it’s not a Quarkus issue