HawtIO shows the trace tab for my camel context, and when I run trace it shows messages counting up on the diagram. However, I never see any messages in the message table at the bottom. I'm using Camel 2.8.0-fuse-07-16. Thanks for any help.
You need a newer version of Camel to support tracing from hawtio. I think you would need the Camel version from JBoss Fuse 6.0 or better.
Related
Well, I decided to hack my own IDEA debugger plugin for Apache Camel. I found some info about the BacklogDebugger feature, but I guess I don't really understand how to use it. What puzzles me is how do I get any notification of the breakpoint reached in the running Camel application. Is there any way to add event listeners to the BacklogDebugger? Or is there any other feature for that?
I couldn't find any examples of how the BacklogDebugger is used.
The Hawtio Camel plugin uses BacklogDebugger for its Camel route debugging page.
It polls the getDebugCounter method to see if there are any new debugged messages and from there it figures out if any breakpoints were hit and retrieves the message exchange content.
You can try to decipher the TypeScript code for inspiration:
https://github.com/hawtio/hawtio-integration/blob/master/plugins/camel/ts/debug/debug.controller.ts
The Eclipse Desktop Fuse Tooling is also using it. As it is written in Java, it migth be easier to translate for IntelliJ IDEA plugin.
See https://github.com/jbosstools/jbosstools-fuse/tree/jbosstools-4.21.0.Final/editor/plugins/org.fusesource.ide.launcher/src/org/fusesource/ide/launcher/debug
On upgrading to Camel 3.3 we came accorss an issue while testing. So, if we restart our camel application while there are multiple messages in the queue for some reason a few messages are getting stuck in an "unacknowledged" state on the solace queue and after the appliation comes back up it doesn't consume those messages. We need to resart the application once more before they get consumed.
This issues only seems to occur only when there are a large number of messages in the queue at the time of restart.
We have not been able to recreate the issue on Camel 2.x versions.
The application is correctly setup to AUTO_ACKNOWLEDGE and it works normally in all other circumstances.
"acceptMessagesWhileStopping" is set to false.
We haven't seen any message loss or duplication.
We went through all the setup and configuration that happens at startup and we haven't found any issues with either the setup or configuration. I am not sure how to go about with debugging this as this is a shutdown related issue that too while messages are in the process of consumption. Any advice on how to go forward would be helpful. Regards.
P.S. I have gone through the Camel 3 migration guides. I didn't find anything pertinent to the issue there.
Newer versions of camel 3 doesn't seem to have this issue.
I have been working with Jboss Fuse 6.1.0.redhat-379 for about a month with great results and higher productivity in EIP. Thank you very much to the community for building such a great product.
Now I am getting ready to deploy my bundles in a dev enviroment with several camel routes and even multiple camel contexts in a single bundle and I'm noticing a weird behavior regarding camel contexts JMX display. The bundle with the multiple camel contexts is only showing the first context, others contexts work fine but they are missing in camel JMX display in hawtio.
After research about this behavior I encountered with this JIRA issue https://issues.apache.org/jira/browse/CAMEL-7545 opened by Claus, describing exactly this problem and manifesting that there are Fix Versions (2.12.4, 2.13.2, 2.14.0)
AFAIK my Jboss Fuse version is distributed with camel 2.12.0.redhat-610379 version and there is a mayor 2.14.0.redhat-620031 version that supposedly will fix this issue and it will be bring many other features like json path and sql generated keys.
Is there a way to upgrade versions of camel features in Jboss Fuse?
UPDATE
There is a similar question for this topic (Updating camel version in fuse esb) accepted answer discourages trying to update the version, however, I think it should be better to permit version upgrades if they fix issues
Not a 100% on this but the rollup patches might include the 2.12 fixed versions. Install the latest patch and see if that fixes the issue.
i want to install the apache camel tools for eclipse: http://tools.jboss.org/features/apachecamel.html
But how to install/ where to find camel tools? I tried to install JBoss Tools from eclipse marketplace but didn't find camel on selection screen. (don't want all tools)
I also tried the update site mentioned here http://tools.jboss.org/blog/2014-04-14-JBTIS-4.html but the only "camel" thing is "JBoss Fuse Camel Editor Feature" is this it?
Besides the visualizing of routes i want to see jmx stuff that is exposed by my camel app.
The blog entry from Paul Leacu provides the correct information. There are currently 3 features which are named like "JBoss Fuse ...".
The Camel Editor feature provides the editor for designing your Camel Routes and to launch them on your local machine.
Then there is the Fuse Server Adapter feature which provides some server adapters for starting / stopping / installing Apache ServiceMix, Apache Karaf and JBoss Fuse servers.
Finally there is the Fuse Runtime feature which provides the JMX stuff you are looking for and the Fabric related functionality.
I made a short install guide on how to install JBoss Fuse Tooling without JBDS and/or the integration stack. You can find the guide here.
Hi I would like to know which camel version is used in Fuse esb (jboss-fuse-6.0.0.redhat-024),
according to the migration guide it's 2.10.0 .
how can I update it to use 2.10.5 ?
JBoss fuse is using customer version of Camel which is based on the Camel 2.10.x branch.
As there are lots other projects which may relates to this Camel version, I don't suggest you to change the version yourself.