Failed to start quarkus #447

shivam-sharma7 · 2023-03-22T12:37:14Z

shivam-sharma7
Mar 22, 2023
Collaborator

Horreum Client ..................................... FAILURE

 to errors
        [error]: Build step io.quarkiverse.quinoa.deployment.ForwardedDevProcessor#prepareDevService threw an exception: java.lang.RuntimeException: java.lang.RuntimeException: Quinoa package manager live coding port 3000 is still not listening after the checkTimeout.
        at io.quarkiverse.quinoa.deployment.ForwardedDevProcessor.prepareDevService(ForwardedDevProcessor.java:144)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:909)
        at io.quarkus.builder.BuildContext.run(BuildContext.java:281)
        at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
        at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)
        at java.base/java.lang.Thread.run(Thread.java:829)
        at org.jboss.threads.JBossThread.run(JBossThread.java:501)
Caused by: java.lang.RuntimeException: Quinoa package manager live coding port 3000 is still not listening after the checkTimeout.
        at io.quarkiverse.quinoa.deployment.packagemanager.PackageManager.dev(PackageManager.java:113)
        at io.quarkiverse.quinoa.deployment.ForwardedDevProcessor.prepareDevService(ForwardedDevProcessor.java:122)
        ... 11 more

        at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment(AugmentActionImpl.java:335)
        at io.quarkus.runner.bootstrap.AugmentActionImpl.createInitialRuntimeApplication(AugmentActionImpl.java:252)
        at io.quarkus.runner.bootstrap.AugmentActionImpl.createInitialRuntimeApplication(AugmentActionImpl.java:60)
        at io.quarkus.deployment.dev.IsolatedDevModeMain.firstStart(IsolatedDevModeMain.java:86)
        at io.quarkus.deployment.dev.IsolatedDevModeMain.accept(IsolatedDevModeMain.java:447)
        at io.quarkus.deployment.dev.IsolatedDevModeMain.accept(IsolatedDevModeMain.java:59)
        at io.quarkus.bootstrap.app.CuratedApplication.runInCl(CuratedApplication.java:149)
        at io.quarkus.bootstrap.app.CuratedApplication.runInAugmentClassLoader(CuratedApplication.java:104)
        at io.quarkus.deployment.dev.DevModeMain.start(DevModeMain.java:131)
        at io.quarkus.deployment.dev.DevModeMain.main(DevModeMain.java:62)
Caused by: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
        [error]: Build step io.quarkiverse.quinoa.deployment.ForwardedDevProcessor#prepareDevService threw an exception: java.lang.RuntimeException: java.lang.RuntimeException: Quinoa package manager live coding port 3000 is still not listening after the checkTimeout.
        at io.quarkiverse.quinoa.deployment.ForwardedDevProcessor.prepareDevService(ForwardedDevProcessor.java:144)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:909)
        at io.quarkus.builder.BuildContext.run(BuildContext.java:281)
        at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
        at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)
        at java.base/java.lang.Thread.run(Thread.java:829)
        at org.jboss.threads.JBossThread.run(JBossThread.java:501)
Caused by: java.lang.RuntimeException: Quinoa package manager live coding port 3000 is still not listening after the checkTimeout.
        at io.quarkiverse.quinoa.deployment.packagemanager.PackageManager.dev(PackageManager.java:113)
        at io.quarkiverse.quinoa.deployment.ForwardedDevProcessor.prepareDevService(ForwardedDevProcessor.java:122)
        ... 11 more

        at io.quarkus.builder.Execution.run(Execution.java:123)
        at io.quarkus.builder.BuildExecutionBuilder.execute(BuildExecutionBuilder.java:79)
        at io.quarkus.deployment.QuarkusAugmentor.run(QuarkusAugmentor.java:160)
        at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment(AugmentActionImpl.java:331)
        ... 9 more
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Quinoa package manager live coding port 3000 is still not listening after the checkTimeout.
        at io.quarkiverse.quinoa.deployment.ForwardedDevProcessor.prepareDevService(ForwardedDevProcessor.java:144)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:909)
        at io.quarkus.builder.BuildContext.run(BuildContext.java:281)
        at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
        at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)
        at java.base/java.lang.Thread.run(Thread.java:829)
        at org.jboss.threads.JBossThread.run(JBossThread.java:501)
Caused by: java.lang.RuntimeException: Quinoa package manager live coding port 3000 is still not listening after the checkTimeout.
        at io.quarkiverse.quinoa.deployment.packagemanager.PackageManager.dev(PackageManager.java:113)
        at io.quarkiverse.quinoa.deployment.ForwardedDevProcessor.prepareDevService(ForwardedDevProcessor.java:122)
        ... 11 more


2023-03-22 17:58:47,213 INFO  [io.qua.qui.dep.pac.PackageManager] (Thread-98) Stopping Quinoa package manager live coding as a dev service.

--
Press [:] for the terminal, [h] for more options>
[INFO]
[INFO] --------------< io.hyperfoil.tools:horreum-api-generator >--------------
[INFO] Building Horreum API Generator 0.8-SNAPSHOT                        [4/7]
[INFO] ----------------------------[ maven-plugin ]----------------------------
[INFO]
[INFO] --- quarkus-maven-plugin:2.16.4.Final:dev (default-cli) @ horreum-api-generator ---
[INFO] Invoking org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources @ horreum-api-generator
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] skip non existing resourceDirectory /mnt/wsl/docker-desktop-bind-mounts/Ubuntu/e869d0daf47b2414c700f11bf08edb11c478c68611de3db18e4f7dc6aaaf6eac/horreum-api-generator/src/main/resources
[INFO] Invoking org.apache.maven.plugins:maven-compiler-plugin:3.10.1:compile @ horreum-api-generator
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 5 source files to /mnt/wsl/docker-desktop-bind-mounts/Ubuntu/e869d0daf47b2414c700f11bf08edb11c478c68611de3db18e4f7dc6aaaf6eac/horreum-api-generator/target/classes
[INFO] /mnt/wsl/docker-desktop-bind-mounts/Ubuntu/e869d0daf47b2414c700f11bf08edb11c478c68611de3db18e4f7dc6aaaf6eac/horreum-api-generator/src/main/java/io/hyperfoil/tools/horreum/generator/BufferingMethodVisitor.java: /mnt/wsl/docker-desktop-bind-mounts/Ubuntu/e869d0daf47b2414c700f11bf08edb11c478c68611de3db18e4f7dc6aaaf6eac/horreum-api-generator/src/main/java/io/hyperfoil/tools/horreum/generator/BufferingMethodVisitor.java uses or overrides a deprecated API.
[INFO] /mnt/wsl/docker-desktop-bind-mounts/Ubuntu/e869d0daf47b2414c700f11bf08edb11c478c68611de3db18e4f7dc6aaaf6eac/horreum-api-generator/src/main/java/io/hyperfoil/tools/horreum/generator/BufferingMethodVisitor.java: Recompile with -Xlint:deprecation for details.
[INFO] Invoking org.apache.maven.plugins:maven-resources-plugin:3.2.0:testResources @ horreum-api-generator
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] skip non existing resourceDirectory /mnt/wsl/docker-desktop-bind-mounts/Ubuntu/e869d0daf47b2414c700f11bf08edb11c478c68611de3db18e4f7dc6aaaf6eac/horreum-api-generator/src/test/resources
[INFO] Invoking org.apache.maven.plugins:maven-compiler-plugin:3.10.1:testCompile @ horreum-api-generator
[INFO] No sources to compile
[WARNING] The quarkus-maven-plugin build goal was not configured for this project, skipping quarkus:dev as this is assumed to be a support library. If you want to run quarkus:dev on this project make sure the quarkus-maven-plugin is configured with the build goal or disable the enforceBuildGoal flag (via plugin configuration or via -Dquarkus.enforceBuildGoal=false).
[INFO]
[INFO] -------------------< io.hyperfoil.tools:horreum-api >-------------------
[INFO] Building Horreum REST API 0.8-SNAPSHOT                             [5/7]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- quarkus-maven-plugin:2.16.4.Final:dev (default-cli) @ horreum-api ---
[INFO] Invoking org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources @ horreum-api
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] skip non existing resourceDirectory /mnt/wsl/docker-desktop-bind-mounts/Ubuntu/e869d0daf47b2414c700f11bf08edb11c478c68611de3db18e4f7dc6aaaf6eac/horreum-api/src/main/resources
[INFO] Invoking org.apache.maven.plugins:maven-compiler-plugin:3.10.1:compile @ horreum-api
[INFO] Not compiling main sources
[INFO] Invoking org.apache.maven.plugins:maven-resources-plugin:3.2.0:testResources @ horreum-api
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] skip non existing resourceDirectory /mnt/wsl/docker-desktop-bind-mounts/Ubuntu/e869d0daf47b2414c700f11bf08edb11c478c68611de3db18e4f7dc6aaaf6eac/horreum-api/src/test/resources
[INFO] Invoking org.apache.maven.plugins:maven-compiler-plugin:3.10.1:testCompile @ horreum-api
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 1 source file to /mnt/wsl/docker-desktop-bind-mounts/Ubuntu/e869d0daf47b2414c700f11bf08edb11c478c68611de3db18e4f7dc6aaaf6eac/horreum-api/target/test-classes
[WARNING] The quarkus-maven-plugin build goal was not configured for this project, skipping quarkus:dev as this is assumed to be a support library. If you want to run quarkus:dev on this project make sure the quarkus-maven-plugin is configured with the build goal or disable the enforceBuildGoal flag (via plugin configuration or via -Dquarkus.enforceBuildGoal=false).
[INFO]
[INFO] -----------------< io.hyperfoil.tools:horreum-client >------------------
[INFO] Building Horreum Client 0.8-SNAPSHOT                               [6/7]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Horreum 0.8-SNAPSHOT:
[INFO]
[INFO] Horreum ............................................ SUCCESS [  0.383 s]
[INFO] Horreum Model ...................................... SUCCESS [ 37.601 s]
[INFO] Horreum Backend .................................... SUCCESS [03:20 min]
[INFO] Horreum API Generator .............................. SUCCESS [  3.603 s]
[INFO] Horreum REST API ................................... SUCCESS [  9.206 s]
[INFO] Horreum Client ..................................... FAILURE [  0.101 s]
[INFO] Horreum Integration Tests .......................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  04:29 min
[INFO] Finished at: 2023-03-22T17:59:00+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project horreum-client: Could not resolve dependencies for project io.hyperfoil.tools:horreum-client:jar:0.8-SNAPSHOT: Could not find artifact io.hyperfoil.tools:horreum-api:jar:0.8-SNAPSHOT -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :horreum-client

johnaohara · 2023-03-22T12:49:47Z

johnaohara
Mar 22, 2023
Maintainer

The first error stack is a timeout in Quinoa waiting for the front end to start, if you increase the timeout, it should start correctly: https://github.com/Hyperfoil/Horreum/pull/446/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R111

The second error, are you building in a windows terminal or in wsl? in a windows native terminal this will fail until we have resolved the issues with horreum-api build, integration test will fail as well atm. You don't need them for developing Horreum, i have disabled these 2 modules in the windows build: https://github.com/Hyperfoil/Horreum/blob/master/.github/workflows/main.yml#L18. with -pl '!horreum-client, !horreum-integration'

13 replies

shivam-sharma7 Mar 23, 2023
Collaborator Author

yes, but Quinoa package manager live coding port 3000 is our error.
UI not showing on POR 8000 or 3000

jesperpedersen Mar 23, 2023
Maintainer

What do you mean with "our error" ? The package manager is part of the Quinoa project.

The UI lives on http://localhost:8080/

johnaohara Mar 23, 2023
Maintainer

This error is due to Quinoa timing out starting the UI. The timeout of 120000ms was sufficient on my machine, but you might need to increase it.

johnaohara Mar 23, 2023
Maintainer

The UI will start eventually, in the terminal you can type s to reload the backend after the UI has started working

shivam-sharma7 Mar 23, 2023
Collaborator Author

Sorry, I reloaded but got the same error

jesperpedersen · 2023-03-23T07:31:24Z

jesperpedersen
Mar 23, 2023
Maintainer

@ia3andy Is there something else we can look into ? Any help would be appreciated

11 replies

ia3andy Mar 23, 2023

So from the stack you pasted, it seems you are running from the parent dir, try running it from the backend directory. Also, you need to run npm start in the webapp dir first.

shivam-sharma7 Mar 23, 2023
Collaborator Author

Are you sure you are running mvn quarkus:dev -Dquarkus.quinoa.dev-server.managed=false? because it's not supposed to build anything and not start the dev server. Is it using Quinoa 1.2.7?

Yes. check this one

 Attempting to start live reload endpoint to recover from previous Quarkus startup failure
2023-03-23 20:04:14,253 ERROR [io.qua.dep.dev.IsolatedDevModeMain] (main) Failed to start quarkus: java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
        [error]: Build step io.quarkiverse.quinoa.deployment.ForwardedDevProcessor#prepareDevService threw an exception: java.lang.IllegalStateException: The Web UI dev server (configured as not managed by Quinoa) is not started on port: 3000
        at io.quarkiverse.quinoa.deployment.ForwardedDevProcessor.prepareDevService(ForwardedDevProcessor.java:114)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:909)
        at io.quarkus.builder.BuildContext.run(BuildContext.java:281)
        at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
        at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)
        at java.base/java.lang.Thread.run(Thread.java:829)
        at org.jboss.threads.JBossThread.run(JBossThread.java:501)

        at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment(AugmentActionImpl.java:335)
        at io.quarkus.runner.bootstrap.AugmentActionImpl.createInitialRuntimeApplication(AugmentActionImpl.java:252)
        at io.quarkus.runner.bootstrap.AugmentActionImpl.createInitialRuntimeApplication(AugmentActionImpl.java:60)
        at io.quarkus.deployment.dev.IsolatedDevModeMain.firstStart(IsolatedDevModeMain.java:86)
        at io.quarkus.deployment.dev.IsolatedDevModeMain.accept(IsolatedDevModeMain.java:447)
        at io.quarkus.deployment.dev.IsolatedDevModeMain.accept(IsolatedDevModeMain.java:59)
        at io.quarkus.bootstrap.app.CuratedApplication.runInCl(CuratedApplication.java:149)
        at io.quarkus.bootstrap.app.CuratedApplication.runInAugmentClassLoader(CuratedApplication.java:104)
        at io.quarkus.deployment.dev.DevModeMain.start(DevModeMain.java:131)
        at io.quarkus.deployment.dev.DevModeMain.main(DevModeMain.java:62)
Caused by: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
        [error]: Build step io.quarkiverse.quinoa.deployment.ForwardedDevProcessor#prepareDevService threw an exception: java.lang.IllegalStateException: The Web UI dev server (configured as not managed by Quinoa) is not started on port: 3000
        at io.quarkiverse.quinoa.deployment.ForwardedDevProcessor.prepareDevService(ForwardedDevProcessor.java:114)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:909)
        at io.quarkus.builder.BuildContext.run(BuildContext.java:281)
        at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
        at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)
        at java.base/java.lang.Thread.run(Thread.java:829)
        at org.jboss.threads.JBossThread.run(JBossThread.java:501)

        at io.quarkus.builder.Execution.run(Execution.java:123)
        at io.quarkus.builder.BuildExecutionBuilder.execute(BuildExecutionBuilder.java:79)
        at io.quarkus.deployment.QuarkusAugmentor.run(QuarkusAugmentor.java:160)
        at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment(AugmentActionImpl.java:331)
        ... 9 more
Caused by: java.lang.IllegalStateException: The Web UI dev server (configured as not managed by Quinoa) is not started on port: 3000
        at io.quarkiverse.quinoa.deployment.ForwardedDevProcessor.prepareDevService(ForwardedDevProcessor.java:114)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:909)
        at io.quarkus.builder.BuildContext.run(BuildContext.java:281)
        at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
        at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)
        at java.base/java.lang.Thread.run(Thread.java:829)
        at org.jboss.threads.JBossThread.run(JBossThread.java:501)

2023-03-23 20:04:14,260 ERROR [io.qua.dep.dev.IsolatedDevModeMain] (main) Failed to recover after failed start: java.lang.RuntimeException: java.lang.RuntimeException: Unable to start HTTP server
        at io.quarkus.vertx.http.runtime.VertxHttpRecorder.startServerAfterFailedStart(VertxHttpRecorder.java:281)
        at io.quarkus.vertx.http.runtime.devmode.VertxHttpHotReplacementSetup.handleFailedInitialStart(VertxHttpHotReplacementSetup.java:61)
        at io.quarkus.deployment.dev.RuntimeUpdatesProcessor.startupFailed(RuntimeUpdatesProcessor.java:1139)
        at io.quarkus.deployment.dev.IsolatedDevModeMain.firstStart(IsolatedDevModeMain.java:175)
        at io.quarkus.deployment.dev.IsolatedDevModeMain.accept(IsolatedDevModeMain.java:447)
        at io.quarkus.deployment.dev.IsolatedDevModeMain.accept(IsolatedDevModeMain.java:59)
        at io.quarkus.bootstrap.app.CuratedApplication.runInCl(CuratedApplication.java:149)
        at io.quarkus.bootstrap.app.CuratedApplication.runInAugmentClassLoader(CuratedApplication.java:104)
        at io.quarkus.deployment.dev.DevModeMain.start(DevModeMain.java:131)
        at io.quarkus.deployment.dev.DevModeMain.main(DevModeMain.java:62)
Caused by: java.lang.RuntimeException: Unable to start HTTP server
        at io.quarkus.vertx.http.runtime.VertxHttpRecorder.doServerStart(VertxHttpRecorder.java:770)
        at io.quarkus.vertx.http.runtime.VertxHttpRecorder.startServerAfterFailedStart(VertxHttpRecorder.java:274)
        ... 9 more
Caused by: java.util.concurrent.ExecutionException: io.quarkus.runtime.QuarkusBindException: Port(s) already bound: 8080: Address already in use
        at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
        at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1999)
        at io.quarkus.vertx.http.runtime.VertxHttpRecorder.doServerStart(VertxHttpRecorder.java:736)
        ... 10 more
Caused by: io.quarkus.runtime.QuarkusBindException: Port(s) already bound: 8080: Address already in use
        at io.quarkus.vertx.http.runtime.VertxHttpRecorder$18.handle(VertxHttpRecorder.java:727)
        at io.quarkus.vertx.http.runtime.VertxHttpRecorder$18.handle(VertxHttpRecorder.java:710)
        at io.vertx.core.impl.future.FutureImpl$3.onFailure(FutureImpl.java:153)
        at io.vertx.core.impl.future.FutureBase.emitFailure(FutureBase.java:75)
        at io.vertx.core.impl.future.FutureImpl.tryFail(FutureImpl.java:230)
        at io.vertx.core.impl.future.Mapping.onFailure(Mapping.java:45)
        at io.vertx.core.impl.future.FutureBase.emitFailure(FutureBase.java:75)
        at io.vertx.core.impl.future.FutureImpl.tryFail(FutureImpl.java:230)
        at io.vertx.core.impl.future.PromiseImpl.tryFail(PromiseImpl.java:23)
        at io.vertx.core.impl.future.PromiseImpl.onFailure(PromiseImpl.java:54)
        at io.vertx.core.impl.future.PromiseImpl.handle(PromiseImpl.java:43)
        at io.vertx.core.impl.future.PromiseImpl.handle(PromiseImpl.java:23)
        at io.vertx.core.impl.DeploymentManager.lambda$reportResult$2(DeploymentManager.java:136)
        at io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:264)
        at io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:246)
        at io.vertx.core.impl.EventLoopContext.lambda$runOnContext$0(EventLoopContext.java:43)
        at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174)
        at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167)
        at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
        at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.base/java.lang.Thread.run(Thread.java:829)



--
Press [:] for the terminal, [h] for more options>
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Horreum 0.8-SNAPSHOT:
[INFO] 
[INFO] Horreum ............................................ SUCCESS [  0.324 s]
[INFO] Horreum Model ...................................... SUCCESS [  7.387 s]
[INFO] Horreum Backend .................................... FAILURE [ 36.788 s]
[INFO] Horreum API Generator .............................. SKIPPED
[INFO] Horreum REST API ................................... SKIPPED
[INFO] Horreum Client ..................................... SKIPPED
[INFO] Horreum Integration Tests .......................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  46.282 s
[INFO] Finished at: 2023-03-23T20:04:14+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal io.quarkus:quarkus-maven-plugin:2.16.5.Final:dev (default-cli) on project horreum-backend: Failed to run: Dev mode process did not complete successfully -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :horreum-backend

shivam-sharma7 Mar 23, 2023
Collaborator Author

@ia3andy I think the Quinoa package manager is not listening on port 3000. I tried sudo lsof -i :3000 and not able to see any output to check webapp listening on port 3000 or not

ia3andy Mar 23, 2023

Ok and you can see it from your browser on localhost:3000?

Could you run the quarkus:dev command from the backend directory?

shivam-sharma7 Mar 23, 2023
Collaborator Author

shivamsharma@shivam:/mnt/c/Users/shivam sharma/Desktop/Open-Source/Horreum$ quarkus:dev quarkus:dev:

output: command not found

shivam-sharma7 · 2023-03-23T14:59:39Z

shivam-sharma7
Mar 23, 2023
Collaborator Author

@ia3andy @jesperpedersen @johnaohara
I first run cmd from dirshivamsharma@shivam:/mnt/c/Users/shivam sharma/Desktop/Open-Source/Horreum/webapp$ npm start

And second time run cmd from dir shivamsharma@shivam:/mnt/c/Users/shivam sharma/Desktop/Open-Source/Horreum$ mvn quarkus:dev -Dquarkus.quinoa.dev-server.managed=false

Then It has opened localhost:3000 with the following errors

ERROR in ./node_modules/@patternfly/patternfly/patternfly.css (./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[5].use[1]!./node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[5].use[2]!./node_modules/source-map-loader/dist/cjs.js!./node_modules/@patternfly/patternfly/patternfly.css) 72:37-93
Module not found: Error: Can't resolve './assets/images/pfbg_576.jpg' in '/mnt/c/Users/shivam sharma/Desktop/Open-Source/Horreum/webapp/node_modules/@patternfly/patternfly'
ERROR in ./node_modules/@patternfly/patternfly/patternfly.css (./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[5].use[1]!./node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[5].use[2]!./node_modules/source-map-loader/dist/cjs.js!./node_modules/@patternfly/patternfly/patternfly.css) 73:37-96
Module not found: Error: Can't resolve './assets/images/pfbg_576@2x.jpg' in '/mnt/c/Users/shivam sharma/Desktop/Open-Source/Horreum/webapp/node_modules/@patternfly/patternfly'
ERROR in ./node_modules/@patternfly/patternfly/patternfly.css (./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[5].use[1]!./node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[5].use[2]!./node_modules/source-map-loader/dist/cjs.js!./node_modules/@patternfly/patternfly/patternfly.css) 74:37-93
Module not found: Error: Can't resolve './assets/images/pfbg_768.jpg' in '/mnt/c/Users/shivam sharma/Desktop/Open-Source/Horreum/webapp/node_modules/@patternfly/patternfly'
ERROR in ./node_modules/@patternfly/patternfly/patternfly.css (./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[5].use[1]!./node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[5].use[2]!./node_modules/source-map-loader/dist/cjs.js!./node_modules/@patternfly/patternfly/patternfly.css) 75:37-96
Module not found: Error: Can't resolve './assets/images/pfbg_768@2x.jpg' in '/mnt/c/Users/shivam sharma/Desktop/Open-Source/Horreum/webapp/node_modules/@patternfly/patternfly'
ERROR in ./node_modules/@patternfly/patternfly/patternfly.css (./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[5].use[1]!./node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[5].use[2]!./node_modules/source-map-loader/dist/cjs.js!./node_modules/@patternfly/patternfly/patternfly.css) 76:37-94
Module not found: Error: Can't resolve './assets/images/pfbg_2000.jpg' in '/mnt/c/Users/shivam sharma/Desktop/Open-Source/Horreum/webapp/node_modules/@patternfly/patternfly'

3 replies

ia3andy Mar 23, 2023

And second time run cmd from dir shivamsharma@shivam:/mnt/c/Users/shivam sharma/Desktop/Open-Source/Horreum$ mvn quarkus:dev -Dquarkus.quinoa.dev-server.managed=false

This should be done in the backend directory.

It seems to me you have errors in the webapp so it doesn't start, this is leading to quinoa not able to reach it.

shivam-sharma7 Mar 24, 2023
Collaborator Author

Thanks to John for the self-recorded video on how to set-up horreum in wsl environment, Let me tell you that all cmd works, And I got it successfully set-up it on my machine in wsl environment.

🙌 @johnaohara @jesperpedersen @ia3andy

jesperpedersen Mar 24, 2023
Maintainer

That is great to hear !

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Failed to start quarkus #447

{{title}}

Replies: 3 comments 27 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Failed to start quarkus #447

shivam-sharma7 Mar 22, 2023 Collaborator

Replies: 3 comments · 27 replies

johnaohara Mar 22, 2023 Maintainer

shivam-sharma7 Mar 23, 2023 Collaborator Author

jesperpedersen Mar 23, 2023 Maintainer

johnaohara Mar 23, 2023 Maintainer

johnaohara Mar 23, 2023 Maintainer

shivam-sharma7 Mar 23, 2023 Collaborator Author

jesperpedersen Mar 23, 2023 Maintainer

ia3andy Mar 23, 2023

shivam-sharma7 Mar 23, 2023 Collaborator Author

shivam-sharma7 Mar 23, 2023 Collaborator Author

ia3andy Mar 23, 2023

shivam-sharma7 Mar 23, 2023 Collaborator Author

shivam-sharma7 Mar 23, 2023 Collaborator Author

ia3andy Mar 23, 2023

shivam-sharma7 Mar 24, 2023 Collaborator Author

jesperpedersen Mar 24, 2023 Maintainer

shivam-sharma7
Mar 22, 2023
Collaborator

Replies: 3 comments 27 replies

johnaohara
Mar 22, 2023
Maintainer

shivam-sharma7 Mar 23, 2023
Collaborator Author

jesperpedersen Mar 23, 2023
Maintainer

johnaohara Mar 23, 2023
Maintainer

johnaohara Mar 23, 2023
Maintainer

shivam-sharma7 Mar 23, 2023
Collaborator Author

jesperpedersen
Mar 23, 2023
Maintainer

shivam-sharma7 Mar 23, 2023
Collaborator Author

shivam-sharma7 Mar 23, 2023
Collaborator Author

shivam-sharma7 Mar 23, 2023
Collaborator Author

shivam-sharma7
Mar 23, 2023
Collaborator Author

shivam-sharma7 Mar 24, 2023
Collaborator Author

jesperpedersen Mar 24, 2023
Maintainer