Bug 1401509 – Java Console Tracing raise exception in pod log (stop camel route)

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1401509 - Java Console Tracing raise exception in pod log (stop camel route)

Summary:	Java Console Tracing raise exception in pod log (stop camel route)

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Management Console (Show other bugs)
Sub Component:
Version:	3.3.1
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Alexandre Kieling
QA Contact:	Peng Li
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-12-05 08:20 EST by David Simansky
Modified:	2017-03-08 13 EST (History)
CC List:	5 users (show)

See Also:
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 07:57:00 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	OSFUSE-433	Blocker	Closed	OCP Java Console Tracing raise exception in pod log (stop camel route)	2017-07-05 04:26 EDT
Red Hat Product Errata	RHBA-2017:0066	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.4 RPM Release Advisory	2017-01-18 12:23:26 EST

Groups: None (edit)

Description David Simansky 2016-12-05 08:20:20 EST

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 15:13:32 EST

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

Comment 2 Alexandre Kieling 2016-12-07 18:40:03 EST

Please use openshift-jvm v1.0.57

Comment 3 Troy Dawson 2016-12-09 14:06:52 EST

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 04:46:19 EST

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 07:57:00 EST

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

Note You need to log in before you can comment on or make changes to this bug.