Bug 1401509

Summary:	Java Console Tracing raise exception in pod log (stop camel route)
Product:	OpenShift Container Platform	Reporter:	David Simansky <dsimansk>
Component:	Management Console	Assignee:	Alexandre Kieling <abrianik>
Status:	CLOSED ERRATA	QA Contact:	Peng Li <penli>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.3.1	CC:	aos-bugs, jforrest, jokerman, mmccomas, tdawson
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Bug in the communication between Web console and Jolokia endpoint Consequence: When activating tracing, an error happens on the server Fix: Change the default value of Apache Camel configuration Result: Error stops happening	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-18 12:57:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Simansky 2016-12-05 13:20:20 UTC

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.

Comment 1 Alexandre Kieling 2016-12-07 20:13:32 UTC

Fix is ready for testing. Please use openshift-jvm v1.0.54.

Comment 2 Alexandre Kieling 2016-12-07 23:40:03 UTC

Please use openshift-jvm v1.0.57

Comment 3 Troy Dawson 2016-12-09 19:06:52 UTC

openshift-jvm v1.0.57 should be merged into ocp and is in OCP v3.4.0.34 or newe

Comment 5 Peng Li 2016-12-12 09:46:19 UTC

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.

Comment 7 errata-xmlrpc 2017-01-18 12:57:00 UTC

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