Red Hat Bugzilla – Bug 1371000
Get error "TypeError: e.value.exclude is not a function" when clicking on Threads tab inside Threads console
Last modified: 2016-09-27 05:46:33 EDT
Created attachment 1195183 [details] Screeshot of bug repro Description of problem: Not able to get threads info inside Threads console, get error "TypeError: e.value.exclude is not a function" when clicking on Threads tab Version-Release number of selected component (if applicable): # openshift version openshift v1.3.0-alpha.3+4250e53 kubernetes v1.3.0+507d3a7 etcd 2.3.0+git How reproducible: Always Steps to Reproduce: 1. Login openshift 2. oc new-project test 3. oc new-app --docker-image=docker.io/chunyunchen/java-mainclass:2.3-SNAPSHOT 4. Visit JXM/Threads console after app pod is up Actual results: Not able to get threads info inside Threads console, get error "TypeError: e.value.exclude is not a function" when clicking on Threads tab Expected results: Should be able to get threads info inside Threads console Additional info: 1.Screenshot attached. 2.Issue exist on OSE: # openshift version openshift v3.3.0.26 kubernetes v1.3.0+507d3a7 etcd 2.3.0+git
The Jolokia port needs to be named 'jolokia' so that the link to the Java console shows up in the pod view. Then I confirm I'm able to reproduce the issue. I'm investigating further and keep you posted.
Fixes have been pushed upstream in https://github.com/hawtio/hawtio-jmx/pull/20. Requires a new release of hawtio-jmx then openshift-jvm before updating origin-web-console.
Upgrade of hawtio-jmx pushed with https://github.com/hawtio/openshift-jvm/pull/5. Requires a new release of openshift-jvm.
openshift-jvm version 1.0.47 has just been released and can be integrated in origin-web-console.
merging to origin in https://github.com/openshift/origin/pull/10722
This has been merged into ose and is in OSE v3.3.0.28 or newer.
Verified with openshift v3.3.0.28 kubernetes v1.3.0+507d3a7 etcd 2.3.0+git The threads UI is back with good data. Set to verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1933