[jira] [Resolved] (CAMEL-13468) Exception tag is missing when Camel Java DSL is converted into XML using dumpRouteAsXml() operation
[
https://issues.apache.org/jira/browse/CAMEL-13468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-13468.
-
Resolution: Fixed
Thanks for reporting and the PR
> Exception tag is missing when Camel Java DSL is converted into XML using
> dumpRouteAsXml() operation
> ---
>
> Key: CAMEL-13468
> URL: https://issues.apache.org/jira/browse/CAMEL-13468
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 2.22.4, 3.0.0-M1
>Reporter: Shailendra Kumar singh
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Exception tag is missing when Camel Java DSL is converted into XML using
> dumpRouteAsXml() operation
> #Java DSL route
> {code:java}
> public void configure() {
>
> onException(Exception.class).log("${exception.stacktrace}").logStackTrace(true)
> .handled(true);
>
> from("timer://foo?fixedRate=true=1=101").routeId("test")
> .log("Hello World");
> }
> {code}
> #XML converted by dumpRouteAsXml()
> operation(*java.lang.Exception* tag is missing)
> {code:java}
>
> http://camel.apache.org/schema/spring; customId="true"
> id="test">
> uri="timer://foo?fixedRate=trueperiod=1repeatCount=101"/>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13468) Exception tag is missing when Camel Java DSL is converted into XML using dumpRouteAsXml() operation
[
https://issues.apache.org/jira/browse/CAMEL-13468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13468:
Fix Version/s: 3.0.0-M3
3.0.0
> Exception tag is missing when Camel Java DSL is converted into XML using
> dumpRouteAsXml() operation
> ---
>
> Key: CAMEL-13468
> URL: https://issues.apache.org/jira/browse/CAMEL-13468
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 2.22.4, 3.0.0-M1
>Reporter: Shailendra Kumar singh
>Priority: Major
> Fix For: 3.0.0, 3.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Exception tag is missing when Camel Java DSL is converted into XML using
> dumpRouteAsXml() operation
> #Java DSL route
> {code:java}
> public void configure() {
>
> onException(Exception.class).log("${exception.stacktrace}").logStackTrace(true)
> .handled(true);
>
> from("timer://foo?fixedRate=true=1=101").routeId("test")
> .log("Hello World");
> }
> {code}
> #XML converted by dumpRouteAsXml()
> operation(*java.lang.Exception* tag is missing)
> {code:java}
>
> http://camel.apache.org/schema/spring; customId="true"
> id="test">
> uri="timer://foo?fixedRate=trueperiod=1repeatCount=101"/>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13468) Exception tag is missing when Camel Java DSL is converted into XML using dumpRouteAsXml() operation
[
https://issues.apache.org/jira/browse/CAMEL-13468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13468:
Priority: Minor (was: Major)
> Exception tag is missing when Camel Java DSL is converted into XML using
> dumpRouteAsXml() operation
> ---
>
> Key: CAMEL-13468
> URL: https://issues.apache.org/jira/browse/CAMEL-13468
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 2.22.4, 3.0.0-M1
>Reporter: Shailendra Kumar singh
>Priority: Minor
> Fix For: 3.0.0, 3.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Exception tag is missing when Camel Java DSL is converted into XML using
> dumpRouteAsXml() operation
> #Java DSL route
> {code:java}
> public void configure() {
>
> onException(Exception.class).log("${exception.stacktrace}").logStackTrace(true)
> .handled(true);
>
> from("timer://foo?fixedRate=true=1=101").routeId("test")
> .log("Hello World");
> }
> {code}
> #XML converted by dumpRouteAsXml()
> operation(*java.lang.Exception* tag is missing)
> {code:java}
>
> http://camel.apache.org/schema/spring; customId="true"
> id="test">
> uri="timer://foo?fixedRate=trueperiod=1repeatCount=101"/>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-13468) Exception tag is missing when Camel Java DSL is converted into XML using dumpRouteAsXml() operation
[
https://issues.apache.org/jira/browse/CAMEL-13468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-13468:
---
Assignee: Claus Ibsen
> Exception tag is missing when Camel Java DSL is converted into XML using
> dumpRouteAsXml() operation
> ---
>
> Key: CAMEL-13468
> URL: https://issues.apache.org/jira/browse/CAMEL-13468
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 2.22.4, 3.0.0-M1
>Reporter: Shailendra Kumar singh
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.0.0, 3.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Exception tag is missing when Camel Java DSL is converted into XML using
> dumpRouteAsXml() operation
> #Java DSL route
> {code:java}
> public void configure() {
>
> onException(Exception.class).log("${exception.stacktrace}").logStackTrace(true)
> .handled(true);
>
> from("timer://foo?fixedRate=true=1=101").routeId("test")
> .log("Hello World");
> }
> {code}
> #XML converted by dumpRouteAsXml()
> operation(*java.lang.Exception* tag is missing)
> {code:java}
>
> http://camel.apache.org/schema/spring; customId="true"
> id="test">
> uri="timer://foo?fixedRate=trueperiod=1repeatCount=101"/>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-13468) Exception tag is missing when Camel Java DSL is converted into XML using dumpRouteAsXml() operation
[
https://issues.apache.org/jira/browse/CAMEL-13468?focusedWorklogId=235050=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-235050
]
ASF GitHub Bot logged work on CAMEL-13468:
--
Author: ASF GitHub Bot
Created on: 30/Apr/19 03:44
Start Date: 30/Apr/19 03:44
Worklog Time Spent: 10m
Work Description: davsclaus commented on pull request #2893:
[CAMEL-13468]Exception tag is missing when Camel Java DSL is converte…
URL: https://github.com/apache/camel/pull/2893
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
Issue Time Tracking
---
Worklog Id: (was: 235050)
Time Spent: 20m (was: 10m)
> Exception tag is missing when Camel Java DSL is converted into XML using
> dumpRouteAsXml() operation
> ---
>
> Key: CAMEL-13468
> URL: https://issues.apache.org/jira/browse/CAMEL-13468
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 2.22.4, 3.0.0-M1
>Reporter: Shailendra Kumar singh
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Exception tag is missing when Camel Java DSL is converted into XML using
> dumpRouteAsXml() operation
> #Java DSL route
> {code:java}
> public void configure() {
>
> onException(Exception.class).log("${exception.stacktrace}").logStackTrace(true)
> .handled(true);
>
> from("timer://foo?fixedRate=true=1=101").routeId("test")
> .log("Hello World");
> }
> {code}
> #XML converted by dumpRouteAsXml()
> operation(*java.lang.Exception* tag is missing)
> {code:java}
>
> http://camel.apache.org/schema/spring; customId="true"
> id="test">
> uri="timer://foo?fixedRate=trueperiod=1repeatCount=101"/>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (CAMEL-13468) Exception tag is missing when Camel Java DSL is converted into XML using dumpRouteAsXml() operation
[
https://issues.apache.org/jira/browse/CAMEL-13468?focusedWorklogId=234688=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-234688
]
ASF GitHub Bot logged work on CAMEL-13468:
--
Author: ASF GitHub Bot
Created on: 29/Apr/19 17:13
Start Date: 29/Apr/19 17:13
Worklog Time Spent: 10m
Work Description: shailendra14k commented on pull request #2893:
[CAMEL-13468]Exception tag is missing when Camel Java DSL is converte…
URL: https://github.com/apache/camel/pull/2893
…d into XML using dumpRouteAsXml() operation
JIRA:- https://issues.apache.org/jira/browse/CAMEL-13468
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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
Issue Time Tracking
---
Worklog Id: (was: 234688)
Time Spent: 10m
Remaining Estimate: 0h
> Exception tag is missing when Camel Java DSL is converted into XML using
> dumpRouteAsXml() operation
> ---
>
> Key: CAMEL-13468
> URL: https://issues.apache.org/jira/browse/CAMEL-13468
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 2.22.4, 3.0.0-M1
>Reporter: Shailendra Kumar singh
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Exception tag is missing when Camel Java DSL is converted into XML using
> dumpRouteAsXml() operation
> #Java DSL route
> {code:java}
> public void configure() {
>
> onException(Exception.class).log("${exception.stacktrace}").logStackTrace(true)
> .handled(true);
>
> from("timer://foo?fixedRate=true=1=101").routeId("test")
> .log("Hello World");
> }
> {code}
> #XML converted by dumpRouteAsXml()
> operation(*java.lang.Exception* tag is missing)
> {code:java}
>
> http://camel.apache.org/schema/spring; customId="true"
> id="test">
> uri="timer://foo?fixedRate=trueperiod=1repeatCount=101"/>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13468) Exception tag is missing when Camel Java DSL is converted into XML using dumpRouteAsXml() operation
Shailendra Kumar singh created CAMEL-13468:
--
Summary: Exception tag is missing when Camel Java DSL is converted
into XML using dumpRouteAsXml() operation
Key: CAMEL-13468
URL: https://issues.apache.org/jira/browse/CAMEL-13468
Project: Camel
Issue Type: Bug
Components: came-core
Affects Versions: 3.0.0-M1, 2.22.4
Reporter: Shailendra Kumar singh
Exception tag is missing when Camel Java DSL is converted into XML using
dumpRouteAsXml() operation
#Java DSL route
{code:java}
public void configure() {
onException(Exception.class).log("${exception.stacktrace}").logStackTrace(true)
.handled(true);
from("timer://foo?fixedRate=true=1=101").routeId("test")
.log("Hello World");
}
{code}
#XML converted by dumpRouteAsXml()
operation(*java.lang.Exception* tag is missing)
{code:java}
http://camel.apache.org/schema/spring; customId="true" id="test">
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (CAMEL-12764) camel-http4: basic auth no longer working when used in combination with a dynamic to
[
https://issues.apache.org/jira/browse/CAMEL-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pascal Schumacher closed CAMEL-12764.
-
Resolution: Fixed
> camel-http4: basic auth no longer working when used in combination with a
> dynamic to
>
>
> Key: CAMEL-12764
> URL: https://issues.apache.org/jira/browse/CAMEL-12764
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 2.22.0, 2.22.1
>Reporter: Pascal Schumacher
>Priority: Major
> Labels: regresion
> Fix For: 2.23.2
>
>
> After upgrading a Spring Boot Project from Camel 2.21.1 to Camel 2.22.0 basic
> authentication of the http4 component stopped working when it is used in
> combination with a dynamic to.
> My (slightly simplified) route:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE,
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
>
> .toD("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/${exchangeProperty.my_id}");
> {code}
> When I change the route and remove the dynamic to everything works fine again:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE,
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
> .setHeader(Exchange.HTTP_PATH, exchangeProperty("my_id"))
> .to("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/");
> {code}
> Maybe this regression was caused by CAMEL-12462?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12764) camel-http4: basic auth no longer working when used in combination with a dynamic to
[
https://issues.apache.org/jira/browse/CAMEL-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829325#comment-16829325
]
Pascal Schumacher commented on CAMEL-12764:
---
I tried with Camel 2.23.2 and it now works again.
> camel-http4: basic auth no longer working when used in combination with a
> dynamic to
>
>
> Key: CAMEL-12764
> URL: https://issues.apache.org/jira/browse/CAMEL-12764
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 2.22.0, 2.22.1
>Reporter: Pascal Schumacher
>Priority: Major
> Labels: regresion
> Fix For: 2.23.2
>
>
> After upgrading a Spring Boot Project from Camel 2.21.1 to Camel 2.22.0 basic
> authentication of the http4 component stopped working when it is used in
> combination with a dynamic to.
> My (slightly simplified) route:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE,
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
>
> .toD("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/${exchangeProperty.my_id}");
> {code}
> When I change the route and remove the dynamic to everything works fine again:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE,
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
> .setHeader(Exchange.HTTP_PATH, exchangeProperty("my_id"))
> .to("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/");
> {code}
> Maybe this regression was caused by CAMEL-12462?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12764) camel-http4: basic auth no longer working when used in combination with a dynamic to
[
https://issues.apache.org/jira/browse/CAMEL-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pascal Schumacher updated CAMEL-12764:
--
Fix Version/s: (was: 2.24.0)
2.23.2
> camel-http4: basic auth no longer working when used in combination with a
> dynamic to
>
>
> Key: CAMEL-12764
> URL: https://issues.apache.org/jira/browse/CAMEL-12764
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 2.22.0, 2.22.1
>Reporter: Pascal Schumacher
>Priority: Major
> Labels: regresion
> Fix For: 2.23.2
>
>
> After upgrading a Spring Boot Project from Camel 2.21.1 to Camel 2.22.0 basic
> authentication of the http4 component stopped working when it is used in
> combination with a dynamic to.
> My (slightly simplified) route:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE,
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
>
> .toD("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/${exchangeProperty.my_id}");
> {code}
> When I change the route and remove the dynamic to everything works fine again:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE,
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
> .setHeader(Exchange.HTTP_PATH, exchangeProperty("my_id"))
> .to("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/");
> {code}
> Maybe this regression was caused by CAMEL-12462?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13415) Camel-core bundle uses sun/misc/Unsafe but do not declare Import-Package
[
https://issues.apache.org/jira/browse/CAMEL-13415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829313#comment-16829313
]
Kamil commented on CAMEL-13415:
---
In Eclipse using bndtools workspace
> Camel-core bundle uses sun/misc/Unsafe but do not declare Import-Package
>
>
> Key: CAMEL-13415
> URL: https://issues.apache.org/jira/browse/CAMEL-13415
> Project: Camel
> Issue Type: Bug
> Components: osgi
>Affects Versions: 2.23.1
>Reporter: Kamil
>Priority: Minor
>
> I have very simple OSGI bundle, which uses just camel-core.
> When I run it, an exception is thrown:
> {code:java}
> 20:14:31.684 [Camel Thread #0 - LRUCacheFactory] DEBUG
> org.apache.camel.util.LRUCacheFactory - Warming up LRUCache ...
> Exception in thread "Camel Thread #0 - LRUCacheFactory"
> java.lang.NoClassDefFoundError: sun/misc/Unsafe
> at
> org.apache.camel.com.github.benmanes.caffeine.base.UnsafeAccess.load(UnsafeAccess.java:68)
> at
> org.apache.camel.com.github.benmanes.caffeine.base.UnsafeAccess.(UnsafeAccess.java:42)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.BLCHeader$DrainStatusRef.(BoundedLocalCache.java:3487)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.LocalCacheFactory.newBoundedLocalCache(Unknown
> Source)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache$BoundedLocalManualCache.(BoundedLocalCache.java:3043)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache$BoundedLocalManualCache.(BoundedLocalCache.java:3039)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.Caffeine.build(Caffeine.java:926)
> at org.apache.camel.util.LRUCache.(LRUCache.java:124)
> at org.apache.camel.util.LRUCache.(LRUCache.java:92)
> at org.apache.camel.util.LRUCache.(LRUCache.java:79)
> at org.apache.camel.util.LRUCache.(LRUCache.java:66)
> at org.apache.camel.util.LRUCacheFactory.newLRUCache(LRUCacheFactory.java:89)
> at
> org.apache.camel.util.LRUCacheFactory.lambda$warmUp$0(LRUCacheFactory.java:66)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.ClassNotFoundException: sun.misc.Unsafe cannot be found
> by org.apache.camel.camel-core_2.23.1
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:511)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:414)
> at
> org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:153)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> ... 18 more
> ! Failed to start bundle adapters.service-0.0.1, exception activator error
> Could not initialize class
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache from:
> sun.reflect.NativeConstructorAccessorImpl:newInstance0#-2
> org.osgi.framework.BundleException: Exception in
> adapters.service.Activator.start() of bundle adapters.service.
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:803)
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:732)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1005)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:357)
> at org.eclipse.osgi.container.Module.doStart(Module.java:584)
> at org.eclipse.osgi.container.Module.start(Module.java:452)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:431)
> at aQute.launcher.Launcher.startBundles(Launcher.java:519)
> at aQute.launcher.Launcher.activate(Launcher.java:425)
> at aQute.launcher.Launcher.run(Launcher.java:303)
> at aQute.launcher.Launcher.main(Launcher.java:149)
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.LocalCacheFactory.newBoundedLocalCache(Unknown
> Source)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache$BoundedLocalManualCache.(BoundedLocalCache.java:3043)
[jira] [Commented] (CAMEL-13464) Problem with Olingo4 and authenticated metadata
[ https://issues.apache.org/jira/browse/CAMEL-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829304#comment-16829304 ] Dmitry Volodin commented on CAMEL-13464: Thanks for report. I can add your fix to upstream or you can create a PR on top of you changes. For test we are working with public based OData v4.0 service, but I'm not aware about auth or any other header-based features for it, but you can try to find. > Problem with Olingo4 and authenticated metadata > --- > > Key: CAMEL-13464 > URL: https://issues.apache.org/jira/browse/CAMEL-13464 > Project: Camel > Issue Type: Bug > Components: camel-olingo4 >Affects Versions: 2.23.2 >Reporter: Remco Schoen >Priority: Minor > Attachments: headers_fix.diff > > > I'm currently working with the Olingo4 component for linking with Microsoft > Dynamics 365 CRM. This OData feed requires authentication to get the > metadata. As I have to refresh the Access Token for authenticating I can not > add it to the configuration, but I'm using the > CamelOlingo4.endpointHttpHeaders header for this. But when the component is > retrieving the metadata it is ignoring the header and it is not able to > authenticate. > If I add the headers to the get metadata request it works. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13464) Problem with Olingo4 and authenticated metadata
[ https://issues.apache.org/jira/browse/CAMEL-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829302#comment-16829302 ] Remco Schoen commented on CAMEL-13464: -- Yup, it is only a problem when getting the EDM, everything else works. > Problem with Olingo4 and authenticated metadata > --- > > Key: CAMEL-13464 > URL: https://issues.apache.org/jira/browse/CAMEL-13464 > Project: Camel > Issue Type: Bug > Components: camel-olingo4 >Affects Versions: 2.23.2 >Reporter: Remco Schoen >Priority: Minor > Attachments: headers_fix.diff > > > I'm currently working with the Olingo4 component for linking with Microsoft > Dynamics 365 CRM. This OData feed requires authentication to get the > metadata. As I have to refresh the Access Token for authenticating I can not > add it to the configuration, but I'm using the > CamelOlingo4.endpointHttpHeaders header for this. But when the component is > retrieving the metadata it is ignoring the header and it is not able to > authenticate. > If I add the headers to the get metadata request it works. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13464) Problem with Olingo4 and authenticated metadata
[ https://issues.apache.org/jira/browse/CAMEL-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829301#comment-16829301 ] Dmitry Volodin commented on CAMEL-13464: Ah, understood, is it related to just for EDM getting only and not for regular requests as described in [Olingo4ComponentTest.java#L280|https://github.com/apache/camel/blob/5fd45068a93973a6fa22ff117bdb04a77a785eb0/components/camel-olingo4/camel-olingo4-component/src/test/java/org/apache/camel/component/olingo4/Olingo4ComponentTest.java#L280]? > Problem with Olingo4 and authenticated metadata > --- > > Key: CAMEL-13464 > URL: https://issues.apache.org/jira/browse/CAMEL-13464 > Project: Camel > Issue Type: Bug > Components: camel-olingo4 >Affects Versions: 2.23.2 >Reporter: Remco Schoen >Priority: Minor > Attachments: headers_fix.diff > > > I'm currently working with the Olingo4 component for linking with Microsoft > Dynamics 365 CRM. This OData feed requires authentication to get the > metadata. As I have to refresh the Access Token for authenticating I can not > add it to the configuration, but I'm using the > CamelOlingo4.endpointHttpHeaders header for this. But when the component is > retrieving the metadata it is ignoring the header and it is not able to > authenticate. > If I add the headers to the get metadata request it works. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13464) Problem with Olingo4 and authenticated metadata
[
https://issues.apache.org/jira/browse/CAMEL-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829295#comment-16829295
]
Remco Schoen commented on CAMEL-13464:
--
This is how I set my header, so yes:
Map endpointHttpHeaders = new HashMap<>()
endpointHttpHeaders.put('AUTHORIZATION', "Bearer
${oDataAuthentication.accessToken}".toString())
exchange.in.headers.put('CamelOlingo4.endpointHttpHeaders', endpointHttpHeaders)
I don't know how to create a simple test-case, I'm not familiar with any mock
odata-services.
I attached the diff how I solved in my project: [^headers_fix.diff]
> Problem with Olingo4 and authenticated metadata
> ---
>
> Key: CAMEL-13464
> URL: https://issues.apache.org/jira/browse/CAMEL-13464
> Project: Camel
> Issue Type: Bug
> Components: camel-olingo4
>Affects Versions: 2.23.2
>Reporter: Remco Schoen
>Priority: Minor
> Attachments: headers_fix.diff
>
>
> I'm currently working with the Olingo4 component for linking with Microsoft
> Dynamics 365 CRM. This OData feed requires authentication to get the
> metadata. As I have to refresh the Access Token for authenticating I can not
> add it to the configuration, but I'm using the
> CamelOlingo4.endpointHttpHeaders header for this. But when the component is
> retrieving the metadata it is ignoring the header and it is not able to
> authenticate.
> If I add the headers to the get metadata request it works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13464) Problem with Olingo4 and authenticated metadata
[ https://issues.apache.org/jira/browse/CAMEL-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remco Schoen updated CAMEL-13464: - Attachment: headers_fix.diff > Problem with Olingo4 and authenticated metadata > --- > > Key: CAMEL-13464 > URL: https://issues.apache.org/jira/browse/CAMEL-13464 > Project: Camel > Issue Type: Bug > Components: camel-olingo4 >Affects Versions: 2.23.2 >Reporter: Remco Schoen >Priority: Minor > Attachments: headers_fix.diff > > > I'm currently working with the Olingo4 component for linking with Microsoft > Dynamics 365 CRM. This OData feed requires authentication to get the > metadata. As I have to refresh the Access Token for authenticating I can not > add it to the configuration, but I'm using the > CamelOlingo4.endpointHttpHeaders header for this. But when the component is > retrieving the metadata it is ignoring the header and it is not able to > authenticate. > If I add the headers to the get metadata request it works. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13467) Camel-box, replace deprecated calls with correct ones
[
https://issues.apache.org/jira/browse/CAMEL-13467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829294#comment-16829294
]
Jiri Ondrusek commented on CAMEL-13467:
---
I'm working on this issue
> Camel-box, replace deprecated calls with correct ones
> --
>
> Key: CAMEL-13467
> URL: https://issues.apache.org/jira/browse/CAMEL-13467
> Project: Camel
> Issue Type: Improvement
> Components: camel-box
>Affects Versions: 3.0.0
>Reporter: Jiri Ondrusek
>Priority: Major
>
> There are 5 calls to depricated APIs iIn camel-box-api module. At least 2 of
> them could be replaced by the correct calls.
> {quote}
> *
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxUsersManager.java
> Warning:(354, 24) java: moveFolderToUser(java.lang.String) in
> com.box.sdk.BoxUser has been deprecated
> *
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxSearchManager.java
> Warning:(83, 44) java: search(java.lang.String) in com.box.sdk.BoxFolder has
> been deprecated
> *
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxFilesManager.java
> Warning:(218, 25) java:
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
> in com.box.sdk.BoxFile has been deprecated
> Warning:(220, 25) java:
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
> in com.box.sdk.BoxFile has been deprecated
> Warning:(223, 21) java: uploadVersion(java.io.InputStream) in
> com.box.sdk.BoxFile has been deprecated
> {quote}
> Inspect all 5 occurrences of deprecated calls and fix them if possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13467) Camel-box, replace deprecated calls with correct ones
Jiri Ondrusek created CAMEL-13467:
-
Summary: Camel-box, replace deprecated calls with correct ones
Key: CAMEL-13467
URL: https://issues.apache.org/jira/browse/CAMEL-13467
Project: Camel
Issue Type: Improvement
Components: camel-box
Affects Versions: 3.0.0
Reporter: Jiri Ondrusek
There are 5 calls to depricated APIs iIn camel-box-api module. At least 2 of
them could be replaced by the correct calls.
{quote}
/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxUsersManager.java
Warning:(354, 24) java: moveFolderToUser(java.lang.String) in
com.box.sdk.BoxUser has been deprecated
/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxSearchManager.java
Warning:(83, 44) java: search(java.lang.String) in com.box.sdk.BoxFolder has
been deprecated
/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxFilesManager.java
Warning:(218, 25) java:
uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
in com.box.sdk.BoxFile has been deprecated
Warning:(220, 25) java:
uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
in com.box.sdk.BoxFile has been deprecated
Warning:(223, 21) java: uploadVersion(java.io.InputStream) in
com.box.sdk.BoxFile has been deprecated
{quote}
Inspect all 5 occurrences of deprecated calls and fix them if possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13467) Camel-box, replace deprecated calls with correct ones
[
https://issues.apache.org/jira/browse/CAMEL-13467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Ondrusek updated CAMEL-13467:
--
Description:
There are 5 calls to depricated APIs iIn camel-box-api module. At least 2 of
them could be replaced by the correct calls.
{quote}
/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxUsersManager.java
* Warning:(354, 24) java: moveFolderToUser(java.lang.String) in
com.box.sdk.BoxUser has been deprecated
/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxSearchManager.java
* Warning:(83, 44) java: search(java.lang.String) in com.box.sdk.BoxFolder has
been deprecated
/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxFilesManager.java
* Warning:(218, 25) java:
uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
in com.box.sdk.BoxFile has been deprecated
* Warning:(220, 25) java:
uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
in com.box.sdk.BoxFile has been deprecated
* Warning:(223, 21) java: uploadVersion(java.io.InputStream) in
com.box.sdk.BoxFile has been deprecated
{quote}
Inspect all 5 occurrences of deprecated calls and fix them if possible.
was:
There are 5 calls to depricated APIs iIn camel-box-api module. At least 2 of
them could be replaced by the correct calls.
{quote}
/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxUsersManager.java
Warning:(354, 24) java: moveFolderToUser(java.lang.String) in
com.box.sdk.BoxUser has been deprecated
/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxSearchManager.java
Warning:(83, 44) java: search(java.lang.String) in com.box.sdk.BoxFolder has
been deprecated
/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxFilesManager.java
Warning:(218, 25) java:
uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
in com.box.sdk.BoxFile has been deprecated
Warning:(220, 25) java:
uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
in com.box.sdk.BoxFile has been deprecated
Warning:(223, 21) java: uploadVersion(java.io.InputStream) in
com.box.sdk.BoxFile has been deprecated
{quote}
Inspect all 5 occurrences of deprecated calls and fix them if possible.
> Camel-box, replace deprecated calls with correct ones
> --
>
> Key: CAMEL-13467
> URL: https://issues.apache.org/jira/browse/CAMEL-13467
> Project: Camel
> Issue Type: Improvement
> Components: camel-box
>Affects Versions: 3.0.0
>Reporter: Jiri Ondrusek
>Priority: Major
>
> There are 5 calls to depricated APIs iIn camel-box-api module. At least 2 of
> them could be replaced by the correct calls.
> {quote}
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxUsersManager.java
> * Warning:(354, 24) java: moveFolderToUser(java.lang.String) in
> com.box.sdk.BoxUser has been deprecated
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxSearchManager.java
> * Warning:(83, 44) java: search(java.lang.String) in com.box.sdk.BoxFolder
> has been deprecated
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxFilesManager.java
> * Warning:(218, 25) java:
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
> in com.box.sdk.BoxFile has been deprecated
> * Warning:(220, 25) java:
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
> in com.box.sdk.BoxFile has been deprecated
> * Warning:(223, 21) java: uploadVersion(java.io.InputStream) in
> com.box.sdk.BoxFile has been deprecated
> {quote}
> Inspect all 5 occurrences of deprecated calls and fix them if possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-13467) Camel-box, replace deprecated calls with correct ones
[
https://issues.apache.org/jira/browse/CAMEL-13467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Ondrusek updated CAMEL-13467:
--
Description:
There are 5 calls to depricated APIs iIn camel-box-api module. At least 2 of
them could be replaced by the correct calls.
{quote}
*
/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxUsersManager.java
Warning:(354, 24) java: moveFolderToUser(java.lang.String) in
com.box.sdk.BoxUser has been deprecated
*
/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxSearchManager.java
Warning:(83, 44) java: search(java.lang.String) in com.box.sdk.BoxFolder has
been deprecated
*
/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxFilesManager.java
Warning:(218, 25) java:
uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
in com.box.sdk.BoxFile has been deprecated
Warning:(220, 25) java:
uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
in com.box.sdk.BoxFile has been deprecated
Warning:(223, 21) java: uploadVersion(java.io.InputStream) in
com.box.sdk.BoxFile has been deprecated
{quote}
Inspect all 5 occurrences of deprecated calls and fix them if possible.
was:
There are 5 calls to depricated APIs iIn camel-box-api module. At least 2 of
them could be replaced by the correct calls.
{quote}
/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxUsersManager.java
* Warning:(354, 24) java: moveFolderToUser(java.lang.String) in
com.box.sdk.BoxUser has been deprecated
/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxSearchManager.java
* Warning:(83, 44) java: search(java.lang.String) in com.box.sdk.BoxFolder has
been deprecated
/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxFilesManager.java
* Warning:(218, 25) java:
uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
in com.box.sdk.BoxFile has been deprecated
* Warning:(220, 25) java:
uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
in com.box.sdk.BoxFile has been deprecated
* Warning:(223, 21) java: uploadVersion(java.io.InputStream) in
com.box.sdk.BoxFile has been deprecated
{quote}
Inspect all 5 occurrences of deprecated calls and fix them if possible.
> Camel-box, replace deprecated calls with correct ones
> --
>
> Key: CAMEL-13467
> URL: https://issues.apache.org/jira/browse/CAMEL-13467
> Project: Camel
> Issue Type: Improvement
> Components: camel-box
>Affects Versions: 3.0.0
>Reporter: Jiri Ondrusek
>Priority: Major
>
> There are 5 calls to depricated APIs iIn camel-box-api module. At least 2 of
> them could be replaced by the correct calls.
> {quote}
> *
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxUsersManager.java
> Warning:(354, 24) java: moveFolderToUser(java.lang.String) in
> com.box.sdk.BoxUser has been deprecated
> *
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxSearchManager.java
> Warning:(83, 44) java: search(java.lang.String) in com.box.sdk.BoxFolder has
> been deprecated
> *
> /camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxFilesManager.java
> Warning:(218, 25) java:
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
> in com.box.sdk.BoxFile has been deprecated
> Warning:(220, 25) java:
> uploadVersion(java.io.InputStream,java.util.Date,long,com.box.sdk.ProgressListener)
> in com.box.sdk.BoxFile has been deprecated
> Warning:(223, 21) java: uploadVersion(java.io.InputStream) in
> com.box.sdk.BoxFile has been deprecated
> {quote}
> Inspect all 5 occurrences of deprecated calls and fix them if possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13464) Problem with Olingo4 and authenticated metadata
[ https://issues.apache.org/jira/browse/CAMEL-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829290#comment-16829290 ] Dmitry Volodin commented on CAMEL-13464: [~r.sch...@topdesk.com], have you configured the code like this example [https://github.com/apache/camel/blob/5fd45068a93973a6fa22ff117bdb04a77a785eb0/components/camel-olingo4/camel-olingo4-component/src/test/java/org/apache/camel/component/olingo4/Olingo4ComponentTest.java#L280] If not, please provide a simple reproducer if possible. > Problem with Olingo4 and authenticated metadata > --- > > Key: CAMEL-13464 > URL: https://issues.apache.org/jira/browse/CAMEL-13464 > Project: Camel > Issue Type: Bug > Components: camel-olingo4 >Affects Versions: 2.23.2 >Reporter: Remco Schoen >Priority: Minor > > I'm currently working with the Olingo4 component for linking with Microsoft > Dynamics 365 CRM. This OData feed requires authentication to get the > metadata. As I have to refresh the Access Token for authenticating I can not > add it to the configuration, but I'm using the > CamelOlingo4.endpointHttpHeaders header for this. But when the component is > retrieving the metadata it is ignoring the header and it is not able to > authenticate. > If I add the headers to the get metadata request it works. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (CAMEL-13465) Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String groupMemebershipId) typo in argument name
[ https://issues.apache.org/jira/browse/CAMEL-13465?focusedWorklogId=234531=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-234531 ] ASF GitHub Bot logged work on CAMEL-13465: -- Author: ASF GitHub Bot Created on: 29/Apr/19 14:01 Start Date: 29/Apr/19 14:01 Worklog Time Spent: 10m Work Description: JiriOndrusek commented on pull request #2892: [CAMEL-13465] Camel-box, BoxGroupMembership.Info getGroupMembershipIn… URL: https://github.com/apache/camel/pull/2892 …fo(String groupMemebershipId) typo in argument name Issue: https://issues.apache.org/jira/browse/CAMEL-13465 Typo in API was forcing users to use wrong name of argument in their code. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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 Issue Time Tracking --- Worklog Id: (was: 234531) Time Spent: 10m Remaining Estimate: 0h > Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String > groupMemebershipId) typo in argument name > -- > > Key: CAMEL-13465 > URL: https://issues.apache.org/jira/browse/CAMEL-13465 > Project: Camel > Issue Type: Bug > Components: camel-box >Affects Versions: 3.0.0 >Reporter: Jiri Ondrusek >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > There is a typo in argument of API method BoxGroupMembership.Info > getGroupMembershipInfo(String groupMemebershipId). >>>memEbership<<< > (see > https://github.com/apache/camel/blob/master/components/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxGroupsManager.java#L273) > It forces users to use this "wrong" parameter in their code. > Typo should be fixed, but it also has to be consistent in tests -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13465) Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String groupMemebershipId) typo in argument name
[ https://issues.apache.org/jira/browse/CAMEL-13465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829282#comment-16829282 ] Jiri Ondrusek commented on CAMEL-13465: --- PR: https://github.com/apache/camel/pull/2892 > Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String > groupMemebershipId) typo in argument name > -- > > Key: CAMEL-13465 > URL: https://issues.apache.org/jira/browse/CAMEL-13465 > Project: Camel > Issue Type: Bug > Components: camel-box >Affects Versions: 3.0.0 >Reporter: Jiri Ondrusek >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > There is a typo in argument of API method BoxGroupMembership.Info > getGroupMembershipInfo(String groupMemebershipId). >>>memEbership<<< > (see > https://github.com/apache/camel/blob/master/components/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxGroupsManager.java#L273) > It forces users to use this "wrong" parameter in their code. > Typo should be fixed, but it also has to be consistent in tests -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13466) DefaultCamelContext not stopping all routes on doStop()
[
https://issues.apache.org/jira/browse/CAMEL-13466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Greffe updated CAMEL-13466:
--
Description:
Hello,
after applying CAMEL-12980,
we're still facing an issue with a failing starting feature and the CXFServlet
{{/services}} URL.
To reproduce :
* drop the attached JAR in deploy
* wait for bundle start and failure
* access {{/services}} URL : endpoint + WSDL are listed > is this an expected
behaviour?
For further analysis, it seems to be something missing in camel-core :
When blueprint fails, the {{doStop()}} method is called :
[https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L3506]
At that line, it tries to stop only the routes already started, but not the
ones failing *before* filling {{routeStartupOrder}} List.
[https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L4041]
One of this routes is a CxfConsumer which has already been instanciated, with a
server creation :
[https://github.com/apache/camel/blob/camel-2.20.1/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfConsumer.java#L69]
Even with {{DefaultCamelContext.doStop()}}, the server is still started and
available in {{/services}}.
Tried a fix by adding this line in DefaultCamelContext:3502 :
{code:java}
// fill all the routes to be stopped
getRouteStartupOrder().addAll(routeServices.values().stream().map(this::doPrepareRouteToBeStarted).collect(Collectors.toList()));
// stop route inputs in the same order as they was started so we stop the very
first inputs first
try {
// force shutting down routes as they may otherwise cause shutdown to hang
...
{code}
And now the endpoint isn't available anymore.
But this fix isn't effective enough as the getRouteStartupOrder() may have
duplicates?
Thanks,
was:
Hello,
after applying CAMEL-12980,
we're still facing an issue with a failing starting feature and the CXFServlet
{{/services}} URL.
To reproduce :
* drop the attached JAR in deploy
* wait for bundle start and failure
* access {{/services}} URL : endpoint + WSDL are listed > is this an expected
behaviour?
For further analysis, it seems to be something missing in camel-core :
When blueprint fails, the {{doStop()}} method is called :
[https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L3506]
At that line, it tries to stop only the routes already started, but not the
ones failing *before* filling {{routeStartupOrder}} List.
[https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L4041]
One of this routes is a CxfConsumer which has already been instanciated, with a
server creation :
[https://github.com/apache/camel/blob/camel-2.20.1/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfConsumer.java#L69]
Even with {{doStop()}}, the server is still started and available in
{{/services}}.
Tried a fix by adding this line in DefaultCamelContext:3502 :
{code:java}
// fill all the routes to be stopped
getRouteStartupOrder().addAll(routeServices.values().stream().map(this::doPrepareRouteToBeStarted).collect(Collectors.toList()));
// stop route inputs in the same order as they was started so we stop the very
first inputs first
try {
// force shutting down routes as they may otherwise cause shutdown to hang
...
{code}
And now the endpoint isn't available anymore.
But this fix isn't effective enough as the getRouteStartupOrder() may have
duplicates?
Thanks,
> DefaultCamelContext not stopping all routes on doStop()
> ---
>
> Key: CAMEL-13466
> URL: https://issues.apache.org/jira/browse/CAMEL-13466
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.20.1
>Reporter: Julien Greffe
>Priority: Major
> Attachments: sample-dozer-route-2.0.0-SNAPSHOT.jar
>
>
> Hello,
> after applying CAMEL-12980,
> we're still facing an issue with a failing starting feature and the
> CXFServlet {{/services}} URL.
>
> To reproduce :
> * drop the attached JAR in deploy
> * wait for bundle start and failure
> * access {{/services}} URL : endpoint + WSDL are listed > is this an
> expected behaviour?
>
> For further analysis, it seems to be something missing in camel-core :
> When blueprint fails, the {{doStop()}} method is called :
>
> [https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L3506]
> At that line, it tries to stop only the routes already started, but not the
> ones failing *before* filling {{routeStartupOrder}} List.
>
>
[jira] [Updated] (CAMEL-13466) DefaultCamelContext not stopping all routes on doStop()
[
https://issues.apache.org/jira/browse/CAMEL-13466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Greffe updated CAMEL-13466:
--
Description:
Hello,
after applying CAMEL-12980,
we're still facing an issue with a failing starting feature and the CXFServlet
{{/services}} URL.
To reproduce :
* drop the attached JAR in deploy
* wait for bundle start and failure
* access {{/services}} URL : endpoint + WSDL are listed > is this an expected
behaviour?
For further analysis, it seems to be something missing in camel-core :
When blueprint fails, the {{doStop()}} method is called :
[https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L3506]
At that line, it tries to stop only the routes already started, but not the
ones failing *before* filling {{routeStartupOrder}} List.
[https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L4041]
One of this routes is a CxfConsumer which has already been instanciated, with a
server creation :
[https://github.com/apache/camel/blob/camel-2.20.1/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfConsumer.java#L69]
Even with {{DefaultCamelContext.doStop()}}, the server is still started and
available in {{/services}}.
Tried a fix by adding this line in DefaultCamelContext:3502 :
{code:java}
// fill all the routes to be stopped
getRouteStartupOrder().addAll(routeServices.values().stream().map(this::doPrepareRouteToBeStarted).collect(Collectors.toList()));
// stop route inputs in the same order as they was started so we stop the very
first inputs first
try {
// force shutting down routes as they may otherwise cause shutdown to hang
...
{code}
And now the endpoint isn't available anymore.
But this fix isn't effective enough as {{getRouteStartupOrder()}} may have
duplicates?
Thanks,
was:
Hello,
after applying CAMEL-12980,
we're still facing an issue with a failing starting feature and the CXFServlet
{{/services}} URL.
To reproduce :
* drop the attached JAR in deploy
* wait for bundle start and failure
* access {{/services}} URL : endpoint + WSDL are listed > is this an expected
behaviour?
For further analysis, it seems to be something missing in camel-core :
When blueprint fails, the {{doStop()}} method is called :
[https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L3506]
At that line, it tries to stop only the routes already started, but not the
ones failing *before* filling {{routeStartupOrder}} List.
[https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L4041]
One of this routes is a CxfConsumer which has already been instanciated, with a
server creation :
[https://github.com/apache/camel/blob/camel-2.20.1/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfConsumer.java#L69]
Even with {{DefaultCamelContext.doStop()}}, the server is still started and
available in {{/services}}.
Tried a fix by adding this line in DefaultCamelContext:3502 :
{code:java}
// fill all the routes to be stopped
getRouteStartupOrder().addAll(routeServices.values().stream().map(this::doPrepareRouteToBeStarted).collect(Collectors.toList()));
// stop route inputs in the same order as they was started so we stop the very
first inputs first
try {
// force shutting down routes as they may otherwise cause shutdown to hang
...
{code}
And now the endpoint isn't available anymore.
But this fix isn't effective enough as the getRouteStartupOrder() may have
duplicates?
Thanks,
> DefaultCamelContext not stopping all routes on doStop()
> ---
>
> Key: CAMEL-13466
> URL: https://issues.apache.org/jira/browse/CAMEL-13466
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.20.1
>Reporter: Julien Greffe
>Priority: Major
> Attachments: sample-dozer-route-2.0.0-SNAPSHOT.jar
>
>
> Hello,
> after applying CAMEL-12980,
> we're still facing an issue with a failing starting feature and the
> CXFServlet {{/services}} URL.
>
> To reproduce :
> * drop the attached JAR in deploy
> * wait for bundle start and failure
> * access {{/services}} URL : endpoint + WSDL are listed > is this an
> expected behaviour?
>
> For further analysis, it seems to be something missing in camel-core :
> When blueprint fails, the {{doStop()}} method is called :
>
> [https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L3506]
> At that line, it tries to stop only the routes already started, but not the
> ones failing *before* filling
[jira] [Updated] (CAMEL-13466) DefaultCamelContext not stopping all routes on doStop()
[
https://issues.apache.org/jira/browse/CAMEL-13466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Greffe updated CAMEL-13466:
--
Attachment: sample-dozer-route-2.0.0-SNAPSHOT.jar
> DefaultCamelContext not stopping all routes on doStop()
> ---
>
> Key: CAMEL-13466
> URL: https://issues.apache.org/jira/browse/CAMEL-13466
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.20.1
>Reporter: Julien Greffe
>Priority: Major
> Attachments: sample-dozer-route-2.0.0-SNAPSHOT.jar
>
>
> Hello,
> after applying CAMEL-12980,
> we're still facing an issue with a failing starting feature and the
> CXFServlet {{/services}} URL.
>
> To reproduce :
> * drop the attached JAR in deploy
> * wait for bundle start and failure
> * access {{/services}} URL : endpoint + WSDL are listed > is this an
> expected behaviour?
>
> For further analysis, it seems to be something missing in camel-core :
> When blueprint fails, the {{doStop()}} method is called :
>
> [https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L3506]
> At that line, it tries to stop only the routes already started, but not the
> ones failing *before* filling {{routeStartupOrder}} List.
>
> [https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L4041]
> One of this routes is a CxfConsumer which has already been instanciated, with
> a server creation :
>
> [https://github.com/apache/camel/blob/camel-2.20.1/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfConsumer.java#L69]
> Even with {{doStop()}}, the server is still started and available in
> {{/services}}.
> Tried a fix by adding this line in DefaultCamelContext:3502 :
> {code:java}
> // fill all the routes to be stopped
> getRouteStartupOrder().addAll(routeServices.values().stream().map(this::doPrepareRouteToBeStarted).collect(Collectors.toList()));
> // stop route inputs in the same order as they was started so we stop the
> very first inputs first
> try {
> // force shutting down routes as they may otherwise cause shutdown to hang
> ...
> {code}
> And now the endpoint isn't available anymore.
> But this fix isn't effective enough as the getRouteStartupOrder() may have
> duplicates?
> Thanks,
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-13466) DefaultCamelContext not stopping all routes on doStop()
Julien Greffe created CAMEL-13466:
-
Summary: DefaultCamelContext not stopping all routes on doStop()
Key: CAMEL-13466
URL: https://issues.apache.org/jira/browse/CAMEL-13466
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.20.1
Reporter: Julien Greffe
Attachments: sample-dozer-route-2.0.0-SNAPSHOT.jar
Hello,
after applying CAMEL-12980,
we're still facing an issue with a failing starting feature and the CXFServlet
{{/services}} URL.
To reproduce :
* drop the attached JAR in deploy
* wait for bundle start and failure
* access {{/services}} URL : endpoint + WSDL are listed > is this an expected
behaviour?
For further analysis, it seems to be something missing in camel-core :
When blueprint fails, the {{doStop()}} method is called :
[https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L3506]
At that line, it tries to stop only the routes already started, but not the
ones failing *before* filling {{routeStartupOrder}} List.
[https://github.com/apache/camel/blob/camel-2.20.1/camel-core/src/main/java/org/apache/camel/impl/DefaultCamelContext.java#L4041]
One of this routes is a CxfConsumer which has already been instanciated, with a
server creation :
[https://github.com/apache/camel/blob/camel-2.20.1/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfConsumer.java#L69]
Even with {{doStop()}}, the server is still started and available in
{{/services}}.
Tried a fix by adding this line in DefaultCamelContext:3502 :
{code:java}
// fill all the routes to be stopped
getRouteStartupOrder().addAll(routeServices.values().stream().map(this::doPrepareRouteToBeStarted).collect(Collectors.toList()));
// stop route inputs in the same order as they was started so we stop the very
first inputs first
try {
// force shutting down routes as they may otherwise cause shutdown to hang
...
{code}
And now the endpoint isn't available anymore.
But this fix isn't effective enough as the getRouteStartupOrder() may have
duplicates?
Thanks,
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13465) Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String groupMemebershipId) typo in argument name
[ https://issues.apache.org/jira/browse/CAMEL-13465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829214#comment-16829214 ] Jiri Ondrusek commented on CAMEL-13465: --- I'm working on this issue > Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String > groupMemebershipId) typo in argument name > -- > > Key: CAMEL-13465 > URL: https://issues.apache.org/jira/browse/CAMEL-13465 > Project: Camel > Issue Type: Bug > Components: camel-box >Affects Versions: 3.0.0 >Reporter: Jiri Ondrusek >Priority: Major > > There is a typo in argument of API method BoxGroupMembership.Info > getGroupMembershipInfo(String groupMem*e*bershipId). > (see > https://github.com/apache/camel/blob/master/components/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxGroupsManager.java#L273) > It forces users to use this _wrong_ parameter in their code. > Typo should be fixed, but it also has to be consistent in tests -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13465) Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String groupMemebershipId) typo in argument name
Jiri Ondrusek created CAMEL-13465: - Summary: Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String groupMemebershipId) typo in argument name Key: CAMEL-13465 URL: https://issues.apache.org/jira/browse/CAMEL-13465 Project: Camel Issue Type: Bug Components: camel-box Affects Versions: 3.0.0 Reporter: Jiri Ondrusek There is a typo in argument of API method BoxGroupMembership.Info getGroupMembershipInfo(String groupMem*e*bershipId). (see https://github.com/apache/camel/blob/master/components/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxGroupsManager.java#L273) It forces users to use this _wrong_ parameter in their code. Typo should be fixed, but it also has to be consistent in tests -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13465) Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String groupMemebershipId) typo in argument name
[ https://issues.apache.org/jira/browse/CAMEL-13465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Ondrusek updated CAMEL-13465: -- Description: There is a typo in argument of API method BoxGroupMembership.Info getGroupMembershipInfo(String groupMemebershipId). (see https://github.com/apache/camel/blob/master/components/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxGroupsManager.java#L273) It forces users to use this "wrong" parameter in their code. Typo should be fixed, but it also has to be consistent in tests was: There is a typo in argument of API method BoxGroupMembership.Info getGroupMembershipInfo(String groupMem*e*bershipId). (see https://github.com/apache/camel/blob/master/components/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxGroupsManager.java#L273) It forces users to use this _wrong_ parameter in their code. Typo should be fixed, but it also has to be consistent in tests > Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String > groupMemebershipId) typo in argument name > -- > > Key: CAMEL-13465 > URL: https://issues.apache.org/jira/browse/CAMEL-13465 > Project: Camel > Issue Type: Bug > Components: camel-box >Affects Versions: 3.0.0 >Reporter: Jiri Ondrusek >Priority: Major > > There is a typo in argument of API method BoxGroupMembership.Info > getGroupMembershipInfo(String groupMemebershipId). > (see > https://github.com/apache/camel/blob/master/components/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxGroupsManager.java#L273) > It forces users to use this "wrong" parameter in their code. > Typo should be fixed, but it also has to be consistent in tests -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13465) Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String groupMemebershipId) typo in argument name
[ https://issues.apache.org/jira/browse/CAMEL-13465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Ondrusek updated CAMEL-13465: -- Description: There is a typo in argument of API method BoxGroupMembership.Info getGroupMembershipInfo(String groupMemebershipId). >>>memEbership<<< (see https://github.com/apache/camel/blob/master/components/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxGroupsManager.java#L273) It forces users to use this "wrong" parameter in their code. Typo should be fixed, but it also has to be consistent in tests was: There is a typo in argument of API method BoxGroupMembership.Info getGroupMembershipInfo(String groupMemebershipId). (see https://github.com/apache/camel/blob/master/components/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxGroupsManager.java#L273) It forces users to use this "wrong" parameter in their code. Typo should be fixed, but it also has to be consistent in tests > Camel-box, BoxGroupMembership.Info getGroupMembershipInfo(String > groupMemebershipId) typo in argument name > -- > > Key: CAMEL-13465 > URL: https://issues.apache.org/jira/browse/CAMEL-13465 > Project: Camel > Issue Type: Bug > Components: camel-box >Affects Versions: 3.0.0 >Reporter: Jiri Ondrusek >Priority: Major > > There is a typo in argument of API method BoxGroupMembership.Info > getGroupMembershipInfo(String groupMemebershipId). >>>memEbership<<< > (see > https://github.com/apache/camel/blob/master/components/camel-box/camel-box-api/src/main/java/org/apache/camel/component/box/api/BoxGroupsManager.java#L273) > It forces users to use this "wrong" parameter in their code. > Typo should be fixed, but it also has to be consistent in tests -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13464) Problem with Olingo4 and authenticated metadata
Remco Schoen created CAMEL-13464: Summary: Problem with Olingo4 and authenticated metadata Key: CAMEL-13464 URL: https://issues.apache.org/jira/browse/CAMEL-13464 Project: Camel Issue Type: Bug Components: camel-olingo4 Affects Versions: 2.23.2 Reporter: Remco Schoen I'm currently working with the Olingo4 component for linking with Microsoft Dynamics 365 CRM. This OData feed requires authentication to get the metadata. As I have to refresh the Access Token for authenticating I can not add it to the configuration, but I'm using the CamelOlingo4.endpointHttpHeaders header for this. But when the component is retrieving the metadata it is ignoring the header and it is not able to authenticate. If I add the headers to the get metadata request it works. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13463) Camel-Google-Bigquery: Add a Karaf feature for it
[ https://issues.apache.org/jira/browse/CAMEL-13463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13463. -- Resolution: Fixed > Camel-Google-Bigquery: Add a Karaf feature for it > - > > Key: CAMEL-13463 > URL: https://issues.apache.org/jira/browse/CAMEL-13463 > Project: Camel > Issue Type: Task > Components: karaf >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.0.0, 3.0.0-M3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13463) Camel-Google-Bigquery: Add a Karaf feature for it
Andrea Cosentino created CAMEL-13463: Summary: Camel-Google-Bigquery: Add a Karaf feature for it Key: CAMEL-13463 URL: https://issues.apache.org/jira/browse/CAMEL-13463 Project: Camel Issue Type: Task Components: karaf Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.0.0, 3.0.0-M3 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13443) Camel Blueprint JUnit Test keeps Filelock after Test
[ https://issues.apache.org/jira/browse/CAMEL-13443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829071#comment-16829071 ] Claus Ibsen commented on CAMEL-13443: - Okay try to look in the camel-test-blueprint source code and see if there is some place something needs to be closed when the test stops, there may be some file streams etc that should be closed. > Camel Blueprint JUnit Test keeps Filelock after Test > > > Key: CAMEL-13443 > URL: https://issues.apache.org/jira/browse/CAMEL-13443 > Project: Camel > Issue Type: Bug > Components: camel-test >Affects Versions: 2.23.1 >Reporter: Florian Wermelskirchen >Priority: Minor > > I use CamelBlueprintTestSupport for my JUnit Tests. CamelBlueprintTestSupport > keeps FileLocks on jar Files in target/test-bundles. Due to this, my Tests > fails on Jenkins, because of FileNotFoundException (too many open files). My > current workaround is to Run every Test in a single JVM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13443) Camel Blueprint JUnit Test keeps Filelock after Test
[ https://issues.apache.org/jira/browse/CAMEL-13443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829059#comment-16829059 ] Florian Wermelskirchen commented on CAMEL-13443: One Jar is named like my test Class and it contains only my blueprint.xml in OSGI-INF. The other one is named configAdminInitBundle. I guess they are created in CamelBlueprintHelper createConfigAdminInitBundle and createTestBundle > Camel Blueprint JUnit Test keeps Filelock after Test > > > Key: CAMEL-13443 > URL: https://issues.apache.org/jira/browse/CAMEL-13443 > Project: Camel > Issue Type: Bug > Components: camel-test >Affects Versions: 2.23.1 >Reporter: Florian Wermelskirchen >Priority: Minor > > I use CamelBlueprintTestSupport for my JUnit Tests. CamelBlueprintTestSupport > keeps FileLocks on jar Files in target/test-bundles. Due to this, my Tests > fails on Jenkins, because of FileNotFoundException (too many open files). My > current workaround is to Run every Test in a single JVM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13343) warning: current version of Yarn is out of date
[ https://issues.apache.org/jira/browse/CAMEL-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13343. - Resolution: Fixed > warning: current version of Yarn is out of date > --- > > Key: CAMEL-13343 > URL: https://issues.apache.org/jira/browse/CAMEL-13343 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Nayananga Muhandiram >Priority: Minor > Attachments: Screenshot from 2019-03-19 20-51-01.png, Screenshot from > 2019-03-19 21-05-00.png > > Time Spent: 20m > Remaining Estimate: 0h > > yarn new version available > > yarn install > yarn install v1.14.0 > [1/5] Resolving packages... > [2/5] Fetching packages... > info fsevents@1.2.4: The platform "linux" is incompatible with this module. > info "fsevents@1.2.4" is an optional dependency and failed compatibility > check. Excluding it from installation. > [3/5] Linking dependencies... > [5/5] Building fresh packages... > warning Your current version of Yarn is out of date. The latest version is > "1.15.2", while you're on "1.14.0". > Done in 977.20s. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13459) camel3 - Move language annotations for bean parameter bindings into their own package
[ https://issues.apache.org/jira/browse/CAMEL-13459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13459. - Resolution: Fixed > camel3 - Move language annotations for bean parameter bindings into their own > package > - > > Key: CAMEL-13459 > URL: https://issues.apache.org/jira/browse/CAMEL-13459 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.0.0, 3.0.0-M3 > > > We have @Simple @Constant and @SpEL that are in the root package of language. > They should be moved to their sub package, and @SpEL moved to camel-spring -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13415) Camel-core bundle uses sun/misc/Unsafe but do not declare Import-Package
[
https://issues.apache.org/jira/browse/CAMEL-13415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13415:
Component/s: (was: camel-core)
osgi
> Camel-core bundle uses sun/misc/Unsafe but do not declare Import-Package
>
>
> Key: CAMEL-13415
> URL: https://issues.apache.org/jira/browse/CAMEL-13415
> Project: Camel
> Issue Type: Bug
> Components: osgi
>Affects Versions: 2.23.1
>Reporter: Kamil
>Priority: Minor
>
> I have very simple OSGI bundle, which uses just camel-core.
> When I run it, an exception is thrown:
> {code:java}
> 20:14:31.684 [Camel Thread #0 - LRUCacheFactory] DEBUG
> org.apache.camel.util.LRUCacheFactory - Warming up LRUCache ...
> Exception in thread "Camel Thread #0 - LRUCacheFactory"
> java.lang.NoClassDefFoundError: sun/misc/Unsafe
> at
> org.apache.camel.com.github.benmanes.caffeine.base.UnsafeAccess.load(UnsafeAccess.java:68)
> at
> org.apache.camel.com.github.benmanes.caffeine.base.UnsafeAccess.(UnsafeAccess.java:42)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.BLCHeader$DrainStatusRef.(BoundedLocalCache.java:3487)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.LocalCacheFactory.newBoundedLocalCache(Unknown
> Source)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache$BoundedLocalManualCache.(BoundedLocalCache.java:3043)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache$BoundedLocalManualCache.(BoundedLocalCache.java:3039)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.Caffeine.build(Caffeine.java:926)
> at org.apache.camel.util.LRUCache.(LRUCache.java:124)
> at org.apache.camel.util.LRUCache.(LRUCache.java:92)
> at org.apache.camel.util.LRUCache.(LRUCache.java:79)
> at org.apache.camel.util.LRUCache.(LRUCache.java:66)
> at org.apache.camel.util.LRUCacheFactory.newLRUCache(LRUCacheFactory.java:89)
> at
> org.apache.camel.util.LRUCacheFactory.lambda$warmUp$0(LRUCacheFactory.java:66)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.ClassNotFoundException: sun.misc.Unsafe cannot be found
> by org.apache.camel.camel-core_2.23.1
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:511)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:414)
> at
> org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:153)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> ... 18 more
> ! Failed to start bundle adapters.service-0.0.1, exception activator error
> Could not initialize class
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache from:
> sun.reflect.NativeConstructorAccessorImpl:newInstance0#-2
> org.osgi.framework.BundleException: Exception in
> adapters.service.Activator.start() of bundle adapters.service.
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:803)
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:732)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1005)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:357)
> at org.eclipse.osgi.container.Module.doStart(Module.java:584)
> at org.eclipse.osgi.container.Module.start(Module.java:452)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:431)
> at aQute.launcher.Launcher.startBundles(Launcher.java:519)
> at aQute.launcher.Launcher.activate(Launcher.java:425)
> at aQute.launcher.Launcher.run(Launcher.java:303)
> at aQute.launcher.Launcher.main(Launcher.java:149)
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.LocalCacheFactory.newBoundedLocalCache(Unknown
> Source)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache$BoundedLocalManualCache.(BoundedLocalCache.java:3043)
>
[jira] [Commented] (CAMEL-13415) Camel-core bundle uses sun/misc/Unsafe but do not declare Import-Package
[
https://issues.apache.org/jira/browse/CAMEL-13415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16828999#comment-16828999
]
Claus Ibsen commented on CAMEL-13415:
-
What osgi container do you run this with?
> Camel-core bundle uses sun/misc/Unsafe but do not declare Import-Package
>
>
> Key: CAMEL-13415
> URL: https://issues.apache.org/jira/browse/CAMEL-13415
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.23.1
>Reporter: Kamil
>Priority: Major
>
> I have very simple OSGI bundle, which uses just camel-core.
> When I run it, an exception is thrown:
> {code:java}
> 20:14:31.684 [Camel Thread #0 - LRUCacheFactory] DEBUG
> org.apache.camel.util.LRUCacheFactory - Warming up LRUCache ...
> Exception in thread "Camel Thread #0 - LRUCacheFactory"
> java.lang.NoClassDefFoundError: sun/misc/Unsafe
> at
> org.apache.camel.com.github.benmanes.caffeine.base.UnsafeAccess.load(UnsafeAccess.java:68)
> at
> org.apache.camel.com.github.benmanes.caffeine.base.UnsafeAccess.(UnsafeAccess.java:42)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.BLCHeader$DrainStatusRef.(BoundedLocalCache.java:3487)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.LocalCacheFactory.newBoundedLocalCache(Unknown
> Source)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache$BoundedLocalManualCache.(BoundedLocalCache.java:3043)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache$BoundedLocalManualCache.(BoundedLocalCache.java:3039)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.Caffeine.build(Caffeine.java:926)
> at org.apache.camel.util.LRUCache.(LRUCache.java:124)
> at org.apache.camel.util.LRUCache.(LRUCache.java:92)
> at org.apache.camel.util.LRUCache.(LRUCache.java:79)
> at org.apache.camel.util.LRUCache.(LRUCache.java:66)
> at org.apache.camel.util.LRUCacheFactory.newLRUCache(LRUCacheFactory.java:89)
> at
> org.apache.camel.util.LRUCacheFactory.lambda$warmUp$0(LRUCacheFactory.java:66)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.ClassNotFoundException: sun.misc.Unsafe cannot be found
> by org.apache.camel.camel-core_2.23.1
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:511)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:414)
> at
> org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:153)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> ... 18 more
> ! Failed to start bundle adapters.service-0.0.1, exception activator error
> Could not initialize class
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache from:
> sun.reflect.NativeConstructorAccessorImpl:newInstance0#-2
> org.osgi.framework.BundleException: Exception in
> adapters.service.Activator.start() of bundle adapters.service.
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:803)
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:732)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1005)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:357)
> at org.eclipse.osgi.container.Module.doStart(Module.java:584)
> at org.eclipse.osgi.container.Module.start(Module.java:452)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:431)
> at aQute.launcher.Launcher.startBundles(Launcher.java:519)
> at aQute.launcher.Launcher.activate(Launcher.java:425)
> at aQute.launcher.Launcher.run(Launcher.java:303)
> at aQute.launcher.Launcher.main(Launcher.java:149)
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.LocalCacheFactory.newBoundedLocalCache(Unknown
> Source)
> at
>
[jira] [Updated] (CAMEL-13415) Camel-core bundle uses sun/misc/Unsafe but do not declare Import-Package
[
https://issues.apache.org/jira/browse/CAMEL-13415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-13415:
Priority: Minor (was: Major)
> Camel-core bundle uses sun/misc/Unsafe but do not declare Import-Package
>
>
> Key: CAMEL-13415
> URL: https://issues.apache.org/jira/browse/CAMEL-13415
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 2.23.1
>Reporter: Kamil
>Priority: Minor
>
> I have very simple OSGI bundle, which uses just camel-core.
> When I run it, an exception is thrown:
> {code:java}
> 20:14:31.684 [Camel Thread #0 - LRUCacheFactory] DEBUG
> org.apache.camel.util.LRUCacheFactory - Warming up LRUCache ...
> Exception in thread "Camel Thread #0 - LRUCacheFactory"
> java.lang.NoClassDefFoundError: sun/misc/Unsafe
> at
> org.apache.camel.com.github.benmanes.caffeine.base.UnsafeAccess.load(UnsafeAccess.java:68)
> at
> org.apache.camel.com.github.benmanes.caffeine.base.UnsafeAccess.(UnsafeAccess.java:42)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.BLCHeader$DrainStatusRef.(BoundedLocalCache.java:3487)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.LocalCacheFactory.newBoundedLocalCache(Unknown
> Source)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache$BoundedLocalManualCache.(BoundedLocalCache.java:3043)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache$BoundedLocalManualCache.(BoundedLocalCache.java:3039)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.Caffeine.build(Caffeine.java:926)
> at org.apache.camel.util.LRUCache.(LRUCache.java:124)
> at org.apache.camel.util.LRUCache.(LRUCache.java:92)
> at org.apache.camel.util.LRUCache.(LRUCache.java:79)
> at org.apache.camel.util.LRUCache.(LRUCache.java:66)
> at org.apache.camel.util.LRUCacheFactory.newLRUCache(LRUCacheFactory.java:89)
> at
> org.apache.camel.util.LRUCacheFactory.lambda$warmUp$0(LRUCacheFactory.java:66)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.lang.ClassNotFoundException: sun.misc.Unsafe cannot be found
> by org.apache.camel.camel-core_2.23.1
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:511)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:414)
> at
> org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:153)
> at java.lang.ClassLoader.loadClass(Unknown Source)
> ... 18 more
> ! Failed to start bundle adapters.service-0.0.1, exception activator error
> Could not initialize class
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache from:
> sun.reflect.NativeConstructorAccessorImpl:newInstance0#-2
> org.osgi.framework.BundleException: Exception in
> adapters.service.Activator.start() of bundle adapters.service.
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:803)
> at
> org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:732)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1005)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:357)
> at org.eclipse.osgi.container.Module.doStart(Module.java:584)
> at org.eclipse.osgi.container.Module.start(Module.java:452)
> at
> org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:431)
> at aQute.launcher.Launcher.startBundles(Launcher.java:519)
> at aQute.launcher.Launcher.activate(Launcher.java:425)
> at aQute.launcher.Launcher.run(Launcher.java:303)
> at aQute.launcher.Launcher.main(Launcher.java:149)
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
> at java.lang.reflect.Constructor.newInstance(Unknown Source)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.LocalCacheFactory.newBoundedLocalCache(Unknown
> Source)
> at
> org.apache.camel.com.github.benmanes.caffeine.cache.BoundedLocalCache$BoundedLocalManualCache.(BoundedLocalCache.java:3043)
> at
>
[jira] [Updated] (CAMEL-13443) Camel Blueprint JUnit Test keeps Filelock after Test
[ https://issues.apache.org/jira/browse/CAMEL-13443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-13443: Priority: Minor (was: Major) > Camel Blueprint JUnit Test keeps Filelock after Test > > > Key: CAMEL-13443 > URL: https://issues.apache.org/jira/browse/CAMEL-13443 > Project: Camel > Issue Type: Bug > Components: camel-test >Affects Versions: 2.23.1 >Reporter: Florian Wermelskirchen >Priority: Minor > > I use CamelBlueprintTestSupport for my JUnit Tests. CamelBlueprintTestSupport > keeps FileLocks on jar Files in target/test-bundles. Due to this, my Tests > fails on Jenkins, because of FileNotFoundException (too many open files). My > current workaround is to Run every Test in a single JVM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13443) Camel Blueprint JUnit Test keeps Filelock after Test
[ https://issues.apache.org/jira/browse/CAMEL-13443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16828998#comment-16828998 ] Claus Ibsen commented on CAMEL-13443: - Are you able to find out which files it has a lock on? I wonder if its the test bundle itself, or the karaf bundles or something. eg if the former its maybe something in camel we can fix, but the latter may be in apache felix/karaf etc. > Camel Blueprint JUnit Test keeps Filelock after Test > > > Key: CAMEL-13443 > URL: https://issues.apache.org/jira/browse/CAMEL-13443 > Project: Camel > Issue Type: Bug > Components: camel-test >Affects Versions: 2.23.1 >Reporter: Florian Wermelskirchen >Priority: Major > > I use CamelBlueprintTestSupport for my JUnit Tests. CamelBlueprintTestSupport > keeps FileLocks on jar Files in target/test-bundles. Due to this, my Tests > fails on Jenkins, because of FileNotFoundException (too many open files). My > current workaround is to Run every Test in a single JVM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-13459) camel3 - Move language annotations for bean parameter bindings into their own package
[ https://issues.apache.org/jira/browse/CAMEL-13459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-13459: --- Assignee: Claus Ibsen > camel3 - Move language annotations for bean parameter bindings into their own > package > - > > Key: CAMEL-13459 > URL: https://issues.apache.org/jira/browse/CAMEL-13459 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.0.0, 3.0.0-M3 > > > We have @Simple @Constant and @SpEL that are in the root package of language. > They should be moved to their sub package, and @SpEL moved to camel-spring -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12504) Test Apache Camel on Java 9 and newer
[ https://issues.apache.org/jira/browse/CAMEL-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-12504: --- Assignee: John Poth > Test Apache Camel on Java 9 and newer > - > > Key: CAMEL-12504 > URL: https://issues.apache.org/jira/browse/CAMEL-12504 > Project: Camel > Issue Type: Test > Components: build system >Reporter: Luca Burgazzoli >Assignee: John Poth >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-11262) camel-google-pubsub - Improve to work with streaming mode
[ https://issues.apache.org/jira/browse/CAMEL-11262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11262: Fix Version/s: (was: 2.24.0) > camel-google-pubsub - Improve to work with streaming mode > - > > Key: CAMEL-11262 > URL: https://issues.apache.org/jira/browse/CAMEL-11262 > Project: Camel > Issue Type: Improvement > Components: camel-google-pubsub >Affects Versions: 2.19.0 >Reporter: Claus Ibsen >Priority: Major > > The pubsub component > https://github.com/apache/camel/tree/master/components/camel-google-pubsub > Can likely be improved to work better with streaming mode and use Camel > asynchronous processing. > There may be other things. > Ray Tsang from Google has some ideas and want to help out. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12504) Test Apache Camel on Java 9 and newer
[ https://issues.apache.org/jira/browse/CAMEL-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12504: Fix Version/s: (was: 2.24.0) > Test Apache Camel on Java 9 and newer > - > > Key: CAMEL-12504 > URL: https://issues.apache.org/jira/browse/CAMEL-12504 > Project: Camel > Issue Type: Test > Components: build system >Reporter: Luca Burgazzoli >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-11647) SupervisingRouteController : add JMX support
[ https://issues.apache.org/jira/browse/CAMEL-11647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11647: Fix Version/s: (was: 2.24.0) 3.0.0 > SupervisingRouteController : add JMX support > > > Key: CAMEL-11647 > URL: https://issues.apache.org/jira/browse/CAMEL-11647 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-spring-boot >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Major > Labels: route-controller > Fix For: 3.0.0 > > > SupervisingRouteController should expose info about routes it is supervising > like: > - the back-off configuration > - the status > - when the next restart will happens (i.e. nb of seconds till attempt) > - the last error/stack trace > Camel Spring Boot should leverage this and expose the same information from > an Endpoints -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-11886) Post guide on how to contribute to documentation updates
[ https://issues.apache.org/jira/browse/CAMEL-11886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11886: Fix Version/s: (was: 2.24.0) 3.0.0 > Post guide on how to contribute to documentation updates > > > Key: CAMEL-11886 > URL: https://issues.apache.org/jira/browse/CAMEL-11886 > Project: Camel > Issue Type: Task > Components: documentation, website >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.0.0 > > > As we migrate from wiki to adoc files we should have a better guide on how to > update or contribute to the documentation. > Also we should post a news on the Camel front page about this, so users can > better know the state of the docs - as the old wiki is toasted and unfixable > at this moment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-11780) camel-amqp - SSL Transport configuration
[ https://issues.apache.org/jira/browse/CAMEL-11780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11780: Fix Version/s: (was: 2.24.0) > camel-amqp - SSL Transport configuration > > > Key: CAMEL-11780 > URL: https://issues.apache.org/jira/browse/CAMEL-11780 > Project: Camel > Issue Type: Improvement > Components: camel-amqp >Affects Versions: 2.19.2 >Reporter: Cyril EDME >Assignee: Viral Gohel >Priority: Major > > Hi, > i'm using camel and specially the amqp component to consume a topic. > Everything is working well but I'm confused regarding the SSL configuration. > It's not clear in the documentation, I don't want to use the default JVM > certificate storage so I tried to configure the connection factory with the > [qpid > documentation|https://qpid.apache.org/releases/qpid-jms-0.24.0/docs/index.html#ssl-transport-configuration-options] > but the qpid-jms-client version used by amqp component (0.11.1) doesn't > handle the amqps schema URI. > There is another way to configure the SSL transport like the key store > location and password without a qpid upgrade ? > Thanks ! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-11780) camel-amqp - SSL Transport configuration
[ https://issues.apache.org/jira/browse/CAMEL-11780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-11780: --- Assignee: (was: Viral Gohel) > camel-amqp - SSL Transport configuration > > > Key: CAMEL-11780 > URL: https://issues.apache.org/jira/browse/CAMEL-11780 > Project: Camel > Issue Type: Improvement > Components: camel-amqp >Affects Versions: 2.19.2 >Reporter: Cyril EDME >Priority: Major > > Hi, > i'm using camel and specially the amqp component to consume a topic. > Everything is working well but I'm confused regarding the SSL configuration. > It's not clear in the documentation, I don't want to use the default JVM > certificate storage so I tried to configure the connection factory with the > [qpid > documentation|https://qpid.apache.org/releases/qpid-jms-0.24.0/docs/index.html#ssl-transport-configuration-options] > but the qpid-jms-client version used by amqp component (0.11.1) doesn't > handle the amqps schema URI. > There is another way to configure the SSL transport like the key store > location and password without a qpid upgrade ? > Thanks ! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-11810) Lifecycle problems for services retrieved from Blueprint container
[
https://issues.apache.org/jira/browse/CAMEL-11810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-11810:
Fix Version/s: (was: 2.24.0)
> Lifecycle problems for services retrieved from Blueprint container
> --
>
> Key: CAMEL-11810
> URL: https://issues.apache.org/jira/browse/CAMEL-11810
> Project: Camel
> Issue Type: Bug
> Components: camel-blueprint
>Reporter: Grzegorz Grzybek
>Assignee: Guillaume Nodet
>Priority: Major
>
> I have a case where one bundle/blueprint-container defines:
> {code:xml}
> class="org.apache.camel.processor.idempotent.MemoryIdempotentRepository"/>
> interface="org.apache.camel.spi.IdempotentRepository"
> ref="messageIdRepositoryImpl" />
> {code}
> and another one defines Camel context with:
> {code:xml}
> interface="org.apache.camel.spi.IdempotentRepository"/>
> http://camel.apache.org/schema/blueprint;>
>
> uri="file://xxx?y=zreadLock=idempotentidempotent=trueidempotentRepository=#messageIdRepositoryother.properties[...]"
> />
> {code}
> The problem is that when bundle defining {{messageIdRepositoryImpl}} is
> stopped, stopping bundle/blueprint-container with camel context that
> references {{messageIdRepositoryImpl}} leads to wait on Proxy/ReferenceRecipe:
> {noformat}
> org.osgi.service.blueprint.container.ServiceUnavailableException: Timeout
> expired when waiting for mandatory OSGi service reference:
> (objectClass=org.apache.camel.spi.IdempotentRepository)
> at
> org.apache.aries.blueprint.container.ReferenceRecipe.getService(ReferenceRecipe.java:234)
> at
> org.apache.aries.blueprint.container.ReferenceRecipe.access$000(ReferenceRecipe.java:56)
> at
> org.apache.aries.blueprint.container.ReferenceRecipe$ServiceDispatcher.call(ReferenceRecipe.java:306)
> at Proxy28f0d520_9465_4682_9ec1_02ae44e9fa4a.toString(Unknown Source)
> at java.lang.String.valueOf(String.java:2994)[:1.8.0_144]
> at java.lang.StringBuilder.append(StringBuilder.java:131)[:1.8.0_144]
> at
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:3214)
> at
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:3234)
> at
> org.apache.camel.impl.DefaultCamelContext.shutdownServices(DefaultCamelContext.java:3222)
> at
> org.apache.camel.impl.DefaultCamelContext.doStop(DefaultCamelContext.java:3101)
> at org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
> at
> org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:129)
> ...
> {noformat}
> There are few problems here. First - {{GenericFileEndpoint.doStart()}} does
> this:
> {code:java}
> if (idempotentRepository != null) {
> getCamelContext().addService(idempotentRepository, true);
> }
> {code}
> which adds the blueprint recipe (proxy) to
> {{org.apache.camel.impl.DefaultCamelContext#servicesToStop}} without a way to
> specify {{stopOnShutdown=false}}.
> IMO services obtained from OSGi registry should not be tied to lifecycle of
> single context with route having {{#referenceToOsgiOrBlueprintService}} in
> endpoint URI.
> Also - the above stack trace is not retrieved when stopping an osgi service,
> but when log.warning an exception!:
> {code:xml}
> log.warn("Error occurred while shutting down service: " + service + ". This
> exception will be ignored.", e);
> {code}
> In the above code we have implicit {{toString()}} call on service which leads
> to another proxy call which calls
> {{org.apache.aries.blueprint.container.ReferenceRecipe.ServiceDispatcher#call()}}
> → {{org.apache.aries.blueprint.container.ReferenceRecipe#getService()}} →
> {{org.apache.aries.blueprint.container.ReferenceRecipe#monitor.wait(metadata.getTimeout()}}.
> The most obvious fix is to move idempotent repository to a blueprint file
> where file endpoint is used.
> But as OSGi devil's advocate, I suggest more generic solution: when looking
> up objects inside {{org.apache.camel.blueprint.BlueprintContainerRegistry}},
> in addition to calling
> {{org.osgi.service.blueprint.container.BlueprintContainer#getComponentInstance()}}
> we may check if {{blueprintContainer.getComponentMetadata(name) instanceof
> ReferenceMetadata}} and in such case return a proxied proxy that would
> prevent waiting for blueprint reference when we're stopping the context -
> we'd have to check if the target service is available anyway (why
> ReferenceRecipe doesn't have a method like "tryGetService()"?)...
> Less generic fix could be to add a flag used instead of default:
> {code:java}
> // idempotent repository may be used by others, so add it as a service so its
> stopped when CamelContext stops
> if
[jira] [Assigned] (CAMEL-11647) SupervisingRouteController : add JMX support
[ https://issues.apache.org/jira/browse/CAMEL-11647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-11647: --- Assignee: (was: Luca Burgazzoli) > SupervisingRouteController : add JMX support > > > Key: CAMEL-11647 > URL: https://issues.apache.org/jira/browse/CAMEL-11647 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-spring-boot >Reporter: Luca Burgazzoli >Priority: Major > Labels: route-controller > Fix For: 3.0.0 > > > SupervisingRouteController should expose info about routes it is supervising > like: > - the back-off configuration > - the status > - when the next restart will happens (i.e. nb of seconds till attempt) > - the last error/stack trace > Camel Spring Boot should leverage this and expose the same information from > an Endpoints -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-11795) service-call : service-call expression should have a way to manipulate headers
[
https://issues.apache.org/jira/browse/CAMEL-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-11795:
Fix Version/s: (was: 2.24.0)
3.0.0
> service-call : service-call expression should have a way to manipulate headers
> --
>
> Key: CAMEL-11795
> URL: https://issues.apache.org/jira/browse/CAMEL-11795
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Luca Burgazzoli
>Assignee: Luca Burgazzoli
>Priority: Minor
> Labels: service-call
> Fix For: 3.0.0
>
>
> From apache-camel:
> {code}
> davsclaus, I'm looking at CAMEL-11711
> (Camel-example-spring-cloud-servicecall doesn't work out of the box)
> the issue is that
> there are some headers like CamelHttpPath now
> so i.e. undertow builds the effective url to incoke combining
> the http uri you give it with info from the headers
> so the final call is not more like http://localhost:9012 but it
> is http://localhost:9012/camel/serviceCall/service1
> which does not exists
> see this gist
> https://gist.github.com/lburgazzoli/1a44497db3cb29d2370ee2d125bb741c
> ah yeah you need to remove the CamelHttp* headers
> i guess maybe camel-undertow has been "fixed" since that example
> was created
> if you use something else like jetty it may have had that
> "problem" from the beginning
> i guess maybe service call eip should disregard those headers or
> something? unless you use those expression stuff etc
> where the expression evaluated the url of the service etc
> {camel}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13461) Http4 Component is not propagated correctly in OSGI environment
[
https://issues.apache.org/jira/browse/CAMEL-13461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16828970#comment-16828970
]
Kamil commented on CAMEL-13461:
---
1) I think it should work nevertheless
2) Of course I make sure that context-provder is started before context-consuner
> Http4 Component is not propagated correctly in OSGI environment
> ---
>
> Key: CAMEL-13461
> URL: https://issues.apache.org/jira/browse/CAMEL-13461
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 2.23.1
>Reporter: Kamil
>Priority: Minor
>
> I'm using Camel 2.23.1 with Karaf 4.2.5, with following features installed:
> {code:java}
> camel camel-scr camel-stream camel-http4 camel-jackson camel-kafka
> camel-quartz2
> {code}
> I have one bundle (let's call it context-provder) which consists of Activator
> only:
> {code:java}
> public class Activator implements BundleActivator {
> private ServiceRegistration registrationCamelContext;
> private CamelContext camelContext;
> @Override
> public void start(final BundleContext bundleContext) throws Exception {
> camelContext = new OsgiDefaultCamelContext(bundleContext);
> registrationCamelContext =
> bundleContext.registerService(CamelContext.class, camelContext, null);
> camelContext.start();
> }
> }
> {code}
> And the second bundle (let's call it context-consumer) which uses several
> Camel componets (kafka, quartz2, http4)
> {code:java}
> @Component(
> immediate = true,
> service = MyService.class
> )
> public class MyServiceImpl implements MyService {
> @Activate
> public NotificationServiceImpl(@Reference final CamelContext camelContext)
> throws Exception {
> super(camelContext)
> camelContext.addRoutes(this);
> }
> @Override
> public void configure() throws Exception {
> //routes using http4, quartz2, kafka etc.
> }
> }
> {code}
> While all other routes are "seen" by Camel and work without any problems,
> http4 is exception to the rule.
> Camel throws:
> {code:java}
> org.apache.karaf.features.internal.util.MultiException: Error restarting
> bundles:
> Activator start error in bundle context.consumer [150].
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:1005)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1058)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:994)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
> at java.base/java.lang.Thread.run(Thread.java:844)
> Suppressed: org.osgi.framework.BundleException: Activator start error
> in bundle context.consumer [150].
> at
> org.apache.felix.framework.Felix.activateBundle(Felix.java:2290)
> at
> org.apache.felix.framework.Felix.startBundle(Felix.java:2146)
> at
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)
> at
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)
> at
> org.apache.karaf.features.internal.service.BundleInstallSupportImpl.startBundle(BundleInstallSupportImpl.java:161)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1149)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:997)
> ... 6 more
> Caused by: java.lang.IllegalArgumentException: Cannot find endpoint
> with scheme https4
> at
> org.apache.camel.runtimecatalog.AbstractCamelCatalog.endpointProperties(AbstractCamelCatalog.java:542)
> at
> org.apache.camel.http.common.HttpSendDynamicAware.prepare(HttpSendDynamicAware.java:57)
> at
> org.apache.camel.processor.SendDynamicProcessor.process(SendDynamicProcessor.java:118)
> 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
>
[jira] [Updated] (CAMEL-12767) cluster service : create a cluster service based component
[ https://issues.apache.org/jira/browse/CAMEL-12767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12767: Fix Version/s: (was: 2.24.0) > cluster service : create a cluster service based component > -- > > Key: CAMEL-12767 > URL: https://issues.apache.org/jira/browse/CAMEL-12767 > Project: Camel > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Labels: clustering > > We should create a cluster component to interact with a camel cluster > leveraging the cluster service. i.e. wwe can create a cluster wide seda -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12398) Camel components - Include component verifier details in the component json schema file
[ https://issues.apache.org/jira/browse/CAMEL-12398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12398: Fix Version/s: (was: 2.24.0) > Camel components - Include component verifier details in the component json > schema file > --- > > Key: CAMEL-12398 > URL: https://issues.apache.org/jira/browse/CAMEL-12398 > Project: Camel > Issue Type: Improvement > Components: tooling >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.0.0 > > > Some components have component verifiers implemented, but we dont really know > which one without looking into the source etc. > We should make this information available in the json schema file, so we can > know this. Then we can have out build tools be able to add details about this > into the component docs, and as well 3rd party tools would know via the > camel-catalog which components has this our not. > Also we may need to include more details information how to execute a > verifier, eg which options to include, so the 3rd party tooling would know. > And we can also generate a report which component has this, and which has > not. Then we can better find out and implement this for more and more > components. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12764) camel-http4: basic auth no longer working when used in combination with a dynamic to
[
https://issues.apache.org/jira/browse/CAMEL-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16828971#comment-16828971
]
Claus Ibsen commented on CAMEL-12764:
-
Can you try with latest releases
> camel-http4: basic auth no longer working when used in combination with a
> dynamic to
>
>
> Key: CAMEL-12764
> URL: https://issues.apache.org/jira/browse/CAMEL-12764
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 2.22.0, 2.22.1
>Reporter: Pascal Schumacher
>Priority: Major
> Labels: regresion
> Fix For: 2.24.0
>
>
> After upgrading a Spring Boot Project from Camel 2.21.1 to Camel 2.22.0 basic
> authentication of the http4 component stopped working when it is used in
> combination with a dynamic to.
> My (slightly simplified) route:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE,
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
>
> .toD("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/${exchangeProperty.my_id}");
> {code}
> When I change the route and remove the dynamic to everything works fine again:
> {code:java}
> from(inUri)
> .setHeader(Exchange.CONTENT_TYPE,
> constant(MediaType.APPLICATION_JSON_VALUE))
> .setBody(constant("{\"action\":\"signal\"}"))
> .setHeader(Exchange.HTTP_METHOD, constant(HttpMethods.PUT))
> .setHeader(Exchange.HTTP_PATH, exchangeProperty("my_id"))
> .to("http4://{{username}}:{{password}}@{{host}}:{{port}}/executions/");
> {code}
> Maybe this regression was caused by CAMEL-12462?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12528) service call : create a service meta data based filter
[ https://issues.apache.org/jira/browse/CAMEL-12528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12528: Fix Version/s: (was: 2.24.0) > service call : create a service meta data based filter > -- > > Key: CAMEL-12528 > URL: https://issues.apache.org/jira/browse/CAMEL-12528 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Labels: cloud, service-call > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13430) Simple language - Functions with space should use camelCase style
[ https://issues.apache.org/jira/browse/CAMEL-13430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-13430. - Resolution: Fixed Fix Version/s: 3.0.0-M3 > Simple language - Functions with space should use camelCase style > - > > Key: CAMEL-13430 > URL: https://issues.apache.org/jira/browse/CAMEL-13430 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0-M3 > > > Lets avoid having functions such as > starts with > not contains > where there are space as that makes it a bit less obvious its a function > name, and can also lead to: > https://stackoverflow.com/questions/55705150/camel-simple-expression-inside-jsonpath-language > So instead if we use > startsWith > notContains -- This message was sent by Atlassian JIRA (v7.6.3#76005)
