Open rhuss opened 9 years ago
Seems that this happens only on Pods with Camel routes (but thats only a feeling)
Maybe try the really simple camel-spring quickstart? It's my usual goto for testing. Be interested to see how that goes.
springboot-camel
works without problems, so it might be some special race condition for fabriq8mq-consumer
and fabriq8mq-controller
.
yay, at least one of 'em works! :-)
BTW, for debugging this kind of thing I'd probably start with the network panel if possible and look at the response back from the jolokia invocations, also maybe double-check that copy/pasting the jolokia URL in the browser location bar gives you a valid response.
When applying the workaround in #4033 and using the fabric8mq-consumer-controller to connect to, the console hangs with this error message:
The tab cannot be closed anymore in Chrome and even closing down the browser doesnt work.
Opening the console again a new tab, shows the following state:
This time the console is responsive, but doesn't show anything.
Restarting the pod result to first state again.
@gashcrumb do you any idea how to continue to debug this ?