Description of problem: OCP Java Console Camel route Tracing raise exception in pod log and stops camel route processing Version-Release number of selected component (if applicable): openshift-jvm version: 1.0.50 OCP 3.3.1 Steps to Reproduce: 1. Deploy some camel route to OCP (for example s2i-springboot-camel-amq: https://github.com/jboss-fuse/application-templates/blob/application-templates-2.0.fuse-000007/quickstarts/springboot-camel-amq-template.json) 2. Open Java console from pod page 3. Camel tab -> jms-cbr-route -> Tracing 4. Click Start tracing 5. Back to OCP console - pod s2i-springboot-camel-amq-xxxx log 6. You can see excpetions For more detail see the linked issue.
Fix is ready for testing. Please use openshift-jvm v1.0.54.
Please use openshift-jvm v1.0.57
openshift-jvm v1.0.57 should be merged into ocp and is in OCP v3.4.0.34 or newe
verified # openshift version openshift v3.4.0.34+87d9d8d About openshift-jvm Version: 1.0.57 1. initiate karaf-camel-rest-sql-archetype 2. start build s2i-quickstart-karaf-camel-rest-sql $ oc process -f quickstart-template.json -v GIT_REPO=. | oc create -f - $ oc start-build s2i-quickstart-karaf-camel-rest-sql --from-dir=. 3. wait for pods ready $ oc get pod NAME READY STATUS RESTARTS AGE s2i-quickstart-karaf-camel-rest-sql-1-du3zz 1/1 Running 0 16m s2i-quickstart-karaf-camel-rest-sql-2-build 0/1 Completed 0 33m 4. click pod s2i-quickstart-karaf-camel-rest-sql-1-du3zz, then 'Open Java Console' 5. selete 'route1', then 'Trace' -> start trace 6. go back to pod, after 5 minutes, check pods log, no exception is observed.
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-2017:0066