[jira] [Commented] (CAMEL-12022) direct component - Let the producer able to block and wait for consumers to be started

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292154#comment-16292154
 ] 

Claus Ibsen commented on CAMEL-12022:
-

Yes it is

> direct component - Let the producer able to block and wait for consumers to 
> be started
> --
>
> Key: CAMEL-12022
> URL: https://issues.apache.org/jira/browse/CAMEL-12022
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> Similar to what direct-vm component can do. We should let the direct producer 
> detect that if there is no consumer yet, then it can wait until its ready 
> (with timeout) during starting routes. 
> This can avoid the slim chance during route startup that you get a 
> DirectConsumerNotAvailableException



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12081) XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292140#comment-16292140
 ] 

ASF GitHub Bot commented on CAMEL-12081:


dmvolod closed pull request #2148: CAMEL-12081: Cherry-pick commits which are 
updating saxon from 9.7 to 9.8
URL: https://github.com/apache/camel/pull/2148
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/terminate.xsl
 
b/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/terminate.xsl
index d4d986049ea..eadebe811a4 100644
--- 
a/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/terminate.xsl
+++ 
b/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/terminate.xsl
@@ -15,7 +15,7 @@
   See the License for the specific language governing permissions and
   limitations under the License.
 -->
-http://www.w3.org/1999/XSL/Transform;>
+http://www.w3.org/1999/XSL/Transform;>
 
   
 
diff --git 
a/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform.xsl
 
b/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform.xsl
index fea1e639f7c..3b2651a809b 100644
--- 
a/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform.xsl
+++ 
b/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform.xsl
@@ -17,7 +17,7 @@
 -->
 
+  version='2.0'>
 
   
 
diff --git 
a/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_dtd.xsl
 
b/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_dtd.xsl
index 1ad29bd6964..96cb5ae8f3b 100644
--- 
a/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_dtd.xsl
+++ 
b/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_dtd.xsl
@@ -17,7 +17,7 @@
 -->
 
+  version='2.0'>
 
   
 
diff --git 
a/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_includes_data.xsl
 
b/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_includes_data.xsl
index 610ab3a2a8d..bf9eca26a2a 100644
--- 
a/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_includes_data.xsl
+++ 
b/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_includes_data.xsl
@@ -15,7 +15,7 @@
 See the License for the specific language governing permissions and
 limitations under the License.
 -->
-http://exslt.org/dates-and-times; version="1.1" 
xmlns:xsl="http://www.w3.org/1999/XSL/Transform;>
+http://exslt.org/dates-and-times; version="2.0" 
xmlns:xsl="http://www.w3.org/1999/XSL/Transform;>
 
 January
 February
diff --git 
a/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_text.xsl
 
b/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_text.xsl
index 6c38e4a4184..e8de2fe2287 100644
--- 
a/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_text.xsl
+++ 
b/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_text.xsl
@@ -15,7 +15,7 @@
 See the License for the specific language governing permissions and
 limitations under the License.
 -->
-http://www.w3.org/1999/XSL/Transform;   
  xmlns:date="http://xml.apache.org/xalan/java/java.util.Date;
  xmlns:rt="http://xml.apache.org/xalan/java/java.lang.Runtime;
diff --git 
a/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_text_imported.xsl
 
b/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_text_imported.xsl
index e7ae4b051da..931cf0ee8d7 100644
--- 
a/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_text_imported.xsl
+++ 
b/components/camel-saxon/src/test/resources/org/apache/camel/component/xslt/transform_text_imported.xsl
@@ -15,7 +15,7 @@
 See the License for the specific language governing permissions and
 limitations under the License.
 -->
-http://www.w3.org/1999/XSL/Transform;>
  
  
diff --git 
a/components/camel-saxon/src/test/resources/org/apache/camel/util/toolbox/aggregate-user-property.xsl
 
b/components/camel-saxon/src/test/resources/org/apache/camel/util/toolbox/aggregate-user-property.xsl
index 74bdd857fbc..75404db7dc5 100644
--- 
a/components/camel-saxon/src/test/resources/org/apache/camel/util/toolbox/aggregate-user-property.xsl
+++ 

[jira] [Commented] (CAMEL-12081) XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292141#comment-16292141
 ] 

ASF GitHub Bot commented on CAMEL-12081:


Github user dmvolod closed the pull request at:

https://github.com/apache/camel/pull/2148


> XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)
> ---
>
> Key: CAMEL-12081
> URL: https://issues.apache.org/jira/browse/CAMEL-12081
> Project: Camel
>  Issue Type: Bug
>  Components: camel-saxon
>Affects Versions: 2.20.1
> Environment: JDK 1.8.0_144. Windows 10 and Centos 7
>Reporter: Riaan Annandale
>Assignee: Dmitry Volodin
> Fix For: 2.20.2
>
>
> Hi guys
> I think saxon went to 9.7 in camel 2.18 (could be 19). Anyway, I used the 
> latest to illustrate my problem (2.20.1 at the time of writing)
> I have a routes that receive XML payloads which I then transform via 
> xqueries. Inside these I use local functions for readability (read: it's the 
> first thing I tried when solving my problem and it worked). 
> Since saxon went to 9.7 I get a null pointer exception when an xquery 
> containing a local function tries to process the XML.
> To demonstrate this, I have made a GitHub project:
> [https://github.com/rannandale/xqueryIssue]
> In the project I use two xqueries to transform the same source. 
> - One uses an inline for loop:
> 
>   {for $v in /root/Data return $v/Name}
> 
> - One uses the local function style:
> declare function local:loopMe($nodes)
> {
>for $node in $nodes
> return 
> {$node/*:Name}
> };
> 
> {local:loopMe(/root/Data)}
> 
> The latter is the one that returns the NPE.
> I know I could probably go refactor all my xqueries to match the inline 
> style, but I figured I'd see if there is an issue here other than PEBKAC. 
> They also get quite complex, so it's quite a bit of work.
> Thanks guys
> Riaan



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12081) XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292139#comment-16292139
 ] 

ASF GitHub Bot commented on CAMEL-12081:


dmvolod commented on issue #2148: CAMEL-12081: Cherry-pick commits which are 
updating saxon from 9.7 to 9.8
URL: https://github.com/apache/camel/pull/2148#issuecomment-351933627
 
 
   Ok, let's keep patch without non-patch updates. PR closed.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)
> ---
>
> Key: CAMEL-12081
> URL: https://issues.apache.org/jira/browse/CAMEL-12081
> Project: Camel
>  Issue Type: Bug
>  Components: camel-saxon
>Affects Versions: 2.20.1
> Environment: JDK 1.8.0_144. Windows 10 and Centos 7
>Reporter: Riaan Annandale
>Assignee: Dmitry Volodin
> Fix For: 2.20.2
>
>
> Hi guys
> I think saxon went to 9.7 in camel 2.18 (could be 19). Anyway, I used the 
> latest to illustrate my problem (2.20.1 at the time of writing)
> I have a routes that receive XML payloads which I then transform via 
> xqueries. Inside these I use local functions for readability (read: it's the 
> first thing I tried when solving my problem and it worked). 
> Since saxon went to 9.7 I get a null pointer exception when an xquery 
> containing a local function tries to process the XML.
> To demonstrate this, I have made a GitHub project:
> [https://github.com/rannandale/xqueryIssue]
> In the project I use two xqueries to transform the same source. 
> - One uses an inline for loop:
> 
>   {for $v in /root/Data return $v/Name}
> 
> - One uses the local function style:
> declare function local:loopMe($nodes)
> {
>for $node in $nodes
> return 
> {$node/*:Name}
> };
> 
> {local:loopMe(/root/Data)}
> 
> The latter is the one that returns the NPE.
> I know I could probably go refactor all my xqueries to match the inline 
> style, but I figured I'd see if there is an issue here other than PEBKAC. 
> They also get quite complex, so it's quite a bit of work.
> Thanks guys
> Riaan



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12022) direct component - Let the producer able to block and wait for consumers to be started

[Ramu kakarla (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291909#comment-16291909
 ] 

 Ramu kakarla commented on CAMEL-12022:
---

Hi Claus,

is this link  [Camel 2.21.0 
Release|https://cwiki.apache.org/confluence/display/CAMEL/Camel+2.21.0+Release] 
needs to be updated ?



> direct component - Let the producer able to block and wait for consumers to 
> be started
> --
>
> Key: CAMEL-12022
> URL: https://issues.apache.org/jira/browse/CAMEL-12022
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> Similar to what direct-vm component can do. We should let the direct producer 
> detect that if there is no consumer yet, then it can wait until its ready 
> (with timeout) during starting routes. 
> This can avoid the slim chance during route startup that you get a 
> DirectConsumerNotAvailableException



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12080) Allow creating csv content without last eol

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291895#comment-16291895
 ] 

ASF GitHub Bot commented on CAMEL-12080:


GitHub user ricardozanini opened a pull request:

https://github.com/apache/camel/pull/2149

CAMEL-12080: allow creating csvcontent without last eol



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ricardozanini/camel camel-12080

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/2149.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2149


commit 156371bb83923249ce2f060a31f378e8db7e48bf
Author: Ricardo Zanini 
Date:   2017-12-15T01:28:29Z

CAMEL-12080: allow creating csvcontent without last eol




> Allow creating csv content without last eol
> ---
>
> Key: CAMEL-12080
> URL: https://issues.apache.org/jira/browse/CAMEL-12080
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-bindy
>Reporter: Marcin Domanski
>Priority: Minor
> Fix For: Future
>
>
> Hello,
>   rfc4180 for CSV states:
> bq. The last record in the file may or may not have an ending line  break.
> For deserialization Bindy accepts both types of files, but for serialization 
> Bindy to my knowledge always creates content with last row ending with 
> newline. Unfortunately some legacy systems treat last newline as one more 
> empty row. Would it be possible to introduce control over this? I have this 
> problem in CSV and also in fixed format for one other place. For now we need 
> to strip the last char in Camel processor.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (CAMEL-12080) Allow creating csv content without last eol

[Ricardo Zanini (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ricardo Zanini updated CAMEL-12080:
---
Comment: was deleted

(was: Pull request sent: https://github.com/apache/camel/pull/2149)

> Allow creating csv content without last eol
> ---
>
> Key: CAMEL-12080
> URL: https://issues.apache.org/jira/browse/CAMEL-12080
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-bindy
>Reporter: Marcin Domanski
>Priority: Minor
> Fix For: Future
>
>
> Hello,
>   rfc4180 for CSV states:
> bq. The last record in the file may or may not have an ending line  break.
> For deserialization Bindy accepts both types of files, but for serialization 
> Bindy to my knowledge always creates content with last row ending with 
> newline. Unfortunately some legacy systems treat last newline as one more 
> empty row. Would it be possible to introduce control over this? I have this 
> problem in CSV and also in fixed format for one other place. For now we need 
> to strip the last char in Camel processor.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12080) Allow creating csv content without last eol

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291894#comment-16291894
 ] 

ASF GitHub Bot commented on CAMEL-12080:


ricardozanini opened a new pull request #2149: CAMEL-12080: allow creating 
csvcontent without last eol
URL: https://github.com/apache/camel/pull/2149
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Allow creating csv content without last eol
> ---
>
> Key: CAMEL-12080
> URL: https://issues.apache.org/jira/browse/CAMEL-12080
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-bindy
>Reporter: Marcin Domanski
>Priority: Minor
> Fix For: Future
>
>
> Hello,
>   rfc4180 for CSV states:
> bq. The last record in the file may or may not have an ending line  break.
> For deserialization Bindy accepts both types of files, but for serialization 
> Bindy to my knowledge always creates content with last row ending with 
> newline. Unfortunately some legacy systems treat last newline as one more 
> empty row. Would it be possible to introduce control over this? I have this 
> problem in CSV and also in fixed format for one other place. For now we need 
> to strip the last char in Camel processor.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12081) XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291571#comment-16291571
 ] 

ASF GitHub Bot commented on CAMEL-12081:


davsclaus commented on issue #2148: CAMEL-12081: Cherry-pick commits which are 
updating saxon from 9.7 to 9.8
URL: https://github.com/apache/camel/pull/2148#issuecomment-351828513
 
 
   Hmm this is good and bad at the same time. Because doing a non-patch upgrade 
on a patch branch is not always so good. What if it breaks other things. That 
user whom had a problem can just wait for Camel 2.21 to upgrade, or upgrade 
saxon himself.
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)
> ---
>
> Key: CAMEL-12081
> URL: https://issues.apache.org/jira/browse/CAMEL-12081
> Project: Camel
>  Issue Type: Bug
>  Components: camel-saxon
>Affects Versions: 2.20.1
> Environment: JDK 1.8.0_144. Windows 10 and Centos 7
>Reporter: Riaan Annandale
>Assignee: Dmitry Volodin
> Fix For: 2.20.2
>
>
> Hi guys
> I think saxon went to 9.7 in camel 2.18 (could be 19). Anyway, I used the 
> latest to illustrate my problem (2.20.1 at the time of writing)
> I have a routes that receive XML payloads which I then transform via 
> xqueries. Inside these I use local functions for readability (read: it's the 
> first thing I tried when solving my problem and it worked). 
> Since saxon went to 9.7 I get a null pointer exception when an xquery 
> containing a local function tries to process the XML.
> To demonstrate this, I have made a GitHub project:
> [https://github.com/rannandale/xqueryIssue]
> In the project I use two xqueries to transform the same source. 
> - One uses an inline for loop:
> 
>   {for $v in /root/Data return $v/Name}
> 
> - One uses the local function style:
> declare function local:loopMe($nodes)
> {
>for $node in $nodes
> return 
> {$node/*:Name}
> };
> 
> {local:loopMe(/root/Data)}
> 
> The latter is the one that returns the NPE.
> I know I could probably go refactor all my xqueries to match the inline 
> style, but I figured I'd see if there is an issue here other than PEBKAC. 
> They also get quite complex, so it's quite a bit of work.
> Thanks guys
> Riaan



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12083) Some camel karaf features errors

[Alex Dettinger (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291261#comment-16291261
 ] 

Alex Dettinger commented on CAMEL-12083:


I was able to install almost all features  with karaf 4.1.2:
* camel-chunk/2.21.0.SNAPSHOT
* camel-hessian/2.21.0.SNAPSHOT
* camel-jsonpath/2.21.0.SNAPSHOT
* camel-kura/2.21.0.SNAPSHOT

However, feature:install *camel-json-validator* reports:
{code:borderStyle=solid}
2017-12-14 18:41:31,768 | INFO  | tall camel-chunk | FeaturesServiceImpl
  | 9 - org.apache.karaf.features.core - 4.1.2 | Adding features: 
camel-json-validator/[2.21.0.SNAPSHOT,2.21.0.SNAPSHOT]
2017-12-14 18:41:31,856 | ERROR | nsole user karaf | ShellUtil  
  | 42 - org.apache.karaf.shell.core - 4.1.2 | Exception caught while 
executing command
org.osgi.service.resolver.ResolutionException: Unable to resolve root: missing 
requirement [root] osgi.identity; osgi.identity=camel-json-validator; 
type=karaf.feature; version="[2.21.0.SNAPSHOT,2.21.0.SNAPSHOT]"; 
filter:="(&(osgi.identity=camel-json-validator)(type=karaf.feature)(version>=2.21.0.SNAPSHOT)(version<=2.21.0.SNAPSHOT))"
 [caused by: Unable to resolve camel-json-validator/2.21.0.SNAPSHOT: missing 
requirement [camel-json-validator/2.21.0.SNAPSHOT] osgi.identity; 
osgi.identity=org.apache.camel.camel-json-validator; type=osgi.bundle; 
version="[2.21.0.SNAPSHOT,2.21.0.SNAPSHOT]"; resolution:=mandatory [caused by: 
Unable to resolve org.apache.camel.camel-json-validator/2.21.0.SNAPSHOT: 
missing requirement [org.apache.camel.camel-json-validator/2.21.0.SNAPSHOT] 
osgi.wiring.package; 
filter:="(&(osgi.wiring.package=org.everit.json.schema.loader)(version>=1.6.0)(!(version>=2.0.0)))"
 [caused by: Unable to resolve org.everit.json.schema/1.6.1: missing 
requirement [org.everit.json.schema/1.6.1] osgi.wiring.package; 
filter:="(&(osgi.wiring.package=org.json)(version>=20171018.0.0)(!(version>=20171019.0.0)))"]]]
at 
org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42) 
~[?:?]
at 
org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:389) ~[?:?]
...
at java.lang.Thread.run(Thread.java:745) [?:?]
{code}

> Some camel karaf features errors
> 
>
> Key: CAMEL-12083
> URL: https://issues.apache.org/jira/browse/CAMEL-12083
> Project: Camel
>  Issue Type: Task
>  Components: karaf
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 2.21.0
>
>
> When you validate the features some of them fail
> [WARNING] Feature resolution failed for [camel-chunk/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-hessian/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-json-validator/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-jsonpath/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-kura/2.21.0.SNAPSHOT]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-11224) aws-sqs producer does not support new FIFO queues

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-11224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291145#comment-16291145
 ] 

ASF GitHub Bot commented on CAMEL-11224:


evankellogg commented on issue #2018: CAMEL-11224 aws-sqs producer does not 
support new FIFO queues
URL: https://github.com/apache/camel/pull/2018#issuecomment-351765129
 
 
   @davsclaus @slukes I am also having trouble finding how to use this fix.  It 
says it's available after 2.6 (currently using 2.20.1), but I cannot find any 
object.  Additionally if I try to use the object as a route variable (eg. 
messageGroupIdStrategy=useExchangeId) I get a message saying the parameter 
could not be set.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> aws-sqs producer does not support new FIFO queues
> -
>
> Key: CAMEL-11224
> URL: https://issues.apache.org/jira/browse/CAMEL-11224
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-aws
>Reporter: Emilio Corengia
>Assignee: Claus Ibsen
> Fix For: 2.21.0
>
>
> At the moment *aws-sqs producer* does not support the new _FIFO_ queue 
> mechanism from AWS ([FIFO-queues 
> ref|http://http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues.html]).
>  There is a new parameter, +MessageGroupId+, that is required for FIFO queues 
> (it is not available on Standard queues).
> The message group ID is the tag that specifies that a message belongs to a 
> specific message group. Messages that belong to the same message group are 
> always processed one by one, in a strict order relative to the message group 
> (however, messages that belong to different message groups might be processed 
> out of order). +Source+: 
> http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queue-recommendations.html#using-messagegroupid-property.
> This improvement consists on adding support for MessageGroupId on the 
> producer side of aws-sqs. It should be applicable on FIFO queues only. It 
> could be customizable via URI options. A default strategy should be provided. 
> This default strategy will generate a unique message group ID for each 
> message to favor throughput and latency over ordering of messages.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-12084) Fixed missing encoding of query params (port CAMEL-12057 for camel-olingo4)

[Dmitry Volodin (JIRA)]

Dmitry Volodin created CAMEL-12084:
--

 Summary: Fixed missing encoding of query params (port CAMEL-12057 
for camel-olingo4)
 Key: CAMEL-12084
 URL: https://issues.apache.org/jira/browse/CAMEL-12084
 Project: Camel
  Issue Type: Bug
  Components: camel-olingo4
Affects Versions: 2.20.1
Reporter: Dmitry Volodin
Assignee: Dmitry Volodin
 Fix For: 2.20.2






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (CAMEL-12084) Fixed missing encoding of query params (port CAMEL-12057 for camel-olingo4)

[Dmitry Volodin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-12084 started by Dmitry Volodin.
--
> Fixed missing encoding of query params (port CAMEL-12057 for camel-olingo4)
> ---
>
> Key: CAMEL-12084
> URL: https://issues.apache.org/jira/browse/CAMEL-12084
> Project: Camel
>  Issue Type: Bug
>  Components: camel-olingo4
>Affects Versions: 2.20.1
>Reporter: Dmitry Volodin
>Assignee: Dmitry Volodin
> Fix For: 2.20.2
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12081) XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291046#comment-16291046
 ] 

ASF GitHub Bot commented on CAMEL-12081:


GitHub user dmvolod opened a pull request:

https://github.com/apache/camel/pull/2148

CAMEL-12081: Cherry-pick commits which are updating saxon from 9.7 to 9.8

This issue is related to saxon and not related to camel-saxon component 
implementation.
I've checked provided test on top of the Camel 2.21.0-SNAPSHOT version and 
it's working correctly.
This PR is created to update saxon to the version 9.8.0-6 on top of the 
Camel 2.20.2.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dmvolod/camel CAMEL-12081

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/2148.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2148


commit 76154f3d3b05e469d8ca3da562e2659b760adc56
Author: Andrea Cosentino 
Date:   2017-11-23T11:49:07Z

Upgrade Saxon and related bundle to version 9.8.0-5 and regen

commit 5bb67b5c9d3d3c176f5e438bd9e033e2af54435a
Author: Andrea Cosentino 
Date:   2017-12-05T07:31:10Z

Upgrade Saxon and related bundle to version 9.8.0-6




> XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)
> ---
>
> Key: CAMEL-12081
> URL: https://issues.apache.org/jira/browse/CAMEL-12081
> Project: Camel
>  Issue Type: Bug
>  Components: camel-saxon
>Affects Versions: 2.20.1
> Environment: JDK 1.8.0_144. Windows 10 and Centos 7
>Reporter: Riaan Annandale
>Assignee: Dmitry Volodin
> Fix For: 2.20.2
>
>
> Hi guys
> I think saxon went to 9.7 in camel 2.18 (could be 19). Anyway, I used the 
> latest to illustrate my problem (2.20.1 at the time of writing)
> I have a routes that receive XML payloads which I then transform via 
> xqueries. Inside these I use local functions for readability (read: it's the 
> first thing I tried when solving my problem and it worked). 
> Since saxon went to 9.7 I get a null pointer exception when an xquery 
> containing a local function tries to process the XML.
> To demonstrate this, I have made a GitHub project:
> [https://github.com/rannandale/xqueryIssue]
> In the project I use two xqueries to transform the same source. 
> - One uses an inline for loop:
> 
>   {for $v in /root/Data return $v/Name}
> 
> - One uses the local function style:
> declare function local:loopMe($nodes)
> {
>for $node in $nodes
> return 
> {$node/*:Name}
> };
> 
> {local:loopMe(/root/Data)}
> 
> The latter is the one that returns the NPE.
> I know I could probably go refactor all my xqueries to match the inline 
> style, but I figured I'd see if there is an issue here other than PEBKAC. 
> They also get quite complex, so it's quite a bit of work.
> Thanks guys
> Riaan



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12081) XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291045#comment-16291045
 ] 

ASF GitHub Bot commented on CAMEL-12081:


dmvolod opened a new pull request #2148: CAMEL-12081: Cherry-pick commits which 
are updating saxon from 9.7 to 9.8
URL: https://github.com/apache/camel/pull/2148
 
 
   This issue is related to saxon and not related to camel-saxon component 
implementation.
   I've checked provided test on top of the Camel 2.21.0-SNAPSHOT version and 
it's working correctly.
   This PR is created to update saxon to the version 9.8.0-6 on top of the 
Camel 2.20.2.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)
> ---
>
> Key: CAMEL-12081
> URL: https://issues.apache.org/jira/browse/CAMEL-12081
> Project: Camel
>  Issue Type: Bug
>  Components: camel-saxon
>Affects Versions: 2.20.1
> Environment: JDK 1.8.0_144. Windows 10 and Centos 7
>Reporter: Riaan Annandale
>Assignee: Dmitry Volodin
> Fix For: 2.20.2
>
>
> Hi guys
> I think saxon went to 9.7 in camel 2.18 (could be 19). Anyway, I used the 
> latest to illustrate my problem (2.20.1 at the time of writing)
> I have a routes that receive XML payloads which I then transform via 
> xqueries. Inside these I use local functions for readability (read: it's the 
> first thing I tried when solving my problem and it worked). 
> Since saxon went to 9.7 I get a null pointer exception when an xquery 
> containing a local function tries to process the XML.
> To demonstrate this, I have made a GitHub project:
> [https://github.com/rannandale/xqueryIssue]
> In the project I use two xqueries to transform the same source. 
> - One uses an inline for loop:
> 
>   {for $v in /root/Data return $v/Name}
> 
> - One uses the local function style:
> declare function local:loopMe($nodes)
> {
>for $node in $nodes
> return 
> {$node/*:Name}
> };
> 
> {local:loopMe(/root/Data)}
> 
> The latter is the one that returns the NPE.
> I know I could probably go refactor all my xqueries to match the inline 
> style, but I figured I'd see if there is an issue here other than PEBKAC. 
> They also get quite complex, so it's quite a bit of work.
> Thanks guys
> Riaan



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12063) Spring Boot - xmlRoutesReloadDirectory & jmxCreateConnector issue - duplicated JMX

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291038#comment-16291038
 ] 

Claus Ibsen commented on CAMEL-12063:
-

Can you provide a sample project.

Also next time ask on the user mailing list first for help, as using JIRA first 
is not the correct way.
The reload directory option you use is only for reloading Camel routes. So you 
must be doing something different that causes the entire CamelContext to be 
reloaded, maybe by spring or something.


> Spring Boot - xmlRoutesReloadDirectory & jmxCreateConnector issue - 
> duplicated JMX
> --
>
> Key: CAMEL-12063
> URL: https://issues.apache.org/jira/browse/CAMEL-12063
> Project: Camel
>  Issue Type: Bug
>  Components: camel-spring-boot
> Environment: Windows
> Camel 2.20.0
> JDK 1.8
>Reporter: Frédéric OLIER
>Priority: Minor
>
> We configured CAMEL with Spring Boot.
> We used the 'application.properties' file to set-up a folder in which routes 
> are read from when they are updated:
> camel.springboot.xmlRoutesReloadDirectory=/path/to/route/folder/
> *First remark:* If a file is already in the folder, a 'touch' on it is 
> required for it to be loaded.
> We then tried to configure an JMX agent with the following configuration, 
> still in 'application.properties':
> camel.sprintboot.jmxCreateConnector=true
> *Second remark:* The value is not set. We traced (debug mode) to check 
> whether the method 'CamelConfigurationProperties.setJmxCreateConnector()' was 
> called. It is NOT called.
> We therefore configured our Spring Boot application to load a context on 
> start-up:
> {{
> @SpringBootApplication
> @ImportResource({"classpath:camelContext.xml"})
> public class ST3Application {
>   /**
>* A main method to start this application.
>* @throws Exception 
>*/
>   public static void main(String[] args) throws Exception {   
>SpringApplication.run(ST3Application.class, args);
>   }
> }
> }}
> The camelContext.xml being as follows:
> {{
> http://www.springframework.org/schema/beans;
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>   xsi:schemaLocation="
>  http://www.springframework.org/schema/beans 
> http://www.springframework.org/schema/beans/spring-beans.xsd
>  http://camel.apache.org/schema/spring 
> http://camel.apache.org/schema/spring/camel-spring.xsd;>
>xmlns="http://camel.apache.org/schema/spring;>
>   
>   
> 
> }}
> In this case, the JMX Bean is exposed and accessible via a JMX client.
> *Third remark:* When we update the route file from the 
> '/path/to/route/folder/' folder, there is a message in the log indicateing 
> that there is a conflict with the exposed JMX:
> {{
> 2017-12-05 09:49:37.368  WARN 3096 --- [   main] 
> a.c.m.DefaultManagementLifecycleStrategy : This CamelContext(camel-xml) will 
> be registered using the name: camel-xml-1 due to clash with an existing name 
> already registered in MBeanServer.
> }}
> So it seems that upon routes reloading, the initial JMX are not properly 
> destroyed before creating the new ones.
> The annoying thing is that we cannot safely access the MBean as it is mixed 
> up.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-10543) New Apache Camel Logo

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-10543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290977#comment-16290977
 ] 

Claus Ibsen commented on CAMEL-10543:
-

[~zregvart] do you mind commit your logo to the source code so we have it, I 
think the PR was closed recently.

> New Apache Camel Logo
> -
>
> Key: CAMEL-10543
> URL: https://issues.apache.org/jira/browse/CAMEL-10543
> Project: Camel
>  Issue Type: Improvement
>  Components: website
>Reporter: Luca Burgazzoli
> Fix For: Future
>
> Attachments: apachecamel.png, apachecamel.png, new_log_camel.jpg
>
>
> The Apache Camel logo is a bit out dated so we have discussed in the Camel 
> PMC and community to come up with a new one.
> We encourage anyone to participate by submitting a logo proposal and/or share 
> thoughts
> The logo can be submitted by either:
> - a PR on GitHub (preferred)
> - file attachment to this JIRA ticket
> And each logo should be:
> - images should be added to docs/img
> - each PR should contains a single logo
> We are looking for a new logo that has two parts
> - graphical logo
> - The name: Apache Camel
> So we can use the logo without the word Apache Camel, but also as a 
> combination of the two of them, eg as logo on the Camel front page.
> Also if the logo can be vector based it would be a benefit, so it can scale 
> up and down nicely.
> You can find details here how to contribute to the project and how to work on 
> the source code. Such as how to do a github PR:
> http://camel.apache.org/contributing



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-12080) Allow creating csv content without last eol

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-12080:

Fix Version/s: Future

> Allow creating csv content without last eol
> ---
>
> Key: CAMEL-12080
> URL: https://issues.apache.org/jira/browse/CAMEL-12080
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-bindy
>Reporter: Marcin Domanski
>Priority: Minor
> Fix For: Future
>
>
> Hello,
>   rfc4180 for CSV states:
> bq. The last record in the file may or may not have an ending line  break.
> For deserialization Bindy accepts both types of files, but for serialization 
> Bindy to my knowledge always creates content with last row ending with 
> newline. Unfortunately some legacy systems treat last newline as one more 
> empty row. Would it be possible to introduce control over this? I have this 
> problem in CSV and also in fixed format for one other place. For now we need 
> to strip the last char in Camel processor.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12080) Allow creating csv content without last eol

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290973#comment-16290973
 ] 

Claus Ibsen commented on CAMEL-12080:
-

People in the community is welcome to work on a patch with such functionality

> Allow creating csv content without last eol
> ---
>
> Key: CAMEL-12080
> URL: https://issues.apache.org/jira/browse/CAMEL-12080
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-bindy
>Reporter: Marcin Domanski
>Priority: Minor
> Fix For: Future
>
>
> Hello,
>   rfc4180 for CSV states:
> bq. The last record in the file may or may not have an ending line  break.
> For deserialization Bindy accepts both types of files, but for serialization 
> Bindy to my knowledge always creates content with last row ending with 
> newline. Unfortunately some legacy systems treat last newline as one more 
> empty row. Would it be possible to introduce control over this? I have this 
> problem in CSV and also in fixed format for one other place. For now we need 
> to strip the last char in Camel processor.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-12080) Allow creating csv content without last eol

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-12080:

Estimated Complexity: Novice  (was: Unknown)

> Allow creating csv content without last eol
> ---
>
> Key: CAMEL-12080
> URL: https://issues.apache.org/jira/browse/CAMEL-12080
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-bindy
>Reporter: Marcin Domanski
>Priority: Minor
> Fix For: Future
>
>
> Hello,
>   rfc4180 for CSV states:
> bq. The last record in the file may or may not have an ending line  break.
> For deserialization Bindy accepts both types of files, but for serialization 
> Bindy to my knowledge always creates content with last row ending with 
> newline. Unfortunately some legacy systems treat last newline as one more 
> empty row. Would it be possible to introduce control over this? I have this 
> problem in CSV and also in fixed format for one other place. For now we need 
> to strip the last char in Camel processor.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-12074) Let okStatusCodeRange support multiple ranges

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-12074:

Fix Version/s: 2.21.0

> Let okStatusCodeRange support multiple ranges
> -
>
> Key: CAMEL-12074
> URL: https://issues.apache.org/jira/browse/CAMEL-12074
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-http, camel-http4
>Affects Versions: 2.20.1
>Reporter: Niels Ull Harremoes
>Priority: Minor
> Fix For: 2.21.0
>
> Attachments: 
> CAMEL-12074_Let_okStatusRange_support_multiple_ranges.patch
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> When working with rest api's, some http status codes such as 404 Not Found 
> are not necessarily errors.  It would be nice to be able to specify multiple 
> ranges and individual codes such as {{okStatusCodeRange=200-204,404}}.
> This would allow us to handle 404 in the main route logic while still 
> throwing an exception for other status codes. While we can use 
> {{throwExceptionOnFailure=false}} we then have to throw exceptions ourselves 
> for most status codes.
> As far as I can tell, this requires a simple modification in 
> HttpHelper::isStatusCodeOk.
> I will give it a shot.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12074) Let okStatusCodeRange support multiple ranges

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290972#comment-16290972
 ] 

Claus Ibsen commented on CAMEL-12074:
-

You need to fix checkstyle errors, build with

mvn compile -P sourcecheck

And the documentation should be done in the java source code as the ascii doc 
file is automatic grabbed from source when it comes to endpoint options, so 
find where it is in the java file and edit there.

> Let okStatusCodeRange support multiple ranges
> -
>
> Key: CAMEL-12074
> URL: https://issues.apache.org/jira/browse/CAMEL-12074
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-http, camel-http4
>Affects Versions: 2.20.1
>Reporter: Niels Ull Harremoes
>Priority: Minor
> Fix For: 2.21.0
>
> Attachments: 
> CAMEL-12074_Let_okStatusRange_support_multiple_ranges.patch
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> When working with rest api's, some http status codes such as 404 Not Found 
> are not necessarily errors.  It would be nice to be able to specify multiple 
> ranges and individual codes such as {{okStatusCodeRange=200-204,404}}.
> This would allow us to handle 404 in the main route logic while still 
> throwing an exception for other status codes. While we can use 
> {{throwExceptionOnFailure=false}} we then have to throw exceptions ourselves 
> for most status codes.
> As far as I can tell, this requires a simple modification in 
> HttpHelper::isStatusCodeOk.
> I will give it a shot.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12083) Some camel karaf features errors

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290962#comment-16290962
 ] 

Claus Ibsen commented on CAMEL-12083:
-

We need to be sure that these features can install manually in karaf and that 
it was just some weird karaf validator issue, some of the features fail with 
some asm import stuff.

> Some camel karaf features errors
> 
>
> Key: CAMEL-12083
> URL: https://issues.apache.org/jira/browse/CAMEL-12083
> Project: Camel
>  Issue Type: Task
>  Components: karaf
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 2.21.0
>
>
> When you validate the features some of them fail
> [WARNING] Feature resolution failed for [camel-chunk/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-hessian/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-json-validator/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-jsonpath/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-kura/2.21.0.SNAPSHOT]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-12083) Some camel karaf features errors

[Claus Ibsen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-12083:

Priority: Minor  (was: Major)

> Some camel karaf features errors
> 
>
> Key: CAMEL-12083
> URL: https://issues.apache.org/jira/browse/CAMEL-12083
> Project: Camel
>  Issue Type: Task
>  Components: karaf
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 2.21.0
>
>
> When you validate the features some of them fail
> [WARNING] Feature resolution failed for [camel-chunk/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-hessian/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-json-validator/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-jsonpath/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-kura/2.21.0.SNAPSHOT]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12083) Some camel karaf features errors

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290942#comment-16290942
 ] 

Claus Ibsen commented on CAMEL-12083:
-

I got camel-hessian fixed. Installing the others manually in karaf worked for 
me.

> Some camel karaf features errors
> 
>
> Key: CAMEL-12083
> URL: https://issues.apache.org/jira/browse/CAMEL-12083
> Project: Camel
>  Issue Type: Task
>  Components: karaf
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> When you validate the features some of them fail
> [WARNING] Feature resolution failed for [camel-chunk/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-hessian/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-json-validator/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-jsonpath/2.21.0.SNAPSHOT]
> [WARNING] Feature resolution failed for [camel-kura/2.21.0.SNAPSHOT]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (CAMEL-12083) Some camel karaf features errors

[Claus Ibsen (JIRA)]

Claus Ibsen created CAMEL-12083:
---

 Summary: Some camel karaf features errors
 Key: CAMEL-12083
 URL: https://issues.apache.org/jira/browse/CAMEL-12083
 Project: Camel
  Issue Type: Task
  Components: karaf
Reporter: Claus Ibsen
 Fix For: 2.21.0


When you validate the features some of them fail

[WARNING] Feature resolution failed for [camel-chunk/2.21.0.SNAPSHOT]
[WARNING] Feature resolution failed for [camel-hessian/2.21.0.SNAPSHOT]
[WARNING] Feature resolution failed for [camel-json-validator/2.21.0.SNAPSHOT]
[WARNING] Feature resolution failed for [camel-jsonpath/2.21.0.SNAPSHOT]
[WARNING] Feature resolution failed for [camel-kura/2.21.0.SNAPSHOT]




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (CAMEL-12081) XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)

[Dmitry Volodin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-12081 started by Dmitry Volodin.
--
> XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)
> ---
>
> Key: CAMEL-12081
> URL: https://issues.apache.org/jira/browse/CAMEL-12081
> Project: Camel
>  Issue Type: Bug
>  Components: camel-saxon
>Affects Versions: 2.20.1
> Environment: JDK 1.8.0_144. Windows 10 and Centos 7
>Reporter: Riaan Annandale
>Assignee: Dmitry Volodin
> Fix For: 2.20.2
>
>
> Hi guys
> I think saxon went to 9.7 in camel 2.18 (could be 19). Anyway, I used the 
> latest to illustrate my problem (2.20.1 at the time of writing)
> I have a routes that receive XML payloads which I then transform via 
> xqueries. Inside these I use local functions for readability (read: it's the 
> first thing I tried when solving my problem and it worked). 
> Since saxon went to 9.7 I get a null pointer exception when an xquery 
> containing a local function tries to process the XML.
> To demonstrate this, I have made a GitHub project:
> [https://github.com/rannandale/xqueryIssue]
> In the project I use two xqueries to transform the same source. 
> - One uses an inline for loop:
> 
>   {for $v in /root/Data return $v/Name}
> 
> - One uses the local function style:
> declare function local:loopMe($nodes)
> {
>for $node in $nodes
> return 
> {$node/*:Name}
> };
> 
> {local:loopMe(/root/Data)}
> 
> The latter is the one that returns the NPE.
> I know I could probably go refactor all my xqueries to match the inline 
> style, but I figured I'd see if there is an issue here other than PEBKAC. 
> They also get quite complex, so it's quite a bit of work.
> Thanks guys
> Riaan



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12081) XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)

[Dmitry Volodin (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290908#comment-16290908
 ] 

Dmitry Volodin commented on CAMEL-12081:


This issue is related to saxon and not related to camel-saxon component 
implementation.
I've checked provided test on top of the Camel 2.21.0-SNAPSHOT version and it's 
working correctly.
I will create a separate PR to update saxon to the version 9.8.0-6 on top of 
the Camel 2.20.2.

> XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)
> ---
>
> Key: CAMEL-12081
> URL: https://issues.apache.org/jira/browse/CAMEL-12081
> Project: Camel
>  Issue Type: Bug
>  Components: camel-saxon
>Affects Versions: 2.20.1
> Environment: JDK 1.8.0_144. Windows 10 and Centos 7
>Reporter: Riaan Annandale
> Fix For: 2.20.2
>
>
> Hi guys
> I think saxon went to 9.7 in camel 2.18 (could be 19). Anyway, I used the 
> latest to illustrate my problem (2.20.1 at the time of writing)
> I have a routes that receive XML payloads which I then transform via 
> xqueries. Inside these I use local functions for readability (read: it's the 
> first thing I tried when solving my problem and it worked). 
> Since saxon went to 9.7 I get a null pointer exception when an xquery 
> containing a local function tries to process the XML.
> To demonstrate this, I have made a GitHub project:
> [https://github.com/rannandale/xqueryIssue]
> In the project I use two xqueries to transform the same source. 
> - One uses an inline for loop:
> 
>   {for $v in /root/Data return $v/Name}
> 
> - One uses the local function style:
> declare function local:loopMe($nodes)
> {
>for $node in $nodes
> return 
> {$node/*:Name}
> };
> 
> {local:loopMe(/root/Data)}
> 
> The latter is the one that returns the NPE.
> I know I could probably go refactor all my xqueries to match the inline 
> style, but I figured I'd see if there is an issue here other than PEBKAC. 
> They also get quite complex, so it's quite a bit of work.
> Thanks guys
> Riaan



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (CAMEL-12081) XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)

[Dmitry Volodin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitry Volodin reassigned CAMEL-12081:
--

Assignee: Dmitry Volodin

> XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)
> ---
>
> Key: CAMEL-12081
> URL: https://issues.apache.org/jira/browse/CAMEL-12081
> Project: Camel
>  Issue Type: Bug
>  Components: camel-saxon
>Affects Versions: 2.20.1
> Environment: JDK 1.8.0_144. Windows 10 and Centos 7
>Reporter: Riaan Annandale
>Assignee: Dmitry Volodin
> Fix For: 2.20.2
>
>
> Hi guys
> I think saxon went to 9.7 in camel 2.18 (could be 19). Anyway, I used the 
> latest to illustrate my problem (2.20.1 at the time of writing)
> I have a routes that receive XML payloads which I then transform via 
> xqueries. Inside these I use local functions for readability (read: it's the 
> first thing I tried when solving my problem and it worked). 
> Since saxon went to 9.7 I get a null pointer exception when an xquery 
> containing a local function tries to process the XML.
> To demonstrate this, I have made a GitHub project:
> [https://github.com/rannandale/xqueryIssue]
> In the project I use two xqueries to transform the same source. 
> - One uses an inline for loop:
> 
>   {for $v in /root/Data return $v/Name}
> 
> - One uses the local function style:
> declare function local:loopMe($nodes)
> {
>for $node in $nodes
> return 
> {$node/*:Name}
> };
> 
> {local:loopMe(/root/Data)}
> 
> The latter is the one that returns the NPE.
> I know I could probably go refactor all my xqueries to match the inline 
> style, but I figured I'd see if there is an issue here other than PEBKAC. 
> They also get quite complex, so it's quite a bit of work.
> Thanks guys
> Riaan



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-12081) XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)

[Dmitry Volodin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitry Volodin updated CAMEL-12081:
---
Fix Version/s: 2.20.2

> XQuery NPE going from saxon 9.5 to 9.7 (upgraded camel from2.17.4-> 2.20.1)
> ---
>
> Key: CAMEL-12081
> URL: https://issues.apache.org/jira/browse/CAMEL-12081
> Project: Camel
>  Issue Type: Bug
>  Components: camel-saxon
>Affects Versions: 2.20.1
> Environment: JDK 1.8.0_144. Windows 10 and Centos 7
>Reporter: Riaan Annandale
> Fix For: 2.20.2
>
>
> Hi guys
> I think saxon went to 9.7 in camel 2.18 (could be 19). Anyway, I used the 
> latest to illustrate my problem (2.20.1 at the time of writing)
> I have a routes that receive XML payloads which I then transform via 
> xqueries. Inside these I use local functions for readability (read: it's the 
> first thing I tried when solving my problem and it worked). 
> Since saxon went to 9.7 I get a null pointer exception when an xquery 
> containing a local function tries to process the XML.
> To demonstrate this, I have made a GitHub project:
> [https://github.com/rannandale/xqueryIssue]
> In the project I use two xqueries to transform the same source. 
> - One uses an inline for loop:
> 
>   {for $v in /root/Data return $v/Name}
> 
> - One uses the local function style:
> declare function local:loopMe($nodes)
> {
>for $node in $nodes
> return 
> {$node/*:Name}
> };
> 
> {local:loopMe(/root/Data)}
> 
> The latter is the one that returns the NPE.
> I know I could probably go refactor all my xqueries to match the inline 
> style, but I figured I'd see if there is an issue here other than PEBKAC. 
> They also get quite complex, so it's quite a bit of work.
> Thanks guys
> Riaan



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12022) direct component - Let the producer able to block and wait for consumers to be started

[Claus Ibsen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290854#comment-16290854
 ] 

Claus Ibsen commented on CAMEL-12022:
-

Make sure to update the release notes as its a change of behaviour
http://camel.apache.org/camel-2210-release.html

> direct component - Let the producer able to block and wait for consumers to 
> be started
> --
>
> Key: CAMEL-12022
> URL: https://issues.apache.org/jira/browse/CAMEL-12022
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> Similar to what direct-vm component can do. We should let the direct producer 
> detect that if there is no consumer yet, then it can wait until its ready 
> (with timeout) during starting routes. 
> This can avoid the slim chance during route startup that you get a 
> DirectConsumerNotAvailableException



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12022) direct component - Let the producer able to block and wait for consumers to be started

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290843#comment-16290843
 ] 

ASF GitHub Bot commented on CAMEL-12022:


oscerd commented on issue #2125: "CAMEL-12022:direct component - Let the 
producer able to block and wa…
URL: https://github.com/apache/camel/pull/2125#issuecomment-351713686
 
 
   ok, I'll merge ASAP


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> direct component - Let the producer able to block and wait for consumers to 
> be started
> --
>
> Key: CAMEL-12022
> URL: https://issues.apache.org/jira/browse/CAMEL-12022
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> Similar to what direct-vm component can do. We should let the direct producer 
> detect that if there is no consumer yet, then it can wait until its ready 
> (with timeout) during starting routes. 
> This can avoid the slim chance during route startup that you get a 
> DirectConsumerNotAvailableException



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12022) direct component - Let the producer able to block and wait for consumers to be started

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290838#comment-16290838
 ] 

ASF GitHub Bot commented on CAMEL-12022:


ramu11 commented on issue #2125: "CAMEL-12022:direct component - Let the 
producer able to block and wa…
URL: https://github.com/apache/camel/pull/2125#issuecomment-351712983
 
 
   Yup tested


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> direct component - Let the producer able to block and wait for consumers to 
> be started
> --
>
> Key: CAMEL-12022
> URL: https://issues.apache.org/jira/browse/CAMEL-12022
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> Similar to what direct-vm component can do. We should let the direct producer 
> detect that if there is no consumer yet, then it can wait until its ready 
> (with timeout) during starting routes. 
> This can avoid the slim chance during route startup that you get a 
> DirectConsumerNotAvailableException



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12022) direct component - Let the producer able to block and wait for consumers to be started

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290834#comment-16290834
 ] 

ASF GitHub Bot commented on CAMEL-12022:


oscerd commented on issue #2125: "CAMEL-12022:direct component - Let the 
producer able to block and wa…
URL: https://github.com/apache/camel/pull/2125#issuecomment-351712248
 
 
   @ramu11 did you test on camel-spring too? Thanks.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> direct component - Let the producer able to block and wait for consumers to 
> be started
> --
>
> Key: CAMEL-12022
> URL: https://issues.apache.org/jira/browse/CAMEL-12022
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> Similar to what direct-vm component can do. We should let the direct producer 
> detect that if there is no consumer yet, then it can wait until its ready 
> (with timeout) during starting routes. 
> This can avoid the slim chance during route startup that you get a 
> DirectConsumerNotAvailableException



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12022) direct component - Let the producer able to block and wait for consumers to be started

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290833#comment-16290833
 ] 

ASF GitHub Bot commented on CAMEL-12022:


oscerd commented on issue #2125: "CAMEL-12022:direct component - Let the 
producer able to block and wa…
URL: https://github.com/apache/camel/pull/2125#issuecomment-351711442
 
 
   If you are ok with this, we can merge this.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> direct component - Let the producer able to block and wait for consumers to 
> be started
> --
>
> Key: CAMEL-12022
> URL: https://issues.apache.org/jira/browse/CAMEL-12022
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> Similar to what direct-vm component can do. We should let the direct producer 
> detect that if there is no consumer yet, then it can wait until its ready 
> (with timeout) during starting routes. 
> This can avoid the slim chance during route startup that you get a 
> DirectConsumerNotAvailableException



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12022) direct component - Let the producer able to block and wait for consumers to be started

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290832#comment-16290832
 ] 

ASF GitHub Bot commented on CAMEL-12022:


davsclaus commented on issue #2125: "CAMEL-12022:direct component - Let the 
producer able to block and wa…
URL: https://github.com/apache/camel/pull/2125#issuecomment-351710150
 
 
   The option on the component level allows to configure this globally, eg to 
turn of block etc.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> direct component - Let the producer able to block and wait for consumers to 
> be started
> --
>
> Key: CAMEL-12022
> URL: https://issues.apache.org/jira/browse/CAMEL-12022
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> Similar to what direct-vm component can do. We should let the direct producer 
> detect that if there is no consumer yet, then it can wait until its ready 
> (with timeout) during starting routes. 
> This can avoid the slim chance during route startup that you get a 
> DirectConsumerNotAvailableException



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (CAMEL-12076) Camel Kafka producer: Specified topic is ignored ("No topic key set" error) when KafkaConfiguration is used

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-12076:
-
Fix Version/s: 2.21.0

> Camel Kafka producer: Specified topic is ignored ("No topic key set" error) 
> when KafkaConfiguration is used
> ---
>
> Key: CAMEL-12076
> URL: https://issues.apache.org/jira/browse/CAMEL-12076
> Project: Camel
>  Issue Type: Bug
>  Components: camel-kafka
>Affects Versions: 2.20.1
>Reporter: Igor Lavrentjev
>Assignee: Dmitry Volodin
> Fix For: 2.21.0
>
>
> Specified topic is ignored ("No topic key set" error) when KafkaConfiguration 
> is used. When topic is set inside KafkaConfiguration then no error occurs.
> 1.5.8.RELEASE
> 2.20.1
> {code}
> from("direct:sendToKafka")
> .setBody(constant("Message from Camel to Kafka"))
> .setHeader(KafkaConstants.KEY, constant("Camel"))
> .to("kafka:TESTTOPIC?configuration=#kafkaConfiguration");
> {code}
> {code}
> 2017-12-11 14:16:35.466 ERROR 12048 --- [ad #1 - WireTap] CamelRouter 
>  : Exchange[ExchangePattern: InOnly, BodyType: String, 
> Body: Message from Camel to Kafka, CaughtExceptionType: 
> org.apache.camel.CamelExchangeException, CaughtExcept
> ionMessage: No topic key set. Exchange[ID-5CG7383K6H00BA-1512994577303-0-3], 
> StackTrace: org.apache.camel.CamelExchangeException: No topic key set. 
> Exchange[ID-5CG7383K6H00BA-1512994577303-0-3]
> at 
> org.apache.camel.component.kafka.KafkaProducer.createRecorder(KafkaProducer.java:149)
> at 
> org.apache.camel.component.kafka.KafkaProducer.process(KafkaProducer.java:251)
> at 
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
> at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at 
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
> at 
> org.apache.camel.processor.SendDynamicProcessor$1.doInAsyncProducer(SendDynamicProcessor.java:132)
> at 
> org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:445)
> at 
> org.apache.camel.processor.SendDynamicProcessor.process(SendDynamicProcessor.java:127)
> at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at 
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)
> at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:158)
> at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:153)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12076) Camel Kafka producer: Specified topic is ignored ("No topic key set" error) when KafkaConfiguration is used

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290653#comment-16290653
 ] 

ASF GitHub Bot commented on CAMEL-12076:


oscerd commented on issue #2147: CAMEL-12076: Specified topic is ignored when 
KafkaConfiguration is used
URL: https://github.com/apache/camel/pull/2147#issuecomment-351666831
 
 
   Thanks the PR has been merged on master. There was a little error on tests 
compilation. Fixed now.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Camel Kafka producer: Specified topic is ignored ("No topic key set" error) 
> when KafkaConfiguration is used
> ---
>
> Key: CAMEL-12076
> URL: https://issues.apache.org/jira/browse/CAMEL-12076
> Project: Camel
>  Issue Type: Bug
>  Components: camel-kafka
>Affects Versions: 2.20.1
>Reporter: Igor Lavrentjev
>Assignee: Dmitry Volodin
> Fix For: 2.21.0
>
>
> Specified topic is ignored ("No topic key set" error) when KafkaConfiguration 
> is used. When topic is set inside KafkaConfiguration then no error occurs.
> 1.5.8.RELEASE
> 2.20.1
> {code}
> from("direct:sendToKafka")
> .setBody(constant("Message from Camel to Kafka"))
> .setHeader(KafkaConstants.KEY, constant("Camel"))
> .to("kafka:TESTTOPIC?configuration=#kafkaConfiguration");
> {code}
> {code}
> 2017-12-11 14:16:35.466 ERROR 12048 --- [ad #1 - WireTap] CamelRouter 
>  : Exchange[ExchangePattern: InOnly, BodyType: String, 
> Body: Message from Camel to Kafka, CaughtExceptionType: 
> org.apache.camel.CamelExchangeException, CaughtExcept
> ionMessage: No topic key set. Exchange[ID-5CG7383K6H00BA-1512994577303-0-3], 
> StackTrace: org.apache.camel.CamelExchangeException: No topic key set. 
> Exchange[ID-5CG7383K6H00BA-1512994577303-0-3]
> at 
> org.apache.camel.component.kafka.KafkaProducer.createRecorder(KafkaProducer.java:149)
> at 
> org.apache.camel.component.kafka.KafkaProducer.process(KafkaProducer.java:251)
> at 
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
> at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at 
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
> at 
> org.apache.camel.processor.SendDynamicProcessor$1.doInAsyncProducer(SendDynamicProcessor.java:132)
> at 
> org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:445)
> at 
> org.apache.camel.processor.SendDynamicProcessor.process(SendDynamicProcessor.java:127)
> at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at 
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)
> at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:158)
> at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:153)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12076) Camel Kafka producer: Specified topic is ignored ("No topic key set" error) when KafkaConfiguration is used

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290654#comment-16290654
 ] 

ASF GitHub Bot commented on CAMEL-12076:


oscerd commented on issue #2147: CAMEL-12076: Specified topic is ignored when 
KafkaConfiguration is used
URL: https://github.com/apache/camel/pull/2147#issuecomment-351667236
 
 
   Since we changed to DefaultComponent this fix can be only on 2.21.0, 
backporting to 2.20.x can be a breaking change for users.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Camel Kafka producer: Specified topic is ignored ("No topic key set" error) 
> when KafkaConfiguration is used
> ---
>
> Key: CAMEL-12076
> URL: https://issues.apache.org/jira/browse/CAMEL-12076
> Project: Camel
>  Issue Type: Bug
>  Components: camel-kafka
>Affects Versions: 2.20.1
>Reporter: Igor Lavrentjev
>Assignee: Dmitry Volodin
> Fix For: 2.21.0
>
>
> Specified topic is ignored ("No topic key set" error) when KafkaConfiguration 
> is used. When topic is set inside KafkaConfiguration then no error occurs.
> 1.5.8.RELEASE
> 2.20.1
> {code}
> from("direct:sendToKafka")
> .setBody(constant("Message from Camel to Kafka"))
> .setHeader(KafkaConstants.KEY, constant("Camel"))
> .to("kafka:TESTTOPIC?configuration=#kafkaConfiguration");
> {code}
> {code}
> 2017-12-11 14:16:35.466 ERROR 12048 --- [ad #1 - WireTap] CamelRouter 
>  : Exchange[ExchangePattern: InOnly, BodyType: String, 
> Body: Message from Camel to Kafka, CaughtExceptionType: 
> org.apache.camel.CamelExchangeException, CaughtExcept
> ionMessage: No topic key set. Exchange[ID-5CG7383K6H00BA-1512994577303-0-3], 
> StackTrace: org.apache.camel.CamelExchangeException: No topic key set. 
> Exchange[ID-5CG7383K6H00BA-1512994577303-0-3]
> at 
> org.apache.camel.component.kafka.KafkaProducer.createRecorder(KafkaProducer.java:149)
> at 
> org.apache.camel.component.kafka.KafkaProducer.process(KafkaProducer.java:251)
> at 
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
> at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at 
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
> at 
> org.apache.camel.processor.SendDynamicProcessor$1.doInAsyncProducer(SendDynamicProcessor.java:132)
> at 
> org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:445)
> at 
> org.apache.camel.processor.SendDynamicProcessor.process(SendDynamicProcessor.java:127)
> at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at 
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)
> at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:158)
> at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:153)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (CAMEL-12076) Camel Kafka producer: Specified topic is ignored ("No topic key set" error) when KafkaConfiguration is used

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-12076.
--
Resolution: Fixed

> Camel Kafka producer: Specified topic is ignored ("No topic key set" error) 
> when KafkaConfiguration is used
> ---
>
> Key: CAMEL-12076
> URL: https://issues.apache.org/jira/browse/CAMEL-12076
> Project: Camel
>  Issue Type: Bug
>  Components: camel-kafka
>Affects Versions: 2.20.1
>Reporter: Igor Lavrentjev
>Assignee: Dmitry Volodin
> Fix For: 2.21.0
>
>
> Specified topic is ignored ("No topic key set" error) when KafkaConfiguration 
> is used. When topic is set inside KafkaConfiguration then no error occurs.
> 1.5.8.RELEASE
> 2.20.1
> {code}
> from("direct:sendToKafka")
> .setBody(constant("Message from Camel to Kafka"))
> .setHeader(KafkaConstants.KEY, constant("Camel"))
> .to("kafka:TESTTOPIC?configuration=#kafkaConfiguration");
> {code}
> {code}
> 2017-12-11 14:16:35.466 ERROR 12048 --- [ad #1 - WireTap] CamelRouter 
>  : Exchange[ExchangePattern: InOnly, BodyType: String, 
> Body: Message from Camel to Kafka, CaughtExceptionType: 
> org.apache.camel.CamelExchangeException, CaughtExcept
> ionMessage: No topic key set. Exchange[ID-5CG7383K6H00BA-1512994577303-0-3], 
> StackTrace: org.apache.camel.CamelExchangeException: No topic key set. 
> Exchange[ID-5CG7383K6H00BA-1512994577303-0-3]
> at 
> org.apache.camel.component.kafka.KafkaProducer.createRecorder(KafkaProducer.java:149)
> at 
> org.apache.camel.component.kafka.KafkaProducer.process(KafkaProducer.java:251)
> at 
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
> at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at 
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
> at 
> org.apache.camel.processor.SendDynamicProcessor$1.doInAsyncProducer(SendDynamicProcessor.java:132)
> at 
> org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:445)
> at 
> org.apache.camel.processor.SendDynamicProcessor.process(SendDynamicProcessor.java:127)
> at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at 
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)
> at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:158)
> at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:153)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12076) Camel Kafka producer: Specified topic is ignored ("No topic key set" error) when KafkaConfiguration is used

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290649#comment-16290649
 ] 

ASF GitHub Bot commented on CAMEL-12076:


Github user oscerd closed the pull request at:

https://github.com/apache/camel/pull/2147


> Camel Kafka producer: Specified topic is ignored ("No topic key set" error) 
> when KafkaConfiguration is used
> ---
>
> Key: CAMEL-12076
> URL: https://issues.apache.org/jira/browse/CAMEL-12076
> Project: Camel
>  Issue Type: Bug
>  Components: camel-kafka
>Affects Versions: 2.20.1
>Reporter: Igor Lavrentjev
>Assignee: Dmitry Volodin
>
> Specified topic is ignored ("No topic key set" error) when KafkaConfiguration 
> is used. When topic is set inside KafkaConfiguration then no error occurs.
> 1.5.8.RELEASE
> 2.20.1
> {code}
> from("direct:sendToKafka")
> .setBody(constant("Message from Camel to Kafka"))
> .setHeader(KafkaConstants.KEY, constant("Camel"))
> .to("kafka:TESTTOPIC?configuration=#kafkaConfiguration");
> {code}
> {code}
> 2017-12-11 14:16:35.466 ERROR 12048 --- [ad #1 - WireTap] CamelRouter 
>  : Exchange[ExchangePattern: InOnly, BodyType: String, 
> Body: Message from Camel to Kafka, CaughtExceptionType: 
> org.apache.camel.CamelExchangeException, CaughtExcept
> ionMessage: No topic key set. Exchange[ID-5CG7383K6H00BA-1512994577303-0-3], 
> StackTrace: org.apache.camel.CamelExchangeException: No topic key set. 
> Exchange[ID-5CG7383K6H00BA-1512994577303-0-3]
> at 
> org.apache.camel.component.kafka.KafkaProducer.createRecorder(KafkaProducer.java:149)
> at 
> org.apache.camel.component.kafka.KafkaProducer.process(KafkaProducer.java:251)
> at 
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
> at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at 
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
> at 
> org.apache.camel.processor.SendDynamicProcessor$1.doInAsyncProducer(SendDynamicProcessor.java:132)
> at 
> org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:445)
> at 
> org.apache.camel.processor.SendDynamicProcessor.process(SendDynamicProcessor.java:127)
> at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at 
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)
> at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:158)
> at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:153)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12076) Camel Kafka producer: Specified topic is ignored ("No topic key set" error) when KafkaConfiguration is used

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290628#comment-16290628
 ] 

ASF GitHub Bot commented on CAMEL-12076:


dmvolod opened a new pull request #2147: CAMEL-12076: Specified topic is 
ignored when KafkaConfiguration is used
URL: https://github.com/apache/camel/pull/2147
 
 
   If topic property was not received from configuration or header parameters 
take it from the remaining URI. Also some minor code style fixes are applied.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Camel Kafka producer: Specified topic is ignored ("No topic key set" error) 
> when KafkaConfiguration is used
> ---
>
> Key: CAMEL-12076
> URL: https://issues.apache.org/jira/browse/CAMEL-12076
> Project: Camel
>  Issue Type: Bug
>  Components: camel-kafka
>Affects Versions: 2.20.1
>Reporter: Igor Lavrentjev
>Assignee: Dmitry Volodin
>
> Specified topic is ignored ("No topic key set" error) when KafkaConfiguration 
> is used. When topic is set inside KafkaConfiguration then no error occurs.
> 1.5.8.RELEASE
> 2.20.1
> {code}
> from("direct:sendToKafka")
> .setBody(constant("Message from Camel to Kafka"))
> .setHeader(KafkaConstants.KEY, constant("Camel"))
> .to("kafka:TESTTOPIC?configuration=#kafkaConfiguration");
> {code}
> {code}
> 2017-12-11 14:16:35.466 ERROR 12048 --- [ad #1 - WireTap] CamelRouter 
>  : Exchange[ExchangePattern: InOnly, BodyType: String, 
> Body: Message from Camel to Kafka, CaughtExceptionType: 
> org.apache.camel.CamelExchangeException, CaughtExcept
> ionMessage: No topic key set. Exchange[ID-5CG7383K6H00BA-1512994577303-0-3], 
> StackTrace: org.apache.camel.CamelExchangeException: No topic key set. 
> Exchange[ID-5CG7383K6H00BA-1512994577303-0-3]
> at 
> org.apache.camel.component.kafka.KafkaProducer.createRecorder(KafkaProducer.java:149)
> at 
> org.apache.camel.component.kafka.KafkaProducer.process(KafkaProducer.java:251)
> at 
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
> at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at 
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
> at 
> org.apache.camel.processor.SendDynamicProcessor$1.doInAsyncProducer(SendDynamicProcessor.java:132)
> at 
> org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:445)
> at 
> org.apache.camel.processor.SendDynamicProcessor.process(SendDynamicProcessor.java:127)
> at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at 
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)
> at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:158)
> at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:153)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12076) Camel Kafka producer: Specified topic is ignored ("No topic key set" error) when KafkaConfiguration is used

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290629#comment-16290629
 ] 

ASF GitHub Bot commented on CAMEL-12076:


GitHub user dmvolod opened a pull request:

https://github.com/apache/camel/pull/2147

CAMEL-12076: Specified topic is ignored when KafkaConfiguration is used

If topic property was not received from configuration or header parameters 
take it from the remaining URI. Also some minor code style fixes are applied.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dmvolod/camel CAMEL-12076

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/2147.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2147


commit ed9d4d6fe5f4ccc9975c62b89a145beebf079ef2
Author: Dmitry Volodin 
Date:   2017-12-14T09:43:50Z

CAMEL-12076: Specified topic is ignored when KafkaConfiguration is used




> Camel Kafka producer: Specified topic is ignored ("No topic key set" error) 
> when KafkaConfiguration is used
> ---
>
> Key: CAMEL-12076
> URL: https://issues.apache.org/jira/browse/CAMEL-12076
> Project: Camel
>  Issue Type: Bug
>  Components: camel-kafka
>Affects Versions: 2.20.1
>Reporter: Igor Lavrentjev
>Assignee: Dmitry Volodin
>
> Specified topic is ignored ("No topic key set" error) when KafkaConfiguration 
> is used. When topic is set inside KafkaConfiguration then no error occurs.
> 1.5.8.RELEASE
> 2.20.1
> {code}
> from("direct:sendToKafka")
> .setBody(constant("Message from Camel to Kafka"))
> .setHeader(KafkaConstants.KEY, constant("Camel"))
> .to("kafka:TESTTOPIC?configuration=#kafkaConfiguration");
> {code}
> {code}
> 2017-12-11 14:16:35.466 ERROR 12048 --- [ad #1 - WireTap] CamelRouter 
>  : Exchange[ExchangePattern: InOnly, BodyType: String, 
> Body: Message from Camel to Kafka, CaughtExceptionType: 
> org.apache.camel.CamelExchangeException, CaughtExcept
> ionMessage: No topic key set. Exchange[ID-5CG7383K6H00BA-1512994577303-0-3], 
> StackTrace: org.apache.camel.CamelExchangeException: No topic key set. 
> Exchange[ID-5CG7383K6H00BA-1512994577303-0-3]
> at 
> org.apache.camel.component.kafka.KafkaProducer.createRecorder(KafkaProducer.java:149)
> at 
> org.apache.camel.component.kafka.KafkaProducer.process(KafkaProducer.java:251)
> at 
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:148)
> at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:138)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:101)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at 
> org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:62)
> at 
> org.apache.camel.processor.SendDynamicProcessor$1.doInAsyncProducer(SendDynamicProcessor.java:132)
> at 
> org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:445)
> at 
> org.apache.camel.processor.SendDynamicProcessor.process(SendDynamicProcessor.java:127)
> at 
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:548)
> at 
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:201)
> at 
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:97)
> at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:158)
> at 
> org.apache.camel.processor.WireTapProcessor$1.call(WireTapProcessor.java:153)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (CAMEL-12082) Camel route commands should set the TCCL when working with local camel context

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290622#comment-16290622
 ] 

ASF GitHub Bot commented on CAMEL-12082:


johnpoth commented on issue #2146: [CAMEL-12082] Set the TCCL to the 
application classloader when execut…
URL: https://github.com/apache/camel/pull/2146#issuecomment-351658775
 
 
   Thanks @oscerd !


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Camel route commands should set the TCCL when working with local camel context
> --
>
> Key: CAMEL-12082
> URL: https://issues.apache.org/jira/browse/CAMEL-12082
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.20.1
>Reporter: John Poth
>Assignee: John Poth
> Fix For: 2.20.2, 2.21.0
>
>
> This causes class not found issues in Karaf when restarting routes for 
> example:
> {code}
> 13:33:50.734 WARN [pipe-camel:route-start websocket camel-context] unavailable
> java.lang.RuntimeException: Unable to load 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServletFactory$Loader.load(WebSocketServletFactory.java:53)
>  ~[?:?]
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.init(WebSocketServlet.java:138)
>  ~[?:?]
>   at javax.servlet.GenericServlet.init(GenericServlet.java:244) 
> ~[34:javax.servlet-api:3.1.0]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:640) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:419) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1596)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1684)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.addServletWithMapping(ServletHandler.java:1027)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.addServlet(ServletContextHandler.java:437)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.createServlet(WebsocketComponent.java:457)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.addServlet(WebsocketComponent.java:439)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.connect(WebsocketComponent.java:214)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketEndpoint.connect(WebsocketEndpoint.java:123)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketProducer.doStart(WebsocketProducer.java:84)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.deferStartService(DefaultCamelContext.java:1558)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.doAddService(DefaultCamelContext.java:1475)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.addService(DefaultCamelContext.java:1445)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:576) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.acquireProducer(ProducerCache.java:168) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.processor.SendProcessor.doStart(SendProcessor.java:248) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> 

[jira] [Updated] (CAMEL-12082) Camel route commands should set the TCCL when working with local camel context

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-12082:
-
Fix Version/s: 2.21.0
   2.20.2

> Camel route commands should set the TCCL when working with local camel context
> --
>
> Key: CAMEL-12082
> URL: https://issues.apache.org/jira/browse/CAMEL-12082
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.20.1
>Reporter: John Poth
>Assignee: John Poth
> Fix For: 2.20.2, 2.21.0
>
>
> This causes class not found issues in Karaf when restarting routes for 
> example:
> {code}
> 13:33:50.734 WARN [pipe-camel:route-start websocket camel-context] unavailable
> java.lang.RuntimeException: Unable to load 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServletFactory$Loader.load(WebSocketServletFactory.java:53)
>  ~[?:?]
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.init(WebSocketServlet.java:138)
>  ~[?:?]
>   at javax.servlet.GenericServlet.init(GenericServlet.java:244) 
> ~[34:javax.servlet-api:3.1.0]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:640) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:419) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1596)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1684)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.addServletWithMapping(ServletHandler.java:1027)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.addServlet(ServletContextHandler.java:437)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.createServlet(WebsocketComponent.java:457)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.addServlet(WebsocketComponent.java:439)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.connect(WebsocketComponent.java:214)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketEndpoint.connect(WebsocketEndpoint.java:123)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketProducer.doStart(WebsocketProducer.java:84)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.deferStartService(DefaultCamelContext.java:1558)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.doAddService(DefaultCamelContext.java:1475)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.addService(DefaultCamelContext.java:1445)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:576) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.acquireProducer(ProducerCache.java:168) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.processor.SendProcessor.doStart(SendProcessor.java:248) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:60) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:104) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:90) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> 

[jira] [Assigned] (CAMEL-12082) Camel route commands should set the TCCL when working with local camel context

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino reassigned CAMEL-12082:


Assignee: John Poth  (was: Andrea Cosentino)

> Camel route commands should set the TCCL when working with local camel context
> --
>
> Key: CAMEL-12082
> URL: https://issues.apache.org/jira/browse/CAMEL-12082
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.20.1
>Reporter: John Poth
>Assignee: John Poth
> Fix For: 2.20.2, 2.21.0
>
>
> This causes class not found issues in Karaf when restarting routes for 
> example:
> {code}
> 13:33:50.734 WARN [pipe-camel:route-start websocket camel-context] unavailable
> java.lang.RuntimeException: Unable to load 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServletFactory$Loader.load(WebSocketServletFactory.java:53)
>  ~[?:?]
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.init(WebSocketServlet.java:138)
>  ~[?:?]
>   at javax.servlet.GenericServlet.init(GenericServlet.java:244) 
> ~[34:javax.servlet-api:3.1.0]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:640) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:419) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1596)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1684)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.addServletWithMapping(ServletHandler.java:1027)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.addServlet(ServletContextHandler.java:437)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.createServlet(WebsocketComponent.java:457)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.addServlet(WebsocketComponent.java:439)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.connect(WebsocketComponent.java:214)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketEndpoint.connect(WebsocketEndpoint.java:123)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketProducer.doStart(WebsocketProducer.java:84)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.deferStartService(DefaultCamelContext.java:1558)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.doAddService(DefaultCamelContext.java:1475)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.addService(DefaultCamelContext.java:1445)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:576) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.acquireProducer(ProducerCache.java:168) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.processor.SendProcessor.doStart(SendProcessor.java:248) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:60) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:104) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:90) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> 

[jira] [Updated] (CAMEL-12082) Camel route commands should set the TCCL when working with local camel context

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-12082:
-
Affects Version/s: (was: 2.20.2)
   2.20.1

> Camel route commands should set the TCCL when working with local camel context
> --
>
> Key: CAMEL-12082
> URL: https://issues.apache.org/jira/browse/CAMEL-12082
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.20.1
>Reporter: John Poth
>Assignee: John Poth
> Fix For: 2.20.2, 2.21.0
>
>
> This causes class not found issues in Karaf when restarting routes for 
> example:
> {code}
> 13:33:50.734 WARN [pipe-camel:route-start websocket camel-context] unavailable
> java.lang.RuntimeException: Unable to load 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServletFactory$Loader.load(WebSocketServletFactory.java:53)
>  ~[?:?]
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.init(WebSocketServlet.java:138)
>  ~[?:?]
>   at javax.servlet.GenericServlet.init(GenericServlet.java:244) 
> ~[34:javax.servlet-api:3.1.0]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:640) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:419) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1596)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1684)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.addServletWithMapping(ServletHandler.java:1027)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.addServlet(ServletContextHandler.java:437)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.createServlet(WebsocketComponent.java:457)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.addServlet(WebsocketComponent.java:439)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.connect(WebsocketComponent.java:214)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketEndpoint.connect(WebsocketEndpoint.java:123)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketProducer.doStart(WebsocketProducer.java:84)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.deferStartService(DefaultCamelContext.java:1558)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.doAddService(DefaultCamelContext.java:1475)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.addService(DefaultCamelContext.java:1445)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:576) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.acquireProducer(ProducerCache.java:168) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.processor.SendProcessor.doStart(SendProcessor.java:248) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:60) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:104) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:90) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> 

[jira] [Resolved] (CAMEL-12082) Camel route commands should set the TCCL when working with local camel context

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-12082.
--
Resolution: Fixed

> Camel route commands should set the TCCL when working with local camel context
> --
>
> Key: CAMEL-12082
> URL: https://issues.apache.org/jira/browse/CAMEL-12082
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.20.1
>Reporter: John Poth
>Assignee: John Poth
> Fix For: 2.20.2, 2.21.0
>
>
> This causes class not found issues in Karaf when restarting routes for 
> example:
> {code}
> 13:33:50.734 WARN [pipe-camel:route-start websocket camel-context] unavailable
> java.lang.RuntimeException: Unable to load 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServletFactory$Loader.load(WebSocketServletFactory.java:53)
>  ~[?:?]
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.init(WebSocketServlet.java:138)
>  ~[?:?]
>   at javax.servlet.GenericServlet.init(GenericServlet.java:244) 
> ~[34:javax.servlet-api:3.1.0]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:640) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:419) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1596)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1684)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.addServletWithMapping(ServletHandler.java:1027)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.addServlet(ServletContextHandler.java:437)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.createServlet(WebsocketComponent.java:457)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.addServlet(WebsocketComponent.java:439)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.connect(WebsocketComponent.java:214)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketEndpoint.connect(WebsocketEndpoint.java:123)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketProducer.doStart(WebsocketProducer.java:84)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.deferStartService(DefaultCamelContext.java:1558)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.doAddService(DefaultCamelContext.java:1475)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.addService(DefaultCamelContext.java:1445)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:576) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.acquireProducer(ProducerCache.java:168) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.processor.SendProcessor.doStart(SendProcessor.java:248) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:60) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:104) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:90) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.processor.RedeliveryErrorHandler.doStart(RedeliveryErrorHandler.java:1472)
>  

[jira] [Assigned] (CAMEL-12082) Camel route commands should set the TCCL when working with local camel context

[Andrea Cosentino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CAMEL-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino reassigned CAMEL-12082:


Assignee: Andrea Cosentino

> Camel route commands should set the TCCL when working with local camel context
> --
>
> Key: CAMEL-12082
> URL: https://issues.apache.org/jira/browse/CAMEL-12082
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.20.1
>Reporter: John Poth
>Assignee: Andrea Cosentino
> Fix For: 2.20.2, 2.21.0
>
>
> This causes class not found issues in Karaf when restarting routes for 
> example:
> {code}
> 13:33:50.734 WARN [pipe-camel:route-start websocket camel-context] unavailable
> java.lang.RuntimeException: Unable to load 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServletFactory$Loader.load(WebSocketServletFactory.java:53)
>  ~[?:?]
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.init(WebSocketServlet.java:138)
>  ~[?:?]
>   at javax.servlet.GenericServlet.init(GenericServlet.java:244) 
> ~[34:javax.servlet-api:3.1.0]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:640) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:419) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1596)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1684)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.addServletWithMapping(ServletHandler.java:1027)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.addServlet(ServletContextHandler.java:437)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.createServlet(WebsocketComponent.java:457)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.addServlet(WebsocketComponent.java:439)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.connect(WebsocketComponent.java:214)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketEndpoint.connect(WebsocketEndpoint.java:123)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketProducer.doStart(WebsocketProducer.java:84)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.deferStartService(DefaultCamelContext.java:1558)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.doAddService(DefaultCamelContext.java:1475)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.addService(DefaultCamelContext.java:1445)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:576) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.acquireProducer(ProducerCache.java:168) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.processor.SendProcessor.doStart(SendProcessor.java:248) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:60) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:104) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:90) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.processor.RedeliveryErrorHandler.doStart(RedeliveryErrorHandler.java:1472)
>  

[jira] [Commented] (CAMEL-12082) Camel route commands should set the TCCL when working with local camel context

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290616#comment-16290616
 ] 

ASF GitHub Bot commented on CAMEL-12082:


oscerd commented on issue #2146: [CAMEL-12082] Set the TCCL to the application 
classloader when execut…
URL: https://github.com/apache/camel/pull/2146#issuecomment-351657908
 
 
   Thanks for the PR it has been merged into master. I'll backport on 2.20.x too
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Camel route commands should set the TCCL when working with local camel context
> --
>
> Key: CAMEL-12082
> URL: https://issues.apache.org/jira/browse/CAMEL-12082
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.20.2
>Reporter: John Poth
>
> This causes class not found issues in Karaf when restarting routes for 
> example:
> {code}
> 13:33:50.734 WARN [pipe-camel:route-start websocket camel-context] unavailable
> java.lang.RuntimeException: Unable to load 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServletFactory$Loader.load(WebSocketServletFactory.java:53)
>  ~[?:?]
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.init(WebSocketServlet.java:138)
>  ~[?:?]
>   at javax.servlet.GenericServlet.init(GenericServlet.java:244) 
> ~[34:javax.servlet-api:3.1.0]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:640) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:419) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1596)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1684)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.addServletWithMapping(ServletHandler.java:1027)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.addServlet(ServletContextHandler.java:437)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.createServlet(WebsocketComponent.java:457)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.addServlet(WebsocketComponent.java:439)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.connect(WebsocketComponent.java:214)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketEndpoint.connect(WebsocketEndpoint.java:123)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketProducer.doStart(WebsocketProducer.java:84)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.deferStartService(DefaultCamelContext.java:1558)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.doAddService(DefaultCamelContext.java:1475)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.addService(DefaultCamelContext.java:1445)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:576) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.acquireProducer(ProducerCache.java:168) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.processor.SendProcessor.doStart(SendProcessor.java:248) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]

[jira] [Commented] (CAMEL-12082) Camel route commands should set the TCCL when working with local camel context

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290615#comment-16290615
 ] 

ASF GitHub Bot commented on CAMEL-12082:


Github user oscerd closed the pull request at:

https://github.com/apache/camel/pull/2146


> Camel route commands should set the TCCL when working with local camel context
> --
>
> Key: CAMEL-12082
> URL: https://issues.apache.org/jira/browse/CAMEL-12082
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.20.2
>Reporter: John Poth
>
> This causes class not found issues in Karaf when restarting routes for 
> example:
> {code}
> 13:33:50.734 WARN [pipe-camel:route-start websocket camel-context] unavailable
> java.lang.RuntimeException: Unable to load 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServletFactory$Loader.load(WebSocketServletFactory.java:53)
>  ~[?:?]
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.init(WebSocketServlet.java:138)
>  ~[?:?]
>   at javax.servlet.GenericServlet.init(GenericServlet.java:244) 
> ~[34:javax.servlet-api:3.1.0]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:640) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:419) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1596)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1684)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.addServletWithMapping(ServletHandler.java:1027)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.addServlet(ServletContextHandler.java:437)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.createServlet(WebsocketComponent.java:457)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.addServlet(WebsocketComponent.java:439)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.connect(WebsocketComponent.java:214)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketEndpoint.connect(WebsocketEndpoint.java:123)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketProducer.doStart(WebsocketProducer.java:84)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.deferStartService(DefaultCamelContext.java:1558)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.doAddService(DefaultCamelContext.java:1475)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.addService(DefaultCamelContext.java:1445)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:576) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.acquireProducer(ProducerCache.java:168) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.processor.SendProcessor.doStart(SendProcessor.java:248) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:60) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:104) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:90) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> 

[jira] [Commented] (CAMEL-12082) Camel route commands should set the TCCL when working with local camel context

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290614#comment-16290614
 ] 

ASF GitHub Bot commented on CAMEL-12082:


oscerd closed pull request #2146: [CAMEL-12082] Set the TCCL to the application 
classloader when execut…
URL: https://github.com/apache/camel/pull/2146
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/platforms/commands/commands-core/src/main/java/org/apache/camel/commands/AbstractRouteCommand.java
 
b/platforms/commands/commands-core/src/main/java/org/apache/camel/commands/AbstractRouteCommand.java
index 74611e8b703..d0da95c57bf 100644
--- 
a/platforms/commands/commands-core/src/main/java/org/apache/camel/commands/AbstractRouteCommand.java
+++ 
b/platforms/commands/commands-core/src/main/java/org/apache/camel/commands/AbstractRouteCommand.java
@@ -22,6 +22,7 @@
 import java.util.List;
 import java.util.Map;
 
+import org.apache.camel.CamelContext;
 import org.apache.camel.commands.internal.RegexUtil;
 
 /**
@@ -53,12 +54,36 @@ public Object execute(CamelController camelController, 
PrintStream out, PrintStr
 for (Map row : camelRoutes) {
 String camelContextName = row.get("camelContextName");
 String routeId = row.get("routeId");
-executeOnRoute(camelController, camelContextName, routeId, out, 
err);
+if (camelController instanceof LocalCamelController) {
+executeLocal((LocalCamelController) camelController, 
camelContextName, routeId, out, err);
+} else {
+executeOnRoute(camelController, camelContextName, routeId, 
out, err);
+}
 }
 
 return null;
 }
 
+private void executeLocal(LocalCamelController camelController, String 
camelContextName, String routeId, PrintStream out, PrintStream err) throws 
Exception {
+CamelContext camelContext = 
camelController.getLocalCamelContext(context);
+if (camelContext == null) {
+err.println("Camel context " + context + " not found.");
+return;
+}
+
+// Setting thread context classloader to the bundle classloader to 
enable legacy code that relies on it
+ClassLoader oldClassloader = 
Thread.currentThread().getContextClassLoader();
+ClassLoader applicationContextClassLoader = 
camelContext.getApplicationContextClassLoader();
+if (applicationContextClassLoader  != null) {
+
Thread.currentThread().setContextClassLoader(applicationContextClassLoader);
+}
+try {
+executeOnRoute(camelController, camelContextName, routeId, out, 
err);
+} finally {
+Thread.currentThread().setContextClassLoader(oldClassloader);
+}
+}
+
 public abstract void executeOnRoute(CamelController camelController, 
String contextName, String routeId, PrintStream out, PrintStream err) throws 
Exception;
 
 /**


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Camel route commands should set the TCCL when working with local camel context
> --
>
> Key: CAMEL-12082
> URL: https://issues.apache.org/jira/browse/CAMEL-12082
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.20.2
>Reporter: John Poth
>
> This causes class not found issues in Karaf when restarting routes for 
> example:
> {code}
> 13:33:50.734 WARN [pipe-camel:route-start websocket camel-context] unavailable
> java.lang.RuntimeException: Unable to load 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServletFactory$Loader.load(WebSocketServletFactory.java:53)
>  ~[?:?]
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.init(WebSocketServlet.java:138)
>  ~[?:?]
>   at javax.servlet.GenericServlet.init(GenericServlet.java:244) 
> ~[34:javax.servlet-api:3.1.0]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:640) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:419) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892) 
> 

[jira] [Commented] (CAMEL-12082) Camel route commands should set the TCCL when working with local camel context

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290610#comment-16290610
 ] 

ASF GitHub Bot commented on CAMEL-12082:


GitHub user johnpoth opened a pull request:

https://github.com/apache/camel/pull/2146

[CAMEL-12082] Set the TCCL to the application classloader when execut…

…ing local route commands

https://issues.apache.org/jira/browse/CAMEL-12082

This is similar to what's being done in 
[AbstractContexCommand](https://github.com/apache/camel/blob/792ce5c5cc0af486b39471cf68206a2e95d3a037/platforms/commands/commands-core/src/main/java/org/apache/camel/commands/AbstractContextCommand.java#L63)
 and 
[DefaultCamelContext](https://github.com/apache/camel/blob/bb39dc44d9603c0e6fce2460ddf35a7b94ca30d4/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L3264)

Thanks!

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/johnpoth/camel CAMEL-12082

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/2146.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2146


commit 0572728f52a2d546cb7c0208c84108c8556643fe
Author: jpoth 
Date:   2017-12-13T17:00:56Z

[CAMEL-12082] Set the TCCL to the application classloader when executing 
local route commands




> Camel route commands should set the TCCL when working with local camel context
> --
>
> Key: CAMEL-12082
> URL: https://issues.apache.org/jira/browse/CAMEL-12082
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.20.2
>Reporter: John Poth
>
> This causes class not found issues in Karaf when restarting routes for 
> example:
> {code}
> 13:33:50.734 WARN [pipe-camel:route-start websocket camel-context] unavailable
> java.lang.RuntimeException: Unable to load 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServletFactory$Loader.load(WebSocketServletFactory.java:53)
>  ~[?:?]
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.init(WebSocketServlet.java:138)
>  ~[?:?]
>   at javax.servlet.GenericServlet.init(GenericServlet.java:244) 
> ~[34:javax.servlet-api:3.1.0]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:640) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:419) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1596)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1684)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.addServletWithMapping(ServletHandler.java:1027)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.addServlet(ServletContextHandler.java:437)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.createServlet(WebsocketComponent.java:457)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.addServlet(WebsocketComponent.java:439)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.connect(WebsocketComponent.java:214)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketEndpoint.connect(WebsocketEndpoint.java:123)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketProducer.doStart(WebsocketProducer.java:84)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.deferStartService(DefaultCamelContext.java:1558)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.doAddService(DefaultCamelContext.java:1475)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> 

[jira] [Commented] (CAMEL-12082) Camel route commands should set the TCCL when working with local camel context

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CAMEL-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16290609#comment-16290609
 ] 

ASF GitHub Bot commented on CAMEL-12082:


johnpoth opened a new pull request #2146: [CAMEL-12082] Set the TCCL to the 
application classloader when execut…
URL: https://github.com/apache/camel/pull/2146
 
 
   …ing local route commands
   
   https://issues.apache.org/jira/browse/CAMEL-12082
   
   This is similar to what's being done in 
[AbstractContexCommand](https://github.com/apache/camel/blob/792ce5c5cc0af486b39471cf68206a2e95d3a037/platforms/commands/commands-core/src/main/java/org/apache/camel/commands/AbstractContextCommand.java#L63)
 and 
[DefaultCamelContext](https://github.com/apache/camel/blob/bb39dc44d9603c0e6fce2460ddf35a7b94ca30d4/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L3264)
   
   Thanks!


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Camel route commands should set the TCCL when working with local camel context
> --
>
> Key: CAMEL-12082
> URL: https://issues.apache.org/jira/browse/CAMEL-12082
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.20.2
>Reporter: John Poth
>
> This causes class not found issues in Karaf when restarting routes for 
> example:
> {code}
> 13:33:50.734 WARN [pipe-camel:route-start websocket camel-context] unavailable
> java.lang.RuntimeException: Unable to load 
> org.eclipse.jetty.websocket.server.WebSocketServerFactory
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServletFactory$Loader.load(WebSocketServletFactory.java:53)
>  ~[?:?]
>   at 
> org.eclipse.jetty.websocket.servlet.WebSocketServlet.init(WebSocketServlet.java:138)
>  ~[?:?]
>   at javax.servlet.GenericServlet.init(GenericServlet.java:244) 
> ~[34:javax.servlet-api:3.1.0]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:640) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:419) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892) 
> [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1596)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1684)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletHandler.addServletWithMapping(ServletHandler.java:1027)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.eclipse.jetty.servlet.ServletContextHandler.addServlet(ServletContextHandler.java:437)
>  [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.createServlet(WebsocketComponent.java:457)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.addServlet(WebsocketComponent.java:439)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketComponent.connect(WebsocketComponent.java:214)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketEndpoint.connect(WebsocketEndpoint.java:123)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.component.websocket.WebsocketProducer.doStart(WebsocketProducer.java:84)
>  [226:org.apache.camel.camel-websocket:2.21.0]
>   at 
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.deferStartService(DefaultCamelContext.java:1558)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.doAddService(DefaultCamelContext.java:1475)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.DefaultCamelContext.addService(DefaultCamelContext.java:1445)
>  [54:org.apache.camel.camel-core:2.21.0]
>   at 
> org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:576) 
> [54:org.apache.camel.camel-core:2.21.0]
>   at 
> 

[jira] [Created] (CAMEL-12082) Camel route commands should set the TCCL when working with local camel context

[John Poth (JIRA)]

John Poth created CAMEL-12082:
-

 Summary: Camel route commands should set the TCCL when working 
with local camel context
 Key: CAMEL-12082
 URL: https://issues.apache.org/jira/browse/CAMEL-12082
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.20.2
Reporter: John Poth


This causes class not found issues in Karaf when restarting routes for example:

{code}
13:33:50.734 WARN [pipe-camel:route-start websocket camel-context] unavailable
java.lang.RuntimeException: Unable to load 
org.eclipse.jetty.websocket.server.WebSocketServerFactory
at 
org.eclipse.jetty.websocket.servlet.WebSocketServletFactory$Loader.load(WebSocketServletFactory.java:53)
 ~[?:?]
at 
org.eclipse.jetty.websocket.servlet.WebSocketServlet.init(WebSocketServlet.java:138)
 ~[?:?]
at javax.servlet.GenericServlet.init(GenericServlet.java:244) 
~[34:javax.servlet-api:3.1.0]
at 
org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:640) 
[241:org.eclipse.jetty.servlet:9.3.15.v20161220]
at 
org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:419) 
[241:org.eclipse.jetty.servlet:9.3.15.v20161220]
at 
org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892) 
[241:org.eclipse.jetty.servlet:9.3.15.v20161220]
at 
org.eclipse.jetty.servlet.ServletHandler.updateMappings(ServletHandler.java:1596)
 [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
at 
org.eclipse.jetty.servlet.ServletHandler.setServletMappings(ServletHandler.java:1684)
 [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
at 
org.eclipse.jetty.servlet.ServletHandler.addServletWithMapping(ServletHandler.java:1027)
 [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
at 
org.eclipse.jetty.servlet.ServletContextHandler.addServlet(ServletContextHandler.java:437)
 [241:org.eclipse.jetty.servlet:9.3.15.v20161220]
at 
org.apache.camel.component.websocket.WebsocketComponent.createServlet(WebsocketComponent.java:457)
 [226:org.apache.camel.camel-websocket:2.21.0]
at 
org.apache.camel.component.websocket.WebsocketComponent.addServlet(WebsocketComponent.java:439)
 [226:org.apache.camel.camel-websocket:2.21.0]
at 
org.apache.camel.component.websocket.WebsocketComponent.connect(WebsocketComponent.java:214)
 [226:org.apache.camel.camel-websocket:2.21.0]
at 
org.apache.camel.component.websocket.WebsocketEndpoint.connect(WebsocketEndpoint.java:123)
 [226:org.apache.camel.camel-websocket:2.21.0]
at 
org.apache.camel.component.websocket.WebsocketProducer.doStart(WebsocketProducer.java:84)
 [226:org.apache.camel.camel-websocket:2.21.0]
at 
org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
[54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
[54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.impl.DefaultCamelContext.deferStartService(DefaultCamelContext.java:1558)
 [54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.impl.DefaultCamelContext.doAddService(DefaultCamelContext.java:1475)
 [54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.impl.DefaultCamelContext.addService(DefaultCamelContext.java:1445)
 [54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:576) 
[54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.impl.ProducerCache.acquireProducer(ProducerCache.java:168) 
[54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.processor.SendProcessor.doStart(SendProcessor.java:248) 
[54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61) 
[54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
[54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:60) 
[54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:104) 
[54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.util.ServiceHelper.startServices(ServiceHelper.java:90) 
[54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.processor.RedeliveryErrorHandler.doStart(RedeliveryErrorHandler.java:1472)
 [54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.support.ChildServiceSupport.start(ChildServiceSupport.java:44) 
[54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.support.ChildServiceSupport.start(ChildServiceSupport.java:31) 
[54:org.apache.camel.camel-core:2.21.0]
at 
org.apache.camel.util.ServiceHelper.startService(ServiceHelper.java:75) 
[54:org.apache.camel.camel-core:2.21.0]
at