Bug 1401511 - Karaf quickstart update source raise exceptions in pod log
Summary: Karaf quickstart update source raise exceptions in pod log
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.3.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Alexandre Kieling
QA Contact: Peng Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-05 13:24 UTC by David Simansky
Modified: 2017-03-08 18:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Bug in the processing of Apache Camel routes defined in XML Consequence: Error in the Apache Camel application Fix: Fix XML by adding expected namespaces Result: Error in the Apache Camel application stops happening
Clone Of:
Environment:
Last Closed: 2017-01-18 12:57:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSFUSE-439 0 Critical Closed OCP Java Console Karaf quickstart update source raise exceptions in pod log 2017-03-01 03:44:08 UTC
Red Hat Product Errata RHBA-2017:0066 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 17:23:26 UTC

Description David Simansky 2016-12-05 13:24:18 UTC
Description of problem:
OCP Java Console Karaf quickstart update source raise exceptions in pod log

Version-Release number of selected component (if applicable):
openshift-jvm version: 1.0.50
OCP 3.3.1

Steps to Reproduce (it happnes only for karaf qs, springboot update source works):
1. Deploy karaf camel route to OCP (for example https://github.com/jboss-fuse/application-templates/blob/application-templates-2.0.fuse-000008/quickstarts/karaf2-camel-amq-template.json)
2. Open Java console from pod page
3. Camel tab -> jms-cbr-route -> Source
4. Update log message (add word MESSAGE): <log message="Done processing MESSAGE $
{file:name}

" id="route-final-log"/>
5. Click Update
6. You can see exceptions in pod log:

For more detail see linked original Jira issue.

Comment 1 Alexandre Kieling 2016-12-07 20:13:42 UTC
Fix is ready for testing. Please use openshift-jvm v1.0.54.

Comment 2 Alexandre Kieling 2016-12-07 23:39:58 UTC
Please use openshift-jvm v1.0.57

Comment 3 Troy Dawson 2016-12-09 19:07:07 UTC
openshift-jvm v1.0.57 should be merged into ocp and is in OCP v3.4.0.34 or newer.

Comment 5 Peng Li 2016-12-12 10:02:51 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. update generateOrder-route
<route xmlns="http://camel.apache.org/schema/spring" id="generateOrder-route">
        <from uri="timer:foo?delay=1s&amp;period=10s"/>
        <transform>
            <method ref="orderBean" method="generateOrder"/>
        </transform>
        <to uri="sql:{{sql.insertOrder}}"/>
        <log message="Inserted new order MESSAGE ${body.id}"/>
</route>
6. check pod log
(...)
2016-12-12 04:57:44,735 | INFO  | #3 - timer://foo | generateOrder-route              | 89 - org.apache.camel.camel-core - 2.15.1.redhat-621084 | Inserted new order MESSAGE 180
2016-12-12 04:57:45,035 | INFO  | ssed%20=%20false | processOrder-route               | 89 - org.apache.camel.camel-core - 2.15.1.redhat-621084 | MESSAGE Processed order id 180 item Camel of 9 copies of Camel in Action
2016-12-12 04:57:54,735 | INFO  | #3 - timer://foo | generateOrder-route              | 89 - org.apache.camel.camel-core - 2.15.1.redhat-621084 | Inserted new order MESSAGE 181
2016-12-12 04:57:55,043 | INFO  | ssed%20=%20false | processOrder-route               | 89 - org.apache.camel.camel-core - 2.15.1.redhat-621084 | MESSAGE Processed order id 181 item ActiveMQ of 9 copies of ActiveMQ in Action
2016-12-12 04:58:04,736 | INFO  | #3 - timer://foo | generateOrder-route              | 89 - org.apache.camel.camel-core - 2.15.1.redhat-621084 | Inserted new order MESSAGE 182
2016-12-12 04:58:05,051 | INFO  | ssed%20=%20false | processOrder-route               | 89 - org.apache.camel.camel-core - 2.15.1.redhat-621084 | MESSAGE Processed order id 182 item Camel of 2 copies of Camel in Action
2016-12-12 04:58:14,735 | INFO  | #3 - timer://foo | generateOrder-route              | 89 - org.apache.camel.camel-core - 2.15.1.redhat-621084 | Inserted new order MESSAGE 183
2016-12-12 04:58:15,059 | INFO  | ssed%20=%20false | processOrder-route               | 89 - org.apache.camel.camel-core - 2.15.1.redhat-621084 | MESSAGE Processed order id 183 item ActiveMQ of 4 copies of ActiveMQ in Action
2016-12-12 04:58:24,736 | INFO  | #3 - timer://foo | generateOrder-route              | 89 - org.apache.camel.camel-core - 2.15.1.redhat-621084 | Inserted new order MESSAGE 184
2016-12-12 04:58:25,067 | INFO  | ssed%20=%20false | processOrder-route               | 89 - org.apache.camel.camel-core - 2.15.1.redhat-621084 | MESSAGE Processed order id 184 item Camel of 9 copies of Camel in Action
(...)

Comment 7 errata-xmlrpc 2017-01-18 12:57:04 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


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