Description of problem: JavaScript errors in Camel-Profile tab in openshift-jvm console Version-Release number of selected component (if applicable): Version: 1.0.52 openshift v3.4.0.25+1f36858 How reproducible: always Steps to Reproduce: 1. Deploy some camel route to OCP (for example s2i-springboot-camel-amq: s2i-quickstart-java-camel-spring 2. Open Java console from pod page 3. Camel tab -> cbr-route -> Profile 4. Open Web console in Firefox 5. You can see java script errors [openshift-jvm] started, version: 1.0.52libs-d99ee5b076.js:9:8800 [openshift-jvm] commit ID: 413f4afe57c2067e3ca527b4991a2fc2100bba4alibs-d99ee5b076.js:9:8800 Lazy loading folder cbr-routelibs-d99ee5b076.js:52:25789 browse thinks the height is only 20 so calculating offset from doc heightlibs-d99ee5b076.js:64:21911 Acyclic Phase time: 1mslibs-d99ee5b076.js:50:17074 Rank Phase time: 4mslibs-d99ee5b076.js:50:17074 Order Phase time: 5mslibs-d99ee5b076.js:50:17074 Position Phase time: 6mslibs-d99ee5b076.js:50:17074 Total layout time: 18mslibs-d99ee5b076.js:50:17074 [Threads] Thread contention monitoring not enabled, enablinglibs-d99ee5b076.js:9:8800 [Threads] Enabled contention monitoringlibs-d99ee5b076.js:9:8800 [Threads] Disabled contention monitoring: truelibs-d99ee5b076.js:9:8800 Lazy loading folder cbr-routelibs-d99ee5b076.js:52:25789 [Threads] Thread contention monitoring not enabled, enablinglibs-d99ee5b076.js:9:8800 [Threads] Enabled contention monitoringlibs-d99ee5b076.js:9:8800 [Threads] Disabled contention monitoring: truelibs-d99ee5b076.js:9:8800 Error in parsing value for 'right'. Declaration dropped.charts [Threads] Thread contention monitoring not enabled, enablinglibs-d99ee5b076.js:9:8800 [Threads] Enabled contention monitoringlibs-d99ee5b076.js:9:8800 [Threads] Disabled contention monitoring: truelibs-d99ee5b076.js:9:8800 Lazy loading folder cbr-routelibs-d99ee5b076.js:52:25789 not well-formed(unknown) [Core] Operation unknown failed due to: java.lang.IllegalArgumentException : Objectname can not be nulllibs-d99ee5b076.js:9:8800 [CamelTracer] Re-activating tracer with 0 existing messageslibs-d99ee5b076.js:9:8800 Loading Camel route profile data...libs-d99ee5b076.js:66:14850 Lazy loading folder cbr-routelibs-d99ee5b076.js:52:25789 not well-formed(unknown) Actual results: Profile won't load, and can see error in Firefox console. Expected results: no error Additional info:
I'm unable to reproduce it on the spring-boot-camel-rest-sql quickstart. The profile data loads and refreshes correctly with version 1.0.52. On Firefox, I can see the 'not well-formed' log message though that doesn't affect the profile data from being loaded. I still need to dig further in order to be able to reproduce the following error log: [Core] Operation unknown failed due to: java.lang.IllegalArgumentException : Objectname can not be null Looking at the complete set of logs, I see the following logs being emitted that correspond to the tracer tab: browse thinks the height is only 20 so calculating offset from doc height Acyclic Phase time: 1ms Rank Phase time: 4ms Order Phase time: 5ms Position Phase time: 6ms Total layout time: 18ms [CamelTracer] Re-activating tracer with 0 existing messages It may indicate that the tracer tab is being activated. So I'm not sure I understand the reproduction steps correctly: what is exactly to be done at step 4, re-opening the OpenShift console? 2. Open Java console from pod page 3. Camel tab -> cbr-route -> Profile 4. Open Web console in Firefox 5. You can see java script errors
java.lang.IllegalArgumentException is a Java exception, therefore something is wrong on the server side. I would like to suggest testing with different Camel routes to make sure the problem isn't related to the Camel route originally used in this test.
Please follow the steps below to capture some information for me: 1. Open the Developer Tools by pressing F12 2. Go to the Network tab 3. Select a Camel route on the tree and go to the Profile tab 4. Inspect the request sent when going to the Profile Tab and take note of the request URL and request body
Created attachment 1221491 [details] screenshot
tried with karaf-camel-rest-sql-archetype, the Profile could be loaded as shown in the screenshot.