[GitHub] [camel-quarkus] Jeansen opened a new issue #1564: make camel-management a camel-quarkus extension.

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] Jeansen opened a new issue #1564: make camel-management a camel-quarkus extension.

GitBox

Jeansen opened a new issue #1564:
URL: https://github.com/apache/camel-quarkus/issues/1564


   In a plain and simple Maven/Camel 3 project, I can - with a dependency of camel-management - easily use hawtio and jolokai to monitor or debug Camel routes. I've tried the same with a simple Quarkus project, but there is no extension for camel-management, yet.
   
   If there are no other ways to access/monitor Camel routs via jolokai and hawtio (that I do not know of, yet), then I'd be happy to see camel-management as an extension, too.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] jamesnetherton commented on issue #1564: make camel-management a camel-quarkus extension.

GitBox

jamesnetherton commented on issue #1564:
URL: https://github.com/apache/camel-quarkus/issues/1564#issuecomment-679108820


   I gave an answer to a similar request here:
   
   https://github.com/hawtio/hawtio/issues/2643#issuecomment-676560836
   
   Not sure if we want to have a dedicated `camel-management` extension as the JMX bits can only work in the normal JVM mode and not natively. @lburgazzoli WDYT?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] Jeansen commented on issue #1564: make camel-management a camel-quarkus extension.

GitBox
In reply to this post by GitBox

Jeansen commented on issue #1564:
URL: https://github.com/apache/camel-quarkus/issues/1564#issuecomment-679399848


   Well, even if it is only a solution for the JVM mode, I think during development it is quite helpful to have something like hawtio be accessible. Later on, in native mode, I do not think it is that relevant. But even if we could get the routs visualizations to work in native mode, it would - IMHO - be better, than nothing.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] davsclaus commented on issue #1564: make camel-management a camel-quarkus extension.

GitBox
In reply to this post by GitBox

davsclaus commented on issue #1564:
URL: https://github.com/apache/camel-quarkus/issues/1564#issuecomment-679619126


   I think its a good idea, we should add in its documentation that native mode is not supported as JMX itself is not supported there. So some extensions would be JVM mode only (there is also camel-jmx etc).
   
   We do have today a way in the catalog to mark the extension as JVM only.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] lburgazzoli commented on issue #1564: make camel-management a camel-quarkus extension.

GitBox
In reply to this post by GitBox

lburgazzoli commented on issue #1564:
URL: https://github.com/apache/camel-quarkus/issues/1564#issuecomment-679831394


   I don't think having an extension for camel-management would be a huge issue however I'd like to know more about the use case especially as it seems the main use case here seems to be relate to dev experience.
   
   In general I don't think traditional monitoring solution based on jmx are the right thing for camel-quarkus as the target is the cloud and containerized workload and exposing jmx is IMHO not the best.
   
   In my spare time I'm working with a colleague to see if we can have a standardized (under MicroProfile or SmallRye) way of exposing a similar experience but via plain REST endpoints (similar to the spring-boot actuators) so you can easily control who has access to what using the same technology you'd use to protect any REST endpoint.
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] jamesnetherton closed issue #1564: make camel-management a camel-quarkus extension.

GitBox
In reply to this post by GitBox

jamesnetherton closed issue #1564:
URL: https://github.com/apache/camel-quarkus/issues/1564


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] Jeansen commented on issue #1564: make camel-management a camel-quarkus extension.

GitBox
In reply to this post by GitBox

Jeansen commented on issue #1564:
URL: https://github.com/apache/camel-quarkus/issues/1564#issuecomment-693240490


   @jamesnetherton  Looks like there is a regeression, or I am doing something wrong.
   
   I've created a simple Quarkus-Projekt in IntelliJ. Actually, IntelliJ creates this for you, so there is no special setup from my side. When creating the project, I also added the the 'camel-core' dependency. Then I tested the project without any problem. But as soon as I add the following maven dependency
   
   ```
           <dependency>
               <groupId>org.apache.camel.quarkus</groupId>
               <artifactId>camel-quarkus-management</artifactId>
               <version>1.1.0</version>
           </dependency>
   ```
   
   I get hits on the next execution:
   
   ```
   /home/marcel/.sdkman/candidates/java/12.0.2-open/bin/java -javaagent:/home/marcel/opt/ideaIU/lib/idea_rt.jar=41467:/home/marcel/opt/ideaIU/bin -Dfile.encoding=UTF-8 -classpath /tmp/demo2/target/classes:/home/marcel/.m2/repository/io/quarkus/quarkus-resteasy/1.7.3.Final/quarkus-resteasy-1.7.3.Final.jar:/home/marcel/.m2/repository/io/quarkus/quarkus-vertx-http/1.7.3.Final/quarkus-vertx-http-1.7.3.Final.jar:/home/marcel/.m2/repository/io/quarkus/quarkus-security-runtime-spi/1.7.3.Final/quarkus-security-runtime-spi-1.7.3.Final.jar:/home/marcel/.m2/repository/io/quarkus/security/quarkus-security/1.1.2.Final/quarkus-security-1.1.2.Final.jar:/home/marcel/.m2/repository/io/smallrye/reactive/mutiny/0.7.0/mutiny-0.7.0.jar:/home/marcel/.m2/repository/org/reactivestreams/reactive-streams/1.0.3/reactive-streams-1.0.3.jar:/home/marcel/.m2/repository/jakarta/enterprise/jakarta.enterprise.cdi-api/2.0.2/jakarta.enterprise.cdi-api-2.0.2.jar:/home/marcel/.m2/repository/jakarta/el/jakarta.el-api/3.0.
 3/jakarta.el-api-3.0.3.jar:/home/marcel/.m2/repository/jakarta/interceptor/jakarta.interceptor-api/1.2.5/jakarta.interceptor-api-1.2.5.jar:/home/marcel/.m2/repository/io/quarkus/quarkus-vertx-core/1.7.3.Final/quarkus-vertx-core-1.7.3.Final.jar:/home/marcel/.m2/repository/io/quarkus/quarkus-netty/1.7.3.Final/quarkus-netty-1.7.3.Final.jar:/home/marcel/.m2/repository/io/netty/netty-codec/4.1.49.Final/netty-codec-4.1.49.Final.jar:/home/marcel/.m2/repository/io/netty/netty-handler/4.1.49.Final/netty-handler-4.1.49.Final.jar:/home/marcel/.m2/repository/io/vertx/vertx-core/3.9.2/vertx-core-3.9.2.jar:/home/marcel/.m2/repository/io/netty/netty-common/4.1.49.Final/netty-common-4.1.49.Final.jar:/home/marcel/.m2/repository/io/netty/netty-buffer/4.1.49.Final/netty-buffer-4.1.49.Final.jar:/home/marcel/.m2/repository/io/netty/netty-transport/4.1.49.Final/netty-transport-4.1.49.Final.jar:/home/marcel/.m2/repository/io/netty/netty-handler-proxy/4.1.49.Final/netty-handler-proxy-4.1.49.Final.jar:/home
 /marcel/.m2/repository/io/netty/netty-codec-socks/4.1.49.Final/netty-codec-socks-4.1.49.Final.jar:/home/marcel/.m2/repository/io/netty/netty-codec-http/4.1.49.Final/netty-codec-http-4.1.49.Final.jar:/home/marcel/.m2/repository/io/netty/netty-codec-http2/4.1.49.Final/netty-codec-http2-4.1.49.Final.jar:/home/marcel/.m2/repository/io/netty/netty-resolver/4.1.49.Final/netty-resolver-4.1.49.Final.jar:/home/marcel/.m2/repository/io/netty/netty-resolver-dns/4.1.49.Final/netty-resolver-dns-4.1.49.Final.jar:/home/marcel/.m2/repository/io/netty/netty-codec-dns/4.1.49.Final/netty-codec-dns-4.1.49.Final.jar:/home/marcel/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.11.2/jackson-core-2.11.2.jar:/home/marcel/.m2/repository/io/vertx/vertx-web/3.9.2/vertx-web-3.9.2.jar:/home/marcel/.m2/repository/io/vertx/vertx-web-common/3.9.2/vertx-web-common-3.9.2.jar:/home/marcel/.m2/repository/io/vertx/vertx-auth-common/3.9.2/vertx-auth-common-3.9.2.jar:/home/marcel/.m2/repository/io/vertx/vertx-bri
 dge-common/3.9.2/vertx-bridge-common-3.9.2.jar:/home/marcel/.m2/repository/io/quarkus/quarkus-resteasy-server-common/1.7.3.Final/quarkus-resteasy-server-common-1.7.3.Final.jar:/home/marcel/.m2/repository/io/quarkus/quarkus-resteasy-common/1.7.3.Final/quarkus-resteasy-common-1.7.3.Final.jar:/home/marcel/.m2/repository/org/jboss/resteasy/resteasy-core/4.5.6.Final/resteasy-core-4.5.6.Final.jar:/home/marcel/.m2/repository/org/jboss/spec/javax/ws/rs/jboss-jaxrs-api_2.1_spec/2.0.1.Final/jboss-jaxrs-api_2.1_spec-2.0.1.Final.jar:/home/marcel/.m2/repository/org/jboss/spec/javax/xml/bind/jboss-jaxb-api_2.3_spec/2.0.0.Final/jboss-jaxb-api_2.3_spec-2.0.0.Final.jar:/home/marcel/.m2/repository/org/jboss/resteasy/resteasy-core-spi/4.5.6.Final/resteasy-core-spi-4.5.6.Final.jar:/home/marcel/.m2/repository/com/ibm/async/asyncutil/0.1.0/asyncutil-0.1.0.jar:/home/marcel/.m2/repository/com/sun/activation/jakarta.activation/1.2.1/jakarta.activation-1.2.1.jar:/home/marcel/.m2/repository/jakarta/validation
 /jakarta.validation-api/2.0.2/jakarta.validation-api-2.0.2.jar:/home/marcel/.m2/repository/io/quarkus/quarkus-core/1.7.3.Final/quarkus-core-1.7.3.Final.jar:/home/marcel/.m2/repository/jakarta/annotation/jakarta.annotation-api/1.3.5/jakarta.annotation-api-1.3.5.jar:/home/marcel/.m2/repository/jakarta/inject/jakarta.inject-api/1.0/jakarta.inject-api-1.0.jar:/home/marcel/.m2/repository/io/quarkus/quarkus-ide-launcher/1.7.3.Final/quarkus-ide-launcher-1.7.3.Final.jar:/home/marcel/.m2/repository/io/smallrye/config/smallrye-config/1.8.5/smallrye-config-1.8.5.jar:/home/marcel/.m2/repository/io/smallrye/common/smallrye-common-annotation/1.1.0/smallrye-common-annotation-1.1.0.jar:/home/marcel/.m2/repository/io/smallrye/config/smallrye-config-common/1.8.5/smallrye-config-common-1.8.5.jar:/home/marcel/.m2/repository/io/smallrye/common/smallrye-common-expression/1.1.0/smallrye-common-expression-1.1.0.jar:/home/marcel/.m2/repository/io/smallrye/common/smallrye-common-function/1.1.0/smallrye-commo
 n-function-1.1.0.jar:/home/marcel/.m2/repository/io/smallrye/common/smallrye-common-constraint/1.1.0/smallrye-common-constraint-1.1.0.jar:/home/marcel/.m2/repository/org/jboss/logging/jboss-logging/3.3.2.Final/jboss-logging-3.3.2.Final.jar:/home/marcel/.m2/repository/org/jboss/logmanager/jboss-logmanager-embedded/1.0.4/jboss-logmanager-embedded-1.0.4.jar:/home/marcel/.m2/repository/org/jboss/logging/jboss-logging-annotations/2.1.0.Final/jboss-logging-annotations-2.1.0.Final.jar:/home/marcel/.m2/repository/org/jboss/threads/jboss-threads/3.1.1.Final/jboss-threads-3.1.1.Final.jar:/home/marcel/.m2/repository/org/slf4j/slf4j-api/1.7.30/slf4j-api-1.7.30.jar:/home/marcel/.m2/repository/org/jboss/slf4j/slf4j-jboss-logging/1.2.0.Final/slf4j-jboss-logging-1.2.0.Final.jar:/home/marcel/.m2/repository/org/graalvm/sdk/graal-sdk/20.1.0/graal-sdk-20.1.0.jar:/home/marcel/.m2/repository/org/wildfly/common/wildfly-common/1.5.4.Final-format-001/wildfly-common-1.5.4.Final-format-001.jar:/home/marcel/.m
 2/repository/io/quarkus/quarkus-bootstrap-runner/1.7.3.Final/quarkus-bootstrap-runner-1.7.3.Final.jar:/home/marcel/.m2/repository/org/apache/camel/quarkus/camel-quarkus-core/1.0.0/camel-quarkus-core-1.0.0.jar:/home/marcel/.m2/repository/io/quarkus/quarkus-arc/1.7.3.Final/quarkus-arc-1.7.3.Final.jar:/home/marcel/.m2/repository/io/quarkus/arc/arc/1.7.3.Final/arc-1.7.3.Final.jar:/home/marcel/.m2/repository/jakarta/transaction/jakarta.transaction-api/1.3.3/jakarta.transaction-api-1.3.3.jar:/home/marcel/.m2/repository/org/eclipse/microprofile/context-propagation/microprofile-context-propagation-api/1.0.1/microprofile-context-propagation-api-1.0.1.jar:/home/marcel/.m2/repository/org/apache/camel/quarkus/camel-quarkus-support-common/1.0.0/camel-quarkus-support-common-1.0.0.jar:/home/marcel/.m2/repository/io/quarkus/quarkus-development-mode-spi/1.7.3.Final/quarkus-development-mode-spi-1.7.3.Final.jar:/home/marcel/.m2/repository/org/apache/camel/camel-core-engine/3.4.2/camel-core-engine-3.4.
 2.jar:/home/marcel/.m2/repository/org/apache/camel/camel-api/3.4.2/camel-api-3.4.2.jar:/home/marcel/.m2/repository/org/apache/camel/camel-management-api/3.4.2/camel-management-api-3.4.2.jar:/home/marcel/.m2/repository/org/apache/camel/camel-support/3.4.2/camel-support-3.4.2.jar:/home/marcel/.m2/repository/org/apache/camel/camel-util/3.4.2/camel-util-3.4.2.jar:/home/marcel/.m2/repository/org/apache/camel/camel-base/3.4.2/camel-base-3.4.2.jar:/home/marcel/.m2/repository/org/apache/camel/camel-core-languages/3.4.2/camel-core-languages-3.4.2.jar:/home/marcel/.m2/repository/org/apache/camel/camel-endpointdsl/3.4.2/camel-endpointdsl-3.4.2.jar:/home/marcel/.m2/repository/org/apache/camel/camel-componentdsl/3.4.2/camel-componentdsl-3.4.2.jar:/home/marcel/.m2/repository/org/apache/camel/camel-core-catalog/3.4.2/camel-core-catalog-3.4.2.jar:/home/marcel/.m2/repository/org/apache/camel/camel-tooling-model/3.4.2/camel-tooling-model-3.4.2.jar:/home/marcel/.m2/repository/org/apache/camel/camel-ut
 il-json/3.4.2/camel-util-json-3.4.2.jar:/home/marcel/.m2/repository/org/apache/camel/camel-microprofile-config/3.4.2/camel-microprofile-config-3.4.2.jar:/home/marcel/.m2/repository/org/eclipse/microprofile/config/microprofile-config-api/1.4/microprofile-config-api-1.4.jar com.example.Main
   __  ____  __  _____   ___  __ ____  ______
    --/ __ \/ / / / _ | / _ \/ //_/ / / / __/
    -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \  
   --\___\_\____/_/ |_/_/|_/_/|_|\____/___/  
   2020-09-16 09:54:46,445 INFO  [org.apa.cam.qua.cor.CamelBootstrapRecorder] (Quarkus Main Thread) bootstrap runtime: org.apache.camel.quarkus.core.CamelContextRuntime
   2020-09-16 09:54:46,512 INFO  [org.apa.cam.man.JmxManagementStrategy] (Quarkus Main Thread) JMX is enabled
   2020-09-16 09:54:46,554 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (Quarkus Main Thread) Apache Camel 3.4.2 (camel-1) is starting
   2020-09-16 09:54:46,555 ERROR [io.qua.application] (Quarkus Main Thread) Failed to start application (with profile dev): java.lang.AbstractMethodError: Receiver class org.apache.camel.management.JmxManagementLifecycleStrategy does not define or inherit an implementation of the resolved method abstract onContextStart(Lorg/apache/camel/CamelContext;)V of interface org.apache.camel.spi.LifecycleStrategy.
    at org.apache.camel.impl.engine.AbstractCamelContext.doStartCamel(AbstractCamelContext.java:2728)
    at org.apache.camel.impl.engine.AbstractCamelContext.doStartContext(AbstractCamelContext.java:2657)
    at org.apache.camel.impl.engine.AbstractCamelContext.doStart(AbstractCamelContext.java:2620)
    at org.apache.camel.support.service.BaseService.start(BaseService.java:115)
    at org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2452)
    at org.apache.camel.quarkus.core.CamelContextRuntime.start(CamelContextRuntime.java:57)
    at org.apache.camel.quarkus.core.CamelBootstrapRecorder.start(CamelBootstrapRecorder.java:45)
    at io.quarkus.deployment.steps.CamelBootstrapProcessor$boot-173480958.deploy_0(CamelBootstrapProcessor$boot-173480958.zig:101)
    at io.quarkus.deployment.steps.CamelBootstrapProcessor$boot-173480958.deploy(CamelBootstrapProcessor$boot-173480958.zig:40)
    at io.quarkus.runner.ApplicationImpl.doStart(ApplicationImpl.zig:708)
    at io.quarkus.runtime.Application.start(Application.java:90)
    at io.quarkus.runtime.ApplicationLifecycleManager.run(ApplicationLifecycleManager.java:91)
    at io.quarkus.runtime.Quarkus.run(Quarkus.java:61)
    at io.quarkus.runtime.Quarkus.run(Quarkus.java:38)
    at io.quarkus.runtime.Quarkus.run(Quarkus.java:106)
    at com.example.Main.main(Main.java:9)
    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:567)
    at io.quarkus.runner.bootstrap.StartupActionImpl$3.run(StartupActionImpl.java:145)
    at java.base/java.lang.Thread.run(Thread.java:835)
   
   2020-09-16 09:54:46,557 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (Quarkus Main Thread) Apache Camel 3.4.2 (camel-1) is shutting down
   2020-09-16 09:54:46,562 WARN  [org.apa.cam.imp.eng.AbstractCamelContext] (Quarkus Main Thread) Error occurred while stopping lifecycle strategies. This exception will be ignored.: java.lang.AbstractMethodError: Receiver class org.apache.camel.management.JmxManagementLifecycleStrategy does not define or inherit an implementation of the resolved method abstract onContextStop(Lorg/apache/camel/CamelContext;)V of interface org.apache.camel.spi.LifecycleStrategy.
    at org.apache.camel.impl.engine.AbstractCamelContext.doStop(AbstractCamelContext.java:2909)
    at org.apache.camel.support.service.BaseService.stop(BaseService.java:155)
    at org.apache.camel.quarkus.core.CamelContextRuntime.stop(CamelContextRuntime.java:62)
    at org.apache.camel.quarkus.core.CamelBootstrapRecorder$1.run(CamelBootstrapRecorder.java:33)
    at io.quarkus.runtime.StartupContext.runAllInReverseOrder(StartupContext.java:83)
    at io.quarkus.runtime.StartupContext.close(StartupContext.java:72)
    at io.quarkus.runner.ApplicationImpl.doStart(ApplicationImpl.zig:786)
    at io.quarkus.runtime.Application.start(Application.java:90)
    at io.quarkus.runtime.ApplicationLifecycleManager.run(ApplicationLifecycleManager.java:91)
    at io.quarkus.runtime.Quarkus.run(Quarkus.java:61)
    at io.quarkus.runtime.Quarkus.run(Quarkus.java:38)
    at io.quarkus.runtime.Quarkus.run(Quarkus.java:106)
    at com.example.Main.main(Main.java:9)
    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:567)
    at io.quarkus.runner.bootstrap.StartupActionImpl$3.run(StartupActionImpl.java:145)
    at java.base/java.lang.Thread.run(Thread.java:835)
   
   2020-09-16 09:54:46,570 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (Quarkus Main Thread) Apache Camel 3.4.2 (camel-1) uptime 0.015 seconds
   2020-09-16 09:54:46,571 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (Quarkus Main Thread) Apache Camel 3.4.2 (camel-1) is shutdown in 0.014 seconds
   Quarkus application exited with code 1
   Press Enter to restart or Ctrl + C to quit
   2020-09-16 09:54:46,870 INFO  [io.qua.dep.dev.IsolatedDevModeMain] (main) Attempting to start hot replacement endpoint to recover from previous Quarkus startup failure
   
   
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] davsclaus commented on issue #1564: make camel-management a camel-quarkus extension.

GitBox
In reply to this post by GitBox

davsclaus commented on issue #1564:
URL: https://github.com/apache/camel-quarkus/issues/1564#issuecomment-693241084


   You need Camel 3.5.0 for that latest release of camel-quarkus


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] ppalaga commented on issue #1564: make camel-management a camel-quarkus extension.

GitBox
In reply to this post by GitBox

ppalaga commented on issue #1564:
URL: https://github.com/apache/camel-quarkus/issues/1564#issuecomment-693279365


   > ```
   >         <dependency>
   >             <groupId>org.apache.camel.quarkus</groupId>
   >             <artifactId>camel-quarkus-management</artifactId>
   >             <version>1.1.0</version>
   >         </dependency>
   > ```
   
   I guess you are mixing camel-quarkus-management 1.1.0 with an older camel quarkus artifacts.
   
   Not sure what exactly IJ generates for you, but since yesterday, you can import `io.quarkus:quarkus-universe-bom:1.8.0.Final` that manages also `camel-quarkus-management` so you can have the dep without version
   
   ```
           <dependency>
               <groupId>org.apache.camel.quarkus</groupId>
               <artifactId>camel-quarkus-management</artifactId>
           </dependency>
   ```
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] Jeansen commented on issue #1564: make camel-management a camel-quarkus extension.

GitBox
In reply to this post by GitBox

Jeansen commented on issue #1564:
URL: https://github.com/apache/camel-quarkus/issues/1564#issuecomment-693318381


   My bad. It was still set to quarkus 1.7.3. With 1.8.0 it now works. Side note: Even with explicit versions for the core and management dependencies, it does not work. But it looks fine now with the dummy project.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] Jeansen commented on issue #1564: make camel-management a camel-quarkus extension.

GitBox
In reply to this post by GitBox

Jeansen commented on issue #1564:
URL: https://github.com/apache/camel-quarkus/issues/1564#issuecomment-693330292


   OK, great. I've had success in running Quarkus with jolokia and hawtio in JVM mode and see the generated graph of a route. Thank you @jamesnetherton


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-quarkus] Jeansen edited a comment on issue #1564: make camel-management a camel-quarkus extension.

GitBox
In reply to this post by GitBox

Jeansen edited a comment on issue #1564:
URL: https://github.com/apache/camel-quarkus/issues/1564#issuecomment-693330292


   OK, great. I've had success in running Quarkus with jolokia in JVM mode and see the generated graph of a route with hawtio. Thank you @jamesnetherton


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[hidden email]