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
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 added a field to a Drupal view sort (level 2) and it didn't sort. I got a missing index message when I saved the view. When I enabled the syslog module to see if I could find the problem the recent log messages does not appear in the menu nor if I try to go directly to the page. What can I do to fix this?
Fixed by installing and using db_maintenance module then running cron a few times.
I'm trying to use a custom domain with a static site hosted on AppEngine. Once I get into Google Apps to add the domain, I just get stuck on this page. Basically, I can't get past Step 4 as per the instructions here. I click "Accept" and hit the activate button but the page just refreshes. I spent about a half hour on the phone with "Lewis" from Google phone support and he eventually told me to try App Engine support lol. During the support call we attempted to get this to work multiple times using both the latest Chrome and FF browsers with cookies/cache, etc. cleared.
No reputation, so no screenshot but like I said, the problem is at Step 4 where you have to accept GAE's terms.
Looks like similar problem here. Anyone have the same problem and/or know of a solution? Thanks
You can try other way to activate, like a html page.
I have used this method to activate.
My activated page seems those:
By html to activate => //i.stack.imgur.com/t3nM1.png ;
By operators to activate =>//i.stack.imgur.com/fZTWH.png;
Can you see them?
By the way, I am in China, so, these uploaded images that I can not see them.
I'm new to Drupal, I have a site of version 7.12 that I need to make changes to. A complete relaunch. For that I need to provide a list of all the content type pages that are frequently searched and pages that never got hit so that I can remove them. Is there a way to see that list?
You needed to have the statistics module turned on for drupal to track this information. You can see how to turn it on here:
https://drupal.org/documentation/modules/statistics
Another possible solution is if you had google analytics setup on your site you could see all that information.
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 !!!