Hawtio 1.4.17 does not show a DEBUG button option for my camel routes.
On both the Camel page and on the JMX page.
The Hawtio page states...
Why does the Debug or Trace tab not appear for my Camel route?
The Debug and Trace tabs depend on the JMX MBeans provided by the Camel release you use.
the Debug tab requires at least version 2.12.x or later of your Camel library to be running
the Trace tab requires either a 2.12.x or later distro of Camel or a Fuse distro of Camel from about 2.8 or later
Well, I'm using 2.13.2. So why..?
Can some one help me out here as to why its not shown?
Also reported on the hawtio project here
https://github.com/hawtio/hawtio/issues/1516
You need to select a route first, in the tree before the debug/trace and other sub tabs become active.
Related
I'm running HawtIO (version 2.14.3) within Apache Karaf.
I very frequently use the ActiveMQ table view to inspect the queue sizes etc.
In this version however, the table refreshes so fast that it's hard to use.
It goes like:
Blank screen for 2 seconds
Display the table for 0.5 seconds
Blank screen for 2 seconds
and repeat...
Is there a way to set the refresh interval(or maybe disable it entirely)?
I know that in older versions of HawtIO this was a setting in the UI.
Check out jbertram's comment on disable web console refreshing. Probably it's the same setting for you.
I want to create a sample project to demo Camel routes working with message communication/transformation between two applications. But when I move to palette to create the routes for CamelContext.xml file , I don't find any palette item.
I tried to search how I can get palette install into my Red Hat Jboss developer studio, but no luck.
Please suggest.
Note this will only work if you are working or starting a new Camel project.
Here is some notes on how to show the palette window.
Make sure you have your camel blueprint or spring file selected. As far as I know this will only work for XML DSL. The screenshot below shows the file I am talking about it is normally found under camel contexts. Make sure this opened in the editor by double clicking on it. You should have a visual representation of your camel route on screen.
To show the palette you can active it by using the menu options Windows -> Show View -> Other. Under the general tab you will find Palette. Double click it and open it. The screenshot below shows you what you should see.
I have 10 Camel Components deployed in the same JVM as Hawtio.
Each of these is unique and has different ID.
I can see all 10 via the JMX view, but only 9 via the "Camel" view.
If I remove "1" I can see number "10", instead if I remove "3" I can see "10".
I can't find a reason why a camel route is not shown on the Camel page.
Can someone please give me some direction on how to fnd out the reason for this please.
I've tested on versions , 1.4.17 & 1.4.12
If I use Hawtio to "Destroy" Camel number 10, then it refreshes to show "01".
This helped me view all our routes in Hawtio:
http://camel.465427.n5.nabble.com/Not-all-processors-are-listed-in-JMX-preventing-detailed-route-statistics-profiling-tt5757634.html#a5757647
The solution is to go into HawtIO / Preferences / Jolokia, and change Max
Collection Size from 500 (the default) up to a larger number.
Cheers
I am using Eclipse EE, and tomcat for a webwork, extjs, hibernate spring application. For spring and hibernate staff, I have remote application debugging settings configured. So I make debug. But for extjs, I have installed firebugs in firefox browser in my ubuntu machine, but I still do not know how to catch break point to see how to trace javascript code.
In Firebug, go to the script tab. On the top, you can see:
Inspect | all | <filename>
Click on to choose the file that contain the javascript you want to track. Once you have selected your file, click on a line number to put a brea kpoint (a big red dot will appear).
You can put several break points in different files. The break point will not disappear if you refresh the page (F5).
This tutorial should help you as well.
Actually for Sencha EXT JS I would recommend the excellent App Inspector for Sencha as well. https://chrome.google.com/webstore/detail/app-inspector-for-sencha/pbeapidedgdpniokbedbfbaacglkceae
I am using Java 6 64-bit and STANDALONE Tomcat 6.0.18 on Vista 64-bit. I am working on a web application with struts 1.3.10 and tiles. Now when I make changes to my java or jsp files, they are not visible when I reload the page. I have to manually reload the web application in Tomcat Manager to see the changes. My web app configuration is as follows:
$CATALINA_BASE/conf/Catalina/localhost/dashboard.xml
<Context docBase="D:/mydata/projects/PatchworkSystems/development/Dashboard/webapp"
path="/dashboard"
reloadable="true" antiJARLocking="true" antiResourceLocking="true" debug="1" />
Any help is greatly appreciated.
Thanks
Quadir
Ah, this old chestnut.
I hit this snag on a project back last summer.
It's because of a side effect with having antiResourceLocking="true" set on your context. If you read the documentation on Tomcat here:
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html
"Please note that setting this to true
has some side effects, including the
disabling of JSP reloading in a
running server: see Bugzilla 37668."
which is here:
https://issues.apache.org/bugzilla/show_bug.cgi?id=37668
There is no workaround as far as I know, if you remove the attribute it will allow you automatic loading of yor JSP's again. We set a deploy time subtitution to put the attribute back in for production. Boo, hiss! Anyways if you remove the antiResourceLocking attribute it will solve the problem you're experiencing.
Provide a workaround Apache !!!