make camel-management a camel-quarkus extension. #1564
Comments
|
I gave an answer to a similar request here: Not sure if we want to have a dedicated |
|
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. |
|
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. |
|
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. |
|
@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 I get hits on the next execution: |
|
You need Camel 3.5.0 for that latest release of camel-quarkus |
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 |
|
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. |
|
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 |
|
Hm..something changed. When I run my dummy project with camel-managment, it works fine. With quarkus (using camel-quarkus-managment), I can see a route, but hawtio does not allow me to open up the details. There is no route diagram, though the tab is visible in hawtio. When on the 'operations' tab and executing 'dumpRouteAsXML', I get: |
|
Which camel-quarkus version is this? Seems to be working ok for me if I invoke |
|
I've uploaded the mini project here: https://github.com/Jeansen/quarkus-camel-dummy. I run it as follows: In IntelliJ with JVM arguments @jamesnetherton If you have time and would have a look, I'd very much appreciate it ;-) |
|
I've not tried to run your app yet. But I see from the pom.xml that you are mixing different Camel & Quarkus versions. Set That should clean up the classpath and hopefully make things work. |
|
Yes, you are right but that should not harm because I run the code directly from within the IDE. I've removed the override and set the version uniformly to 1.11.Final. I've tried different versions, from 1.8 up. But the effect is the same. |
|
Works fine for me in IntelliJ and from the command line. I can only assume that the app classpath in your IDE needs updating. Also, you don't really need class Your |
|
Mhm...bummer. Running the compiled jar via cli works! No I've got to find out what the heck is broken in my IDE ... Thanks for your effort @jamesnetherton . And thank you for the hint above ;-) |
|
@jamesnetherton may I ask how you run it from the IDE? I simply cannot get it to work from within the IDE. Building it and running it from the cli out of the target folder works. But running it as a Java Application always only works half (as described above). Running it as a quarkus application (with the quarkus plugin) does not work for me. Then I do not even see the camel routs at all in hawtio. |
|
I just run right click and select 'Run' on the If you're using IntelliJ, one thing to try is right click on the pom.xml and do: Maven -> Reload Project. That should ensure the dependency tree is up to date. |
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.
The text was updated successfully, but these errors were encountered: