Red Hat Bugzilla – Bug 1287078
Camel Hawt.io console hangs in Firefox with karaf-camel-amq quickstart
Last modified: 2016-09-07 17:13:53 EDT
Description of problem:
After deploying of the Karaf Amq Quickstart
Using the 'connect' button in the OpenShift Console to open the karaf-camel-amq pod in Firefox, the view hangs.
Version-Release number of selected component (if applicable):
Using Karaf image
Using A-MQ image
Steps to Reproduce:
1. Deploy the quickstart from
(change the mentioned images to use the current RCM images mentioned above)
2. Open OpenShift console, locate the karaf-camel-amq Pod, use the "Connect" link to connect to the container Hawt.io
3. Notice the console appears to be hanging
Console is stuck in an empty list of camel routes
3 routes should immediately appear.
This seems to work properly with Google Chrome. Also, and more interestingly, when the view is stuck in Firefox, opening the same view in Chrome make the Firefox view unstuck... pretty hardcore stuff...
Just to clarify, if you click on another item in the JMX tree and then back on "Routes" do they show up then? Am seeing here on Firefox only that a fair number of views don't show up on the initial page load, whereas they do on Google Chrome and am wondering if this is actually the same general problem.
Just pushed this fix which fixes the issue I've been seeing, which sounds like the same issue:
Will pull this into a new openshift-jvm release after I've done a bit of layout work on a few pages.
After reproducing this multiple times on two different instances:
* This does not seem to happen always after all. It seem to be more likely to happen with a slower master (on OS1 internal openstack rather than an OSE instance on bare metal) or when the master is under load (but I don't really have enough data to be sure)
Moving to low since Stan isn't able to reproduce this
Have reproduced this and am currently investigating
Tracked down a couple sync calls being made, reworked that. There seems to be a general issue with that quickstart but maybe it's just my environment, in any case it's issues made it reliably reproduce for me :-)
Anyways, the related fixes are below, will get a PR to get this into openshift early next week after maybe getting another fix or two in.
hawtio-integration => https://github.com/hawtio/hawtio-integration/commit/72a2f0d15f77fa900dfe1ea79d7502a8d06ee386
hawtio-jmx => https://github.com/hawtio/hawtio-jmx/commit/aed2c1b61793ce499266902bde6b72c37279f9af
which went into this openshift-jvm version:
PR => https://github.com/openshift/origin/pull/6938
Verified on current 3.2 Puddle
(openshift-jvm Version: 1.0.42 Commit ID: d46658f96d3134f99b0b6073433d4366defaee0f )