[jira] [Commented] (CAMEL-12584) Allow sede producers to offer data to the queue with timeout
[ https://issues.apache.org/jira/browse/CAMEL-12584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516944#comment-16516944 ] Ramu kakarla commented on CAMEL-12584: --- looking > Allow sede producers to offer data to the queue with timeout > > > Key: CAMEL-12584 > URL: https://issues.apache.org/jira/browse/CAMEL-12584 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 2.21.0 >Reporter: Andrew Doumaux >Priority: Major > Fix For: 2.23.0 > > > The seda producer only allows: > * adding with possible exception if queue is full > * blocking until space is available > I'd like to suggest a third option for seda where a configured timeout can be > added to the block case. Utilizing the .offer(timeout) method of the > underlining java queue > Use Case: > I have a Apache NiFi system doing rest posts to my Apache Camel system. The > camel system attempt to put the received message onto a seda queue which is > backed by a SynchronousQueue. This causes an exception to occur if no > threads are available to do the work requested, returns a service temporarily > unavailable status to NiFi and Nifi pauses it's rest posts for a short delay. > I'd be able to save on some network traffic I/O if I was able to say try and > wait 100ms before giving up on putting the data on the queue. > > Concept of adding the "offer/timeout" was suggested in comments of CAMEL-1962 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12494) spring-boot: use ApplicationContextRunner in spring-boot test to test AutoConfigurations
[ https://issues.apache.org/jira/browse/CAMEL-12494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503316#comment-16503316 ] Ramu kakarla commented on CAMEL-12494: --- I have checked again. I have checked other projects like 'camel-spring-cloud','camel-spring-cloud-consul' ... I don't find any. May be I am missing something here. > spring-boot: use ApplicationContextRunner in spring-boot test to test > AutoConfigurations > > > Key: CAMEL-12494 > URL: https://issues.apache.org/jira/browse/CAMEL-12494 > Project: Camel > Issue Type: Task > Components: camel-spring-boot, camel-spring-boot-starters >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 2.22.0 > > > We should migrate AutoConfigurations related test to use > ApplicationContextRunner, see: > https://spring.io/blog/2018/03/07/testing-auto-configurations-with-spring-boot-2-0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12542) seda - Have a default queue size limit
[ https://issues.apache.org/jira/browse/CAMEL-12542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500150#comment-16500150 ] Ramu kakarla commented on CAMEL-12542: --- working > seda - Have a default queue size limit > -- > > Key: CAMEL-12542 > URL: https://issues.apache.org/jira/browse/CAMEL-12542 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.0.0 > > > The seda/vm queues are unbounded by default. But some users may fill up > endless messages into these queues and hit OOME. > We should possible set a default queue size of some reasonable size so that > out of the box this wont happen. > Maybe 1000 messages is a good default. People should not really store a very > high number of in-flight messages in a JVM / CamelContext. Its not good > practice. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12494) spring-boot: use ApplicationContextRunner in spring-boot test to test AutoConfigurations
[ https://issues.apache.org/jira/browse/CAMEL-12494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471629#comment-16471629 ] Ramu kakarla commented on CAMEL-12494: --- working on this > spring-boot: use ApplicationContextRunner in spring-boot test to test > AutoConfigurations > > > Key: CAMEL-12494 > URL: https://issues.apache.org/jira/browse/CAMEL-12494 > Project: Camel > Issue Type: Task > Components: camel-spring-boot, camel-spring-boot-starters >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 2.22.0 > > > We should migrate AutoConfigurations related test to use > ApplicationContextRunner, see: > https://spring.io/blog/2018/03/07/testing-auto-configurations-with-spring-boot-2-0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (CAMEL-12494) spring-boot: use ApplicationContextRunner in spring-boot test to test AutoConfigurations
[ https://issues.apache.org/jira/browse/CAMEL-12494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramu kakarla updated CAMEL-12494: - Comment: was deleted (was: looking) > spring-boot: use ApplicationContextRunner in spring-boot test to test > AutoConfigurations > > > Key: CAMEL-12494 > URL: https://issues.apache.org/jira/browse/CAMEL-12494 > Project: Camel > Issue Type: Task > Components: camel-spring-boot, camel-spring-boot-starters >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 2.22.0 > > > We should migrate AutoConfigurations related test to use > ApplicationContextRunner, see: > https://spring.io/blog/2018/03/07/testing-auto-configurations-with-spring-boot-2-0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12494) spring-boot: use ApplicationContextRunner in spring-boot test to test AutoConfigurations
[ https://issues.apache.org/jira/browse/CAMEL-12494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469889#comment-16469889 ] Ramu kakarla commented on CAMEL-12494: --- looking > spring-boot: use ApplicationContextRunner in spring-boot test to test > AutoConfigurations > > > Key: CAMEL-12494 > URL: https://issues.apache.org/jira/browse/CAMEL-12494 > Project: Camel > Issue Type: Task > Components: camel-spring-boot, camel-spring-boot-starters >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 2.22.0 > > > We should migrate AutoConfigurations related test to use > ApplicationContextRunner, see: > https://spring.io/blog/2018/03/07/testing-auto-configurations-with-spring-boot-2-0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12459) camel-spring-boot - Add route group to route actuator
[
https://issues.apache.org/jira/browse/CAMEL-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465476#comment-16465476
]
Ramu kakarla commented on CAMEL-12459:
---
Hello Dimi,
Please refer PR . New property Group needs to be added.
[xyz@xyz camel-example-spring-boot]$ curl -XGET -s
http://localhost:8080/actuator/camelroutes
[{"id":"hello","uptime":"13.248
seconds","uptimeMillis":13248,"status":"Started"}]
curl -XGET -s http://localhost:8080/actuator/camelroutes
[{"id":"hello","group":"hello-group","uptime":"11.633
seconds","uptimeMillis":11633,"status":"Started"}]
> camel-spring-boot - Add route group to route actuator
> -
>
> Key: CAMEL-12459
> URL: https://issues.apache.org/jira/browse/CAMEL-12459
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 2.22.0
>
>
> A route can have a group assigned, and if it has, then we should output the
> group in the routes actuator for the info and route details we have.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-12442) rest-dsl - Rest producer should use RestConfiguration
[ https://issues.apache.org/jira/browse/CAMEL-12442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16438930#comment-16438930 ] Ramu kakarla edited comment on CAMEL-12442 at 4/16/18 2:33 AM: looking > rest-dsl - Rest producer should use RestConfiguration > - > > Key: CAMEL-12442 > URL: https://issues.apache.org/jira/browse/CAMEL-12442 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.22.0 > > > The RestConfiguration have additional configuration for component level, > endpoint level which you may want to allow to configure for the rest-dsl > producer side. > Currently this is only supported on the consumer side. > To introduce this, requires an API change in the RestProducerFactory method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12378) Spring Boot 2 - Fix the camel-example-spring-cloud-servicecall
[ https://issues.apache.org/jira/browse/CAMEL-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408856#comment-16408856 ] Ramu kakarla commented on CAMEL-12378: --- Example builds success in my tests. am I Testing something different (mvn clean install) > Spring Boot 2 - Fix the camel-example-spring-cloud-servicecall > -- > > Key: CAMEL-12378 > URL: https://issues.apache.org/jira/browse/CAMEL-12378 > Project: Camel > Issue Type: Sub-task >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.22.0 > > > This example fails with starting the consumer. Some weird SB classpath > problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-12378) Spring Boot 2 - Fix the camel-example-spring-cloud-servicecall
[ https://issues.apache.org/jira/browse/CAMEL-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408856#comment-16408856 ] Ramu kakarla edited comment on CAMEL-12378 at 3/22/18 12:51 AM: - Example builds success in my tests. am I Testing something different (mvn clean install) ? was (Author: kramu.k7): Example builds success in my tests. am I Testing something different (mvn clean install) > Spring Boot 2 - Fix the camel-example-spring-cloud-servicecall > -- > > Key: CAMEL-12378 > URL: https://issues.apache.org/jira/browse/CAMEL-12378 > Project: Camel > Issue Type: Sub-task >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.22.0 > > > This example fails with starting the consumer. Some weird SB classpath > problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12230) Camel-Ribbon: add a Karaf feature
[
https://issues.apache.org/jira/browse/CAMEL-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355143#comment-16355143
]
Ramu kakarla commented on CAMEL-12230:
---
I have tried by adding camel-ribbon feature . seems like it is not OSGI
friendly
{code:java}
JBossFuse:karaf@root> features:list | grep camel-ribbon
[uninstalled] [2.17.0.redhat-630310 ] camel-ribbon
camel-2.17.0.redhat-630310
JBossFuse:karaf@root> features:install camel-ribbon
Error executing command: Can not resolve feature
camel-ribbon/2.17.0.redhat-630310, resource
mvn:com.netflix.ribbon/ribbon-core/2.2.4 is not proper OSGi bundle
{code}
> Camel-Ribbon: add a Karaf feature
> -
>
> Key: CAMEL-12230
> URL: https://issues.apache.org/jira/browse/CAMEL-12230
> Project: Camel
> Issue Type: Task
> Components: camel-ribbon
>Affects Versions: 2.20.2
> Environment: Karaf 4.1.4
> Camel 2.20.2
> Win 10
> Oracle Java 1.8.0_161
>Reporter: Vadim R
>Priority: Minor
>
> I'm trying to use ribbon load balancer in *Karaf* like this:
> {code:java}
> from("timer:consumerTimer?fixedRate=true=0=1")
> .routeId("consumeService")
> .setBody(simple("Hello, Producer! This is message from
> consumer on ${camelId}/${routeId}"))
> .serviceCall()
> .name("producer")
> .component("netty4:tcp")
> .ribbonLoadBalancer()
> .consulServiceDiscovery()
> .endParent()
> .convertBodyTo(String.class)
> .log("Producer response: ${body}");
> {code}
> But after start my bundle, following error appear in log (log:display):
> {code:java}
> 2018-02-06 10:53:24,289 | ERROR | nt Dispatcher: 1 | BlueprintCamelContext
> | 36 - org.apache.camel.camel-blueprint - 2.20.2 | Error occurred
> during starting Camel Context consumer-context
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> consumeService at: >>> ServiceCall[producer] <<< in route:
> Route(consumeService)[[From[timer:consumerTimer?fixedRate=tr... because of
> Could not find factory class for resource:
> META-INF/services/org/apache/camel/cloud/ribbon-service-load-balancer
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1298)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:204)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1148)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:3727)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3441)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:244)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:284)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.blueprintEvent(BlueprintCamelContext.java:177)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:201)
> [28:org.apache.aries.blueprint.core:1.8.3]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:199)
> [28:org.apache.aries.blueprint.core:1.8.3]
>
[jira] [Commented] (CAMEL-12230) Camel-Ribbon: add a Karaf feature
[
https://issues.apache.org/jira/browse/CAMEL-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355099#comment-16355099
]
Ramu kakarla commented on CAMEL-12230:
---
looking
> Camel-Ribbon: add a Karaf feature
> -
>
> Key: CAMEL-12230
> URL: https://issues.apache.org/jira/browse/CAMEL-12230
> Project: Camel
> Issue Type: Task
> Components: camel-ribbon
>Affects Versions: 2.20.2
> Environment: Karaf 4.1.4
> Camel 2.20.2
> Win 10
> Oracle Java 1.8.0_161
>Reporter: Vadim R
>Priority: Minor
>
> I'm trying to use ribbon load balancer in *Karaf* like this:
> {code:java}
> from("timer:consumerTimer?fixedRate=true=0=1")
> .routeId("consumeService")
> .setBody(simple("Hello, Producer! This is message from
> consumer on ${camelId}/${routeId}"))
> .serviceCall()
> .name("producer")
> .component("netty4:tcp")
> .ribbonLoadBalancer()
> .consulServiceDiscovery()
> .endParent()
> .convertBodyTo(String.class)
> .log("Producer response: ${body}");
> {code}
> But after start my bundle, following error appear in log (log:display):
> {code:java}
> 2018-02-06 10:53:24,289 | ERROR | nt Dispatcher: 1 | BlueprintCamelContext
> | 36 - org.apache.camel.camel-blueprint - 2.20.2 | Error occurred
> during starting Camel Context consumer-context
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> consumeService at: >>> ServiceCall[producer] <<< in route:
> Route(consumeService)[[From[timer:consumerTimer?fixedRate=tr... because of
> Could not find factory class for resource:
> META-INF/services/org/apache/camel/cloud/ribbon-service-load-balancer
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:1298)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:204)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:1148)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:3727)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:3441)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:208)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3249)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doWithDefinedClassLoader(DefaultCamelContext.java:3268)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:3245)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:3168)
> [39:org.apache.camel.camel-core:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:244)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:284)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.camel.blueprint.BlueprintCamelContext.blueprintEvent(BlueprintCamelContext.java:177)
> [36:org.apache.camel.camel-blueprint:2.20.2]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:201)
> [28:org.apache.aries.blueprint.core:1.8.3]
> at
> org.apache.aries.blueprint.container.BlueprintEventDispatcher$4.call(BlueprintEventDispatcher.java:199)
> [28:org.apache.aries.blueprint.core:1.8.3]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
>
[jira] [Commented] (CAMEL-11598) camel-spring-boot - actuator endpoints - Make it read-only by default
[ https://issues.apache.org/jira/browse/CAMEL-11598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16334143#comment-16334143 ] Ramu kakarla commented on CAMEL-11598: --- is anything pending to close this case? > camel-spring-boot - actuator endpoints - Make it read-only by default > - > > Key: CAMEL-11598 > URL: https://issues.apache.org/jira/browse/CAMEL-11598 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.21.0 > > > We should make these commands read-only by default, as you can today stop and > start routes. This can be a little bit problematic. It may be nice to have > read-only actions to get route statistics etc. > We can then add some option the user must set to allow to control the routes > Maybe it should be named read-only and be true by default? > endpoints.camelroutes.read-only = true|false > Or we can come up with a better name. And allow to specify which actions to > turn on > endpoints.camelroutes.allow=info > endpoints.camelroutes.allow=info,start,stop > endpoints.camelroutes.allow=* > I am not sure what spring-boot may come OOTB in this regard, they may have > something also, for user roles to allow invoking certain operations etc. > But it would be nice with read-only OOTB so you can see the state of all your > routes always. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12115) Camel-Consul: Upgrade to 1.0.0 consul client
[ https://issues.apache.org/jira/browse/CAMEL-12115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312998#comment-16312998 ] Ramu kakarla commented on CAMEL-12115: --- I am almost done. Fixing some compile time errors. > Camel-Consul: Upgrade to 1.0.0 consul client > > > Key: CAMEL-12115 > URL: https://issues.apache.org/jira/browse/CAMEL-12115 > Project: Camel > Issue Type: Task > Components: camel-consul >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino > Fix For: 2.21.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (CAMEL-12115) Camel-Consul: Upgrade to 1.0.0 consul client
[ https://issues.apache.org/jira/browse/CAMEL-12115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312470#comment-16312470 ] Ramu kakarla edited comment on CAMEL-12115 at 1/5/18 4:49 AM: --- Apolgies,I realized later that it is already assigned .I also haven't really started was (Author: kramu.k7): I realized later that it is already assigned .I also haven't really started > Camel-Consul: Upgrade to 1.0.0 consul client > > > Key: CAMEL-12115 > URL: https://issues.apache.org/jira/browse/CAMEL-12115 > Project: Camel > Issue Type: Task > Components: camel-consul >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino > Fix For: 2.21.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (CAMEL-12115) Camel-Consul: Upgrade to 1.0.0 consul client
[ https://issues.apache.org/jira/browse/CAMEL-12115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312470#comment-16312470 ] Ramu kakarla edited comment on CAMEL-12115 at 1/5/18 4:44 AM: --- I realized later that it is already assigned .I also haven't really started was (Author: kramu.k7): I realized later that it is already assigned . > Camel-Consul: Upgrade to 1.0.0 consul client > > > Key: CAMEL-12115 > URL: https://issues.apache.org/jira/browse/CAMEL-12115 > Project: Camel > Issue Type: Task > Components: camel-consul >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino > Fix For: 2.21.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-12115) Camel-Consul: Upgrade to 1.0.0 consul client
[ https://issues.apache.org/jira/browse/CAMEL-12115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312470#comment-16312470 ] Ramu kakarla commented on CAMEL-12115: --- I realized later that it is already assigned . > Camel-Consul: Upgrade to 1.0.0 consul client > > > Key: CAMEL-12115 > URL: https://issues.apache.org/jira/browse/CAMEL-12115 > Project: Camel > Issue Type: Task > Components: camel-consul >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino > Fix For: 2.21.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-12115) Camel-Consul: Upgrade to 1.0.0 consul client
[ https://issues.apache.org/jira/browse/CAMEL-12115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311234#comment-16311234 ] Ramu kakarla commented on CAMEL-12115: --- I am looking into it > Camel-Consul: Upgrade to 1.0.0 consul client > > > Key: CAMEL-12115 > URL: https://issues.apache.org/jira/browse/CAMEL-12115 > Project: Camel > Issue Type: Task > Components: camel-consul >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino > Fix For: 2.21.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-12022) direct component - Let the producer able to block and wait for consumers to be started
[ https://issues.apache.org/jira/browse/CAMEL-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292227#comment-16292227 ] Ramu kakarla commented on CAMEL-12022: --- Hello Claus, I don't have ACL rights to edit the WIKI page. Could you do the favours > direct component - Let the producer able to block and wait for consumers to > be started > -- > > Key: CAMEL-12022 > URL: https://issues.apache.org/jira/browse/CAMEL-12022 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen > Fix For: 2.21.0 > > > Similar to what direct-vm component can do. We should let the direct producer > detect that if there is no consumer yet, then it can wait until its ready > (with timeout) during starting routes. > This can avoid the slim chance during route startup that you get a > DirectConsumerNotAvailableException -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-12022) direct component - Let the producer able to block and wait for consumers to be started
[ https://issues.apache.org/jira/browse/CAMEL-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16291909#comment-16291909 ] Ramu kakarla commented on CAMEL-12022: --- Hi Claus, is this link [Camel 2.21.0 Release|https://cwiki.apache.org/confluence/display/CAMEL/Camel+2.21.0+Release] needs to be updated ? > direct component - Let the producer able to block and wait for consumers to > be started > -- > > Key: CAMEL-12022 > URL: https://issues.apache.org/jira/browse/CAMEL-12022 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen > Fix For: 2.21.0 > > > Similar to what direct-vm component can do. We should let the direct producer > detect that if there is no consumer yet, then it can wait until its ready > (with timeout) during starting routes. > This can avoid the slim chance during route startup that you get a > DirectConsumerNotAvailableException -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-12022) direct component - Let the producer able to block and wait for consumers to be started
[ https://issues.apache.org/jira/browse/CAMEL-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272386#comment-16272386 ] Ramu kakarla commented on CAMEL-12022: --- Yes claus, I am almost done. Some of the test classes are getting failed .I am working on the same > direct component - Let the producer able to block and wait for consumers to > be started > -- > > Key: CAMEL-12022 > URL: https://issues.apache.org/jira/browse/CAMEL-12022 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen > Fix For: 2.21.0 > > > Similar to what direct-vm component can do. We should let the direct producer > detect that if there is no consumer yet, then it can wait until its ready > (with timeout) during starting routes. > This can avoid the slim chance during route startup that you get a > DirectConsumerNotAvailableException -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-12022) direct component - Let the producer able to block and wait for consumers to be started
[ https://issues.apache.org/jira/browse/CAMEL-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264053#comment-16264053 ] Ramu kakarla commented on CAMEL-12022: --- Thanks Claus,I will raise PR > direct component - Let the producer able to block and wait for consumers to > be started > -- > > Key: CAMEL-12022 > URL: https://issues.apache.org/jira/browse/CAMEL-12022 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen > Fix For: 2.21.0 > > > Similar to what direct-vm component can do. We should let the direct producer > detect that if there is no consumer yet, then it can wait until its ready > (with timeout) during starting routes. > This can avoid the slim chance during route startup that you get a > DirectConsumerNotAvailableException -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-12022) direct component - Let the producer able to block and wait for consumers to be started
[
https://issues.apache.org/jira/browse/CAMEL-12022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262740#comment-16262740
]
Ramu kakarla commented on CAMEL-12022:
---
Hello Claus,
I do see 2 classes
1.DirectProducer.java (without timeout)
2.DirectBlockingProducer (with timeout)
If no consumer is available producer should wait till consumer avaialble
(with some default time)
If we implement this timeout in Directproducer. then there will be no diff b/w
DirectProducer.java and DirectBlockingProducer
instead we can use DirectBlockingProducer .
{code:java}
public Producer createProducer() throws Exception {
if (block) {
return new DirectBlockingProducer(this);
} else {
return new DirectProducer(this);
}
}
{code}
> direct component - Let the producer able to block and wait for consumers to
> be started
> --
>
> Key: CAMEL-12022
> URL: https://issues.apache.org/jira/browse/CAMEL-12022
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Claus Ibsen
> Fix For: 2.21.0
>
>
> Similar to what direct-vm component can do. We should let the direct producer
> detect that if there is no consumer yet, then it can wait until its ready
> (with timeout) during starting routes.
> This can avoid the slim chance during route startup that you get a
> DirectConsumerNotAvailableException
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-12018) camel-shiro - Upgrade to 1.4.0
[ https://issues.apache.org/jira/browse/CAMEL-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262502#comment-16262502 ] Ramu kakarla commented on CAMEL-12018: --- worrking on it > camel-shiro - Upgrade to 1.4.0 > -- > > Key: CAMEL-12018 > URL: https://issues.apache.org/jira/browse/CAMEL-12018 > Project: Camel > Issue Type: Improvement > Components: camel-shiro >Reporter: Claus Ibsen > Fix For: 2.21.0 > > > We should upgrade to the newer 1.4.0 release -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11914) camel-fn component to call funktions on the fnplatform
[ https://issues.apache.org/jira/browse/CAMEL-11914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16220174#comment-16220174 ] Ramu kakarla commented on CAMEL-11914: --- I will look into it > camel-fn component to call funktions on the fnplatform > -- > > Key: CAMEL-11914 > URL: https://issues.apache.org/jira/browse/CAMEL-11914 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen > Fix For: Future > > > One of those popular servless function platforms - fnproject has a java > client api, which can be used to call funktions > https://github.com/fnproject/fdk-java > We should create a little Camel component for this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (CAMEL-11822) Upgade jaxb-core
[ https://issues.apache.org/jira/browse/CAMEL-11822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203798#comment-16203798 ] Ramu kakarla edited comment on CAMEL-11822 at 10/13/17 5:13 PM: - PR raised [https://github.com/apache/camel/pull/2039| https://github.com/apache/camel/pull/2039] was (Author: kramu.k7): PR raised [PR| https://github.com/apache/camel/pull/2039] > Upgade jaxb-core > > > Key: CAMEL-11822 > URL: https://issues.apache.org/jira/browse/CAMEL-11822 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Claus Ibsen > Fix For: 2.21.0 > > > We are using 2.2.11 but there is a newer 2.3.0 release out. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (CAMEL-11822) Upgade jaxb-core
[ https://issues.apache.org/jira/browse/CAMEL-11822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203798#comment-16203798 ] Ramu kakarla edited comment on CAMEL-11822 at 10/13/17 5:12 PM: - PR raised [PR| https://github.com/apache/camel/pull/2039] was (Author: kramu.k7): PR raised "https://github.com/apache/camel/pull/2039; > Upgade jaxb-core > > > Key: CAMEL-11822 > URL: https://issues.apache.org/jira/browse/CAMEL-11822 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Claus Ibsen > Fix For: 2.21.0 > > > We are using 2.2.11 but there is a newer 2.3.0 release out. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11822) Upgade jaxb-core
[ https://issues.apache.org/jira/browse/CAMEL-11822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203798#comment-16203798 ] Ramu kakarla commented on CAMEL-11822: --- PR raised "https://github.com/apache/camel/pull/2039; > Upgade jaxb-core > > > Key: CAMEL-11822 > URL: https://issues.apache.org/jira/browse/CAMEL-11822 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Claus Ibsen > Fix For: 2.21.0 > > > We are using 2.2.11 but there is a newer 2.3.0 release out. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11822) Upgade jaxb-core
[ https://issues.apache.org/jira/browse/CAMEL-11822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16194380#comment-16194380 ] Ramu kakarla commented on CAMEL-11822: --- I have tested in java 8 By upgrading jaxb-core and jaxb-impl versions . Everything seems fine. I am in the process of testing in JDK9. > Upgade jaxb-core > > > Key: CAMEL-11822 > URL: https://issues.apache.org/jira/browse/CAMEL-11822 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Claus Ibsen > Fix For: 2.21.0 > > > We are using 2.2.11 but there is a newer 2.3.0 release out. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11822) Upgade jaxb-core
[ https://issues.apache.org/jira/browse/CAMEL-11822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16194340#comment-16194340 ] Ramu kakarla commented on CAMEL-11822: --- seems like it's compatible with Java 9 but does not require it ? > Upgade jaxb-core > > > Key: CAMEL-11822 > URL: https://issues.apache.org/jira/browse/CAMEL-11822 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Claus Ibsen > Fix For: 2.21.0 > > > We are using 2.2.11 but there is a newer 2.3.0 release out. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11822) Upgade jaxb-core
[ https://issues.apache.org/jira/browse/CAMEL-11822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191458#comment-16191458 ] Ramu kakarla commented on CAMEL-11822: --- I am looking into it > Upgade jaxb-core > > > Key: CAMEL-11822 > URL: https://issues.apache.org/jira/browse/CAMEL-11822 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Claus Ibsen > Fix For: 2.21.0 > > > We are using 2.2.11 but there is a newer 2.3.0 release out. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11805) Upgrade to Apache Ignite 2.x
[ https://issues.apache.org/jira/browse/CAMEL-11805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191238#comment-16191238 ] Ramu kakarla commented on CAMEL-11805: --- Thanks Claus for the clarifications. I will raise PR soon > Upgrade to Apache Ignite 2.x > > > Key: CAMEL-11805 > URL: https://issues.apache.org/jira/browse/CAMEL-11805 > Project: Camel > Issue Type: Task > Components: camel-ignite >Reporter: Luca Burgazzoli > Fix For: 2.21.0 > > > Last version is 2.2.0, we are on 1.9.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11805) Upgrade to Apache Ignite 2.x
[ https://issues.apache.org/jira/browse/CAMEL-11805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191075#comment-16191075 ] Ramu kakarla commented on CAMEL-11805: --- Hello All, I have gone through the "Apache Ignite 2.0 Migration Guide" . It seems like backward compatibility is not possible in 2.0 [1] "Apache Ignite 2.0 incorporate tremendous changes that make it different from Apache Ignite 1.x releases. Apache Ignite 2.0 is incompatible with previous versions and, most likely, application code has to be altered if someone plans to migrate to 2.0." May be new component is needed here (camel-ignite2) . Any thoughts on this [1]https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide > Upgrade to Apache Ignite 2.x > > > Key: CAMEL-11805 > URL: https://issues.apache.org/jira/browse/CAMEL-11805 > Project: Camel > Issue Type: Task > Components: camel-ignite >Reporter: Luca Burgazzoli > Fix For: 2.21.0 > > > Last version is 2.2.0, we are on 1.9.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11805) Upgrade to Apache Ignite 2.x
[ https://issues.apache.org/jira/browse/CAMEL-11805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190032#comment-16190032 ] Ramu kakarla commented on CAMEL-11805: --- I am looking into it > Upgrade to Apache Ignite 2.x > > > Key: CAMEL-11805 > URL: https://issues.apache.org/jira/browse/CAMEL-11805 > Project: Camel > Issue Type: Task > Components: camel-ignite >Reporter: Luca Burgazzoli > Fix For: 2.21.0 > > > Last version is 2.2.0, we are on 1.9.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11819) camel-velocity - Upgrade to 2.x
[ https://issues.apache.org/jira/browse/CAMEL-11819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180922#comment-16180922 ] Ramu kakarla commented on CAMEL-11819: --- I am working on it > camel-velocity - Upgrade to 2.x > --- > > Key: CAMEL-11819 > URL: https://issues.apache.org/jira/browse/CAMEL-11819 > Project: Camel > Issue Type: Improvement > Components: camel-velocity >Reporter: Claus Ibsen > Fix For: 2.21.0 > > > There is a 2.0 release - the old 1.7 release is very old. > Contributions is welcome > http://camel.apache.org/contributing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (CAMEL-11622) Rest-dsl doesn't support post() endpoints with different request body types
[
https://issues.apache.org/jira/browse/CAMEL-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110291#comment-16110291
]
Ramu kakarla edited comment on CAMEL-11622 at 8/2/17 5:37 AM:
---
looking into it,could you please add a simple test case
was (Author: kramu.k7):
looking into it
> Rest-dsl doesn't support post() endpoints with different request body types
> ---
>
> Key: CAMEL-11622
> URL: https://issues.apache.org/jira/browse/CAMEL-11622
> Project: Camel
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.18.1
> Environment: Spring-Boot with Tomcat8 container
>Reporter: Balazs Szeti
>
> The rest-dsl doesn't support two post() endpoints with different request body
> types.
> {code:java}
> restConfiguration()
> .component("servlet")
> .contextPath("/api")
> .bindingMode(RestBindingMode.json)
> ;
> rest("/user")
> .post("/").type(UserPojo.class)
> .route()
> .log("Name: ${body.name}")
> .endRest()
> ;
> rest("/country")
> .post("/").type(CountryPojo.class)
> .route()
> .log("Name: ${body.country}")
> .endRest()
> ;
> {code}
> Both endpoints (/api/user, /api/country) tries to unmarshal the post body to
> CountryPojo and a JsonProcessingException is thrown when a UserPojo json is
> sent to /user.
> The problem is that they share one JascksonDataFormat instance registered
> with name "json-jackson" and the RestDefinition.type() sets the
> JascksonDataFormat.unmarshalType so at the end both post() endpoints will try
> to unmarshal to the same class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11622) Rest-dsl doesn't support post() endpoints with different request body types
[
https://issues.apache.org/jira/browse/CAMEL-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16110291#comment-16110291
]
Ramu kakarla commented on CAMEL-11622:
---
looking into it
> Rest-dsl doesn't support post() endpoints with different request body types
> ---
>
> Key: CAMEL-11622
> URL: https://issues.apache.org/jira/browse/CAMEL-11622
> Project: Camel
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.18.1
> Environment: Spring-Boot with Tomcat8 container
>Reporter: Balazs Szeti
>
> The rest-dsl doesn't support two post() endpoints with different request body
> types.
> {code:java}
> restConfiguration()
> .component("servlet")
> .contextPath("/api")
> .bindingMode(RestBindingMode.json)
> ;
> rest("/user")
> .post("/").type(UserPojo.class)
> .route()
> .log("Name: ${body.name}")
> .endRest()
> ;
> rest("/country")
> .post("/").type(CountryPojo.class)
> .route()
> .log("Name: ${body.country}")
> .endRest()
> ;
> {code}
> Both endpoints (/api/user, /api/country) tries to unmarshal the post body to
> CountryPojo and a JsonProcessingException is thrown when a UserPojo json is
> sent to /user.
> The problem is that they share one JascksonDataFormat instance registered
> with name "json-jackson" and the RestDefinition.type() sets the
> JascksonDataFormat.unmarshalType so at the end both post() endpoints will try
> to unmarshal to the same class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11596) camel-spring-boot - actuator endpoint routes - Get single route only
[
https://issues.apache.org/jira/browse/CAMEL-11596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108432#comment-16108432
]
Ramu kakarla commented on CAMEL-11596:
---
Could somebody verify
> camel-spring-boot - actuator endpoint routes - Get single route only
>
>
> Key: CAMEL-11596
> URL: https://issues.apache.org/jira/browse/CAMEL-11596
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>
> See the readme of this example
> https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot-routecontroller
> To get info about a route you need to
> {code}
> curl -XGET -s http://localhost:8080/camel/routes/id/info
> {code}
> That returns many information about the route, but if you just want to big
> summary like
> {code}
> curl -XGET -s http://localhost:8080/camel/routes
> {code}
> But for a specific route like bar
> {code}
> curl -XGET -s http://localhost:8080/camel/routes/bar
> {code}
> Then that is not possible. It may be nice to then just return
> {code}
> {"id":"bar","uptime":"3.405 seconds","uptimeMillis":3405,"status":"Started"}
> {code}
> eg only that route.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11617) spring-boot - service-call tests uses hardcoded port numbers
[ https://issues.apache.org/jira/browse/CAMEL-11617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16107259#comment-16107259 ] Ramu kakarla commented on CAMEL-11617: --- Ok I am working on this > spring-boot - service-call tests uses hardcoded port numbers > > > Key: CAMEL-11617 > URL: https://issues.apache.org/jira/browse/CAMEL-11617 > Project: Camel > Issue Type: Test > Components: tests >Reporter: Claus Ibsen >Priority: Minor > Fix For: Future > > > They tend to fail on CI servers with Port number in use errors > Its in camel-spring-boot, camel-spring-cloud, and camel-spring-cloud-netflix > etc. > Failed > org.apache.camel.spring.boot.cloud.CamelCloudServiceCallTest.testServiceCall > Failing for the past 3 builds (Since Unstable#1564 ) > Took 6 ms. > Error Message > Failed to load ApplicationContext > Stacktrace > java.lang.IllegalStateException: Failed to load ApplicationContext > Caused by: org.apache.camel.RuntimeCamelException: java.net.BindException: > Address already in use > Caused by: java.net.BindException: Address already in use -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (CAMEL-11596) camel-spring-boot - actuator endpoint routes - Get single route only
[
https://issues.apache.org/jira/browse/CAMEL-11596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101718#comment-16101718
]
Ramu kakarla edited comment on CAMEL-11596 at 7/26/17 2:24 PM:
Hello,
I have added camel/routes/
{id}
/detail as per Luca Burgazzoli suggestion
1)$ curl -XGET -s http://localhost:8080/camel/routes/
[{"id":"bar","uptime":"13
minutes","uptimeMillis":801360,"status":"Started"},{"id":"foo","uptime":"13
minutes","uptimeMillis":801359,"status":"Started"},{"id":"undertow","uptime":"13
minutes","uptimeMillis":801363,"status":"Started"}]
2)$ curl -XGET -s http://localhost:8080/camel/routes/foo/info
{"id":"foo","uptime":"13
minutes","uptimeMillis":807866,"status":"Started","details":{"deltaProcessingTime":1,"exchangesInflight":0,"exchangesTotal":162,"externalRedeliveries":0,"failuresHandled":0,"firstExchangeCompletedExchangeId":"ID--1501077986781-0-1","firstExchangeCompletedTimestamp":1501077989469,"lastExchangeCompletedExchangeId":"ID-kkakarla-pnq-csb-1501077986781-0-324","lastExchangeCompletedTimestamp":1501078794481,"lastProcessingTime":1,"maxProcessingTime":3,"meanProcessingTime":0,"minProcessingTime":0,"redeliveries":0,"totalProcessingTime":42,"hasRouteController":true}}
3)$ curl -XGET -s http://localhost:8080/camel/routes/foo/detail
{"id":"foo","uptime":"13
minutes","uptimeMillis":815282,"status":"Started","details":{"deltaProcessingTime":-1,"exchangesInflight":0,"exchangesTotal":163,"externalRedeliveries":0,"failuresHandled":0,"firstExchangeCompletedExchangeId":"ID-kkakarla-pnq-csb-1501077986781-0-1","firstExchangeCompletedTimestamp":1501077989469,"lastExchangeCompletedExchangeId":"ID-kkakarla-pnq-csb-1501077986781-0-326","lastExchangeCompletedTimestamp":1501078799480,"lastProcessingTime":0,"maxProcessingTime":3,"meanProcessingTime":0,"minProcessingTime":0,"redeliveries":0,"totalProcessingTime":42,"hasRouteController":true}}
4)$ curl -XGET -s http://localhost:8080/camel/routes/foo
{"id":"foo","uptime":"13 minutes","uptimeMillis":819307,"status":"Started"}
was (Author: kramu.k7):
Hello,
I have added camel/routes/
{id}
/detail as per Luca Burgazzoli suggestion
1)[kkakarla@kkakarla /]$ curl -XGET -s http://localhost:8080/camel/routes/
[{"id":"bar","uptime":"13
minutes","uptimeMillis":801360,"status":"Started"},{"id":"foo","uptime":"13
minutes","uptimeMillis":801359,"status":"Started"},{"id":"undertow","uptime":"13
minutes","uptimeMillis":801363,"status":"Started"}]
2)[kkakarla@kkakarla /]$ curl -XGET -s
http://localhost:8080/camel/routes/foo/info
{"id":"foo","uptime":"13
minutes","uptimeMillis":807866,"status":"Started","details":{"deltaProcessingTime":1,"exchangesInflight":0,"exchangesTotal":162,"externalRedeliveries":0,"failuresHandled":0,"firstExchangeCompletedExchangeId":"ID--1501077986781-0-1","firstExchangeCompletedTimestamp":1501077989469,"lastExchangeCompletedExchangeId":"ID-kkakarla-pnq-csb-1501077986781-0-324","lastExchangeCompletedTimestamp":1501078794481,"lastProcessingTime":1,"maxProcessingTime":3,"meanProcessingTime":0,"minProcessingTime":0,"redeliveries":0,"totalProcessingTime":42,"hasRouteController":true}}
3)[kkakarla@kkakarla /]$ curl -XGET -s
http://localhost:8080/camel/routes/foo/detail
{"id":"foo","uptime":"13
minutes","uptimeMillis":815282,"status":"Started","details":{"deltaProcessingTime":-1,"exchangesInflight":0,"exchangesTotal":163,"externalRedeliveries":0,"failuresHandled":0,"firstExchangeCompletedExchangeId":"ID-kkakarla-pnq-csb-1501077986781-0-1","firstExchangeCompletedTimestamp":1501077989469,"lastExchangeCompletedExchangeId":"ID-kkakarla-pnq-csb-1501077986781-0-326","lastExchangeCompletedTimestamp":1501078799480,"lastProcessingTime":0,"maxProcessingTime":3,"meanProcessingTime":0,"minProcessingTime":0,"redeliveries":0,"totalProcessingTime":42,"hasRouteController":true}}
4)[kkakarla@kkakarla /]$ curl -XGET -s http://localhost:8080/camel/routes/foo
{"id":"foo","uptime":"13
minutes","uptimeMillis":819307,"status":"Started"}[kkakarla@kkakarla /]$
> camel-spring-boot - actuator endpoint routes - Get single route only
>
>
> Key: CAMEL-11596
> URL: https://issues.apache.org/jira/browse/CAMEL-11596
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>
> See the readme of this example
> https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot-routecontroller
> To get info about a route you need to
> {code}
> curl -XGET -s http://localhost:8080/camel/routes/id/info
> {code}
> That returns many information about the route, but if you just want to big
> summary like
> {code}
> curl -XGET -s http://localhost:8080/camel/routes
> {code}
> But for a specific route like bar
[jira] [Commented] (CAMEL-11596) camel-spring-boot - actuator endpoint routes - Get single route only
[
https://issues.apache.org/jira/browse/CAMEL-11596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101718#comment-16101718
]
Ramu kakarla commented on CAMEL-11596:
---
Hello,
I have added camel/routes/
{id}
/detail as per Luca Burgazzoli suggestion
1)[kkakarla@kkakarla /]$ curl -XGET -s http://localhost:8080/camel/routes/
[{"id":"bar","uptime":"13
minutes","uptimeMillis":801360,"status":"Started"},{"id":"foo","uptime":"13
minutes","uptimeMillis":801359,"status":"Started"},{"id":"undertow","uptime":"13
minutes","uptimeMillis":801363,"status":"Started"}]
2)[kkakarla@kkakarla /]$ curl -XGET -s
http://localhost:8080/camel/routes/foo/info
{"id":"foo","uptime":"13
minutes","uptimeMillis":807866,"status":"Started","details":{"deltaProcessingTime":1,"exchangesInflight":0,"exchangesTotal":162,"externalRedeliveries":0,"failuresHandled":0,"firstExchangeCompletedExchangeId":"ID--1501077986781-0-1","firstExchangeCompletedTimestamp":1501077989469,"lastExchangeCompletedExchangeId":"ID-kkakarla-pnq-csb-1501077986781-0-324","lastExchangeCompletedTimestamp":1501078794481,"lastProcessingTime":1,"maxProcessingTime":3,"meanProcessingTime":0,"minProcessingTime":0,"redeliveries":0,"totalProcessingTime":42,"hasRouteController":true}}
3)[kkakarla@kkakarla /]$ curl -XGET -s
http://localhost:8080/camel/routes/foo/detail
{"id":"foo","uptime":"13
minutes","uptimeMillis":815282,"status":"Started","details":{"deltaProcessingTime":-1,"exchangesInflight":0,"exchangesTotal":163,"externalRedeliveries":0,"failuresHandled":0,"firstExchangeCompletedExchangeId":"ID-kkakarla-pnq-csb-1501077986781-0-1","firstExchangeCompletedTimestamp":1501077989469,"lastExchangeCompletedExchangeId":"ID-kkakarla-pnq-csb-1501077986781-0-326","lastExchangeCompletedTimestamp":1501078799480,"lastProcessingTime":0,"maxProcessingTime":3,"meanProcessingTime":0,"minProcessingTime":0,"redeliveries":0,"totalProcessingTime":42,"hasRouteController":true}}
4)[kkakarla@kkakarla /]$ curl -XGET -s http://localhost:8080/camel/routes/foo
{"id":"foo","uptime":"13
minutes","uptimeMillis":819307,"status":"Started"}[kkakarla@kkakarla /]$
> camel-spring-boot - actuator endpoint routes - Get single route only
>
>
> Key: CAMEL-11596
> URL: https://issues.apache.org/jira/browse/CAMEL-11596
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>
> See the readme of this example
> https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot-routecontroller
> To get info about a route you need to
> {code}
> curl -XGET -s http://localhost:8080/camel/routes/id/info
> {code}
> That returns many information about the route, but if you just want to big
> summary like
> {code}
> curl -XGET -s http://localhost:8080/camel/routes
> {code}
> But for a specific route like bar
> {code}
> curl -XGET -s http://localhost:8080/camel/routes/bar
> {code}
> Then that is not possible. It may be nice to then just return
> {code}
> {"id":"bar","uptime":"3.405 seconds","uptimeMillis":3405,"status":"Started"}
> {code}
> eg only that route.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (CAMEL-11596) camel-spring-boot - actuator endpoint routes - Get single route only
[
https://issues.apache.org/jira/browse/CAMEL-11596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101654#comment-16101654
]
Ramu kakarla edited comment on CAMEL-11596 at 7/26/17 1:15 PM:
Hello Luca Burgazzoli ,
Shall I change New Endpoint from http://localhost:8080/camel/routes/{id}
to
http://localhost:8080/camel/routes/{id}/detail
was (Author: kramu.k7):
Hello Luca Burgazzoli ,
Shall I change New Endpoint from http://localhost:8080/camel/routes/{id}
to
http://localhost:8080/camel/routes/{id}/detail
> camel-spring-boot - actuator endpoint routes - Get single route only
>
>
> Key: CAMEL-11596
> URL: https://issues.apache.org/jira/browse/CAMEL-11596
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>
> See the readme of this example
> https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot-routecontroller
> To get info about a route you need to
> {code}
> curl -XGET -s http://localhost:8080/camel/routes/id/info
> {code}
> That returns many information about the route, but if you just want to big
> summary like
> {code}
> curl -XGET -s http://localhost:8080/camel/routes
> {code}
> But for a specific route like bar
> {code}
> curl -XGET -s http://localhost:8080/camel/routes/bar
> {code}
> Then that is not possible. It may be nice to then just return
> {code}
> {"id":"bar","uptime":"3.405 seconds","uptimeMillis":3405,"status":"Started"}
> {code}
> eg only that route.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (CAMEL-11596) camel-spring-boot - actuator endpoint routes - Get single route only
[
https://issues.apache.org/jira/browse/CAMEL-11596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101654#comment-16101654
]
Ramu kakarla edited comment on CAMEL-11596 at 7/26/17 1:15 PM:
Hello Luca Burgazzoli ,
Shall I change New Endpoint from http://localhost:8080/camel/routes/{id}
to
http://localhost:8080/camel/routes/{id}/detail
was (Author: kramu.k7):
Hello Luca,
Shall I change New Endpoint from http://localhost:8080/camel/routes/{id}
to
http://localhost:8080/camel/routes/{id}/detail
> camel-spring-boot - actuator endpoint routes - Get single route only
>
>
> Key: CAMEL-11596
> URL: https://issues.apache.org/jira/browse/CAMEL-11596
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>
> See the readme of this example
> https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot-routecontroller
> To get info about a route you need to
> {code}
> curl -XGET -s http://localhost:8080/camel/routes/id/info
> {code}
> That returns many information about the route, but if you just want to big
> summary like
> {code}
> curl -XGET -s http://localhost:8080/camel/routes
> {code}
> But for a specific route like bar
> {code}
> curl -XGET -s http://localhost:8080/camel/routes/bar
> {code}
> Then that is not possible. It may be nice to then just return
> {code}
> {"id":"bar","uptime":"3.405 seconds","uptimeMillis":3405,"status":"Started"}
> {code}
> eg only that route.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11596) camel-spring-boot - actuator endpoint routes - Get single route only
[
https://issues.apache.org/jira/browse/CAMEL-11596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101654#comment-16101654
]
Ramu kakarla commented on CAMEL-11596:
---
Hello Luca,
Shall I change New Endpoint from http://localhost:8080/camel/routes/{id}
to
http://localhost:8080/camel/routes/{id}/detail
> camel-spring-boot - actuator endpoint routes - Get single route only
>
>
> Key: CAMEL-11596
> URL: https://issues.apache.org/jira/browse/CAMEL-11596
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>
> See the readme of this example
> https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot-routecontroller
> To get info about a route you need to
> {code}
> curl -XGET -s http://localhost:8080/camel/routes/id/info
> {code}
> That returns many information about the route, but if you just want to big
> summary like
> {code}
> curl -XGET -s http://localhost:8080/camel/routes
> {code}
> But for a specific route like bar
> {code}
> curl -XGET -s http://localhost:8080/camel/routes/bar
> {code}
> Then that is not possible. It may be nice to then just return
> {code}
> {"id":"bar","uptime":"3.405 seconds","uptimeMillis":3405,"status":"Started"}
> {code}
> eg only that route.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11596) camel-spring-boot - actuator endpoint routes - Get single route only
[
https://issues.apache.org/jira/browse/CAMEL-11596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101639#comment-16101639
]
Ramu kakarla commented on CAMEL-11596:
---
[kkakarla@kkakarla endpoint]$ curl -XGET -s
http://localhost:8080/camel/routes/foo
{"id":"foo","uptime":"1
minute","uptimeMillis":62708,"status":"Started","details":{"deltaProcessingTime":-1,"exchangesInflight":0,"exchangesTotal":13,"externalRedeliveries":0,"failuresHandled":0,"firstExchangeCompletedExchangeId":"ID-kkakarla-pnq-csb-1501074001787-0-1","firstExchangeCompletedTimestamp":1501074004459,"lastExchangeCompletedExchangeId":"ID-kkakarla-pnq-csb-1501074001787-0-26","lastExchangeCompletedTimestamp":1501074064450,"lastProcessingTime":0,"maxProcessingTime":5,"meanProcessingTime":0,"minProcessingTime":0,"redeliveries":0,"totalProcessingTime":8,"hasRouteController":true}}[kkakarla@kkakarla
endpoint]$
> camel-spring-boot - actuator endpoint routes - Get single route only
>
>
> Key: CAMEL-11596
> URL: https://issues.apache.org/jira/browse/CAMEL-11596
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.0
>
>
> See the readme of this example
> https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot-routecontroller
> To get info about a route you need to
> {code}
> curl -XGET -s http://localhost:8080/camel/routes/id/info
> {code}
> That returns many information about the route, but if you just want to big
> summary like
> {code}
> curl -XGET -s http://localhost:8080/camel/routes
> {code}
> But for a specific route like bar
> {code}
> curl -XGET -s http://localhost:8080/camel/routes/bar
> {code}
> Then that is not possible. It may be nice to then just return
> {code}
> {"id":"bar","uptime":"3.405 seconds","uptimeMillis":3405,"status":"Started"}
> {code}
> eg only that route.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11059) camel-spring-dm - Should be removed
[ https://issues.apache.org/jira/browse/CAMEL-11059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007696#comment-16007696 ] Ramu kakarla commented on CAMEL-11059: --- I don't find examples/camel-example-box-osgi camel-spring-dm-starter ( The following components do not have a starter because of compatibility issues: camel-spring-dm) > camel-spring-dm - Should be removed > --- > > Key: CAMEL-11059 > URL: https://issues.apache.org/jira/browse/CAMEL-11059 > Project: Camel > Issue Type: Task > Components: karaf, osgi >Reporter: Claus Ibsen > Fix For: 2.20.0 > > > Does not really work in OSGi > http://camel.465427.n5.nabble.com/camel-spring-dm-feature-incompatible-to-most-other-features-of-camel-2-18-3-tp5796032.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Issue Comment Deleted] (CAMEL-11216) REST-DSL - Producer fails with NPE or other exceptions if you have not set a hostname
[
https://issues.apache.org/jira/browse/CAMEL-11216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramu kakarla updated CAMEL-11216:
-
Comment: was deleted
(was: Hi Claus,
I have reproduced the issue. By removing Host from restConfiguration
restConfiguration().port(8080); gives Host value Null . This can be checked in
populateRests method of RouteBuilder class
##
if (getRestConfigurations() != null) {
for (Map.Entry entry :
getRestConfigurations().entrySet()) {
RestConfiguration config =
entry.getValue().asRestConfiguration(getContext());
if ("".equals(entry.getKey())) {
if(entry.getValue().getHost()==null){
throw new IllegalArgumentException("Host is null in
the provided endpoint");
}
###
Please verify this,so that I can raise pull req
Regards
Ramu
)
> REST-DSL - Producer fails with NPE or other exceptions if you have not set a
> hostname
> -
>
> Key: CAMEL-11216
> URL: https://issues.apache.org/jira/browse/CAMEL-11216
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Affects Versions: 2.19.0
>Reporter: Claus Ibsen
>
> If you forget to configure a host name then the rest producer fails with
> different errors if you use http4, netty4-http, undertow etc.
> We should likely add some validation logic in the rest endpoint / rest
> producer so it can detect this missing configuration and report this in the
> same way.
> You can reproduce from this example by removing host at
> https://github.com/apache/camel/blob/master/examples/camel-example-rest-producer/src/main/java/sample/camel/RestRoute.java#L33
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (CAMEL-11216) REST-DSL - Producer fails with NPE or other exceptions if you have not set a hostname
[
https://issues.apache.org/jira/browse/CAMEL-11216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996926#comment-15996926
]
Ramu kakarla edited comment on CAMEL-11216 at 5/5/17 9:30 AM:
---
Hi Claus,
I have reproduced the issue. By removing Host from restConfiguration
restConfiguration().port(8080); gives Host value Null . This can be checked in
populateRests method of RouteBuilder class
##
if (getRestConfigurations() != null) {
for (Map.Entry entry :
getRestConfigurations().entrySet()) {
RestConfiguration config =
entry.getValue().asRestConfiguration(getContext());
if ("".equals(entry.getKey())) {
if(entry.getValue().getHost()==null){
throw new IllegalArgumentException("Host is null in
the provided endpoint");
}
###
Please verify this,so that I can raise pull req
Regards
Ramu
was (Author: kramu.k7):
Hi Claus,
I have reproduced the issue. By removing Host from restConfiguration
restConfiguration().port(8080); gives Host value Null . This can be checked in
populateRests method of RouteBuilder class
##
if (getRestConfigurations() != null) {
for (Map.Entry entry :
getRestConfigurations().entrySet()) {
RestConfiguration config =
entry.getValue().asRestConfiguration(getContext());
if ("".equals(entry.getKey())) {
if(entry.getValue().getHost()==null){
throw new IllegalArgumentException("Host can't be
null");
}
###
Please verify this,so that I can raise pull req
Regards
Ramu
> REST-DSL - Producer fails with NPE or other exceptions if you have not set a
> hostname
> -
>
> Key: CAMEL-11216
> URL: https://issues.apache.org/jira/browse/CAMEL-11216
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Affects Versions: 2.19.0
>Reporter: Claus Ibsen
>
> If you forget to configure a host name then the rest producer fails with
> different errors if you use http4, netty4-http, undertow etc.
> We should likely add some validation logic in the rest endpoint / rest
> producer so it can detect this missing configuration and report this in the
> same way.
> You can reproduce from this example by removing host at
> https://github.com/apache/camel/blob/master/examples/camel-example-rest-producer/src/main/java/sample/camel/RestRoute.java#L33
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (CAMEL-11216) REST-DSL - Producer fails with NPE or other exceptions if you have not set a hostname
[
https://issues.apache.org/jira/browse/CAMEL-11216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996926#comment-15996926
]
Ramu kakarla edited comment on CAMEL-11216 at 5/4/17 3:28 PM:
---
Hi Claus,
I have reproduced the issue. By removing Host from restConfiguration
restConfiguration().port(8080); gives Host value Null . This can be checked in
populateRests method of RouteBuilder class
##
if (getRestConfigurations() != null) {
for (Map.Entry entry :
getRestConfigurations().entrySet()) {
RestConfiguration config =
entry.getValue().asRestConfiguration(getContext());
if ("".equals(entry.getKey())) {
if(entry.getValue().getHost()==null){
throw new IllegalArgumentException("Host can't be
null");
}
###
Please verify this,so that I can raise pull req
Regards
Ramu
was (Author: kramu.k7):
Hi Claus,
I have reproduced the issue. By removing Host from restConfiguration
restConfiguration().port(8080); gives Host value Null . This can be checked in
populateRests method of RouteBuilder class
##
if (getRestConfigurations() != null) {
for (Map.Entry entry :
getRestConfigurations().entrySet()) {
RestConfiguration config =
entry.getValue().asRestConfiguration(getContext());
if ("".equals(entry.getKey())) {
if(entry.getValue().getHost()==null){
throw new IllegalArgumentException("Host can't be
null");
}
-
##
Please verify this,so that I can raise pull req
Regards
Ramu
> REST-DSL - Producer fails with NPE or other exceptions if you have not set a
> hostname
> -
>
> Key: CAMEL-11216
> URL: https://issues.apache.org/jira/browse/CAMEL-11216
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Affects Versions: 2.19.0
>Reporter: Claus Ibsen
>
> If you forget to configure a host name then the rest producer fails with
> different errors if you use http4, netty4-http, undertow etc.
> We should likely add some validation logic in the rest endpoint / rest
> producer so it can detect this missing configuration and report this in the
> same way.
> You can reproduce from this example by removing host at
> https://github.com/apache/camel/blob/master/examples/camel-example-rest-producer/src/main/java/sample/camel/RestRoute.java#L33
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CAMEL-11216) REST-DSL - Producer fails with NPE or other exceptions if you have not set a hostname
[
https://issues.apache.org/jira/browse/CAMEL-11216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996926#comment-15996926
]
Ramu kakarla commented on CAMEL-11216:
---
Hi Claus,
I have reproduced the issue. By removing Host from restConfiguration
restConfiguration().port(8080); gives Host value Null . This can be checked in
populateRests method of RouteBuilder class
##
if (getRestConfigurations() != null) {
for (Map.Entry entry :
getRestConfigurations().entrySet()) {
RestConfiguration config =
entry.getValue().asRestConfiguration(getContext());
if ("".equals(entry.getKey())) {
if(entry.getValue().getHost()==null){
throw new IllegalArgumentException("Host can't be
null");
}
-
##
Please verify this,so that I can raise pull req
Regards
Ramu
> REST-DSL - Producer fails with NPE or other exceptions if you have not set a
> hostname
> -
>
> Key: CAMEL-11216
> URL: https://issues.apache.org/jira/browse/CAMEL-11216
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Affects Versions: 2.19.0
>Reporter: Claus Ibsen
>
> If you forget to configure a host name then the rest producer fails with
> different errors if you use http4, netty4-http, undertow etc.
> We should likely add some validation logic in the rest endpoint / rest
> producer so it can detect this missing configuration and report this in the
> same way.
> You can reproduce from this example by removing host at
> https://github.com/apache/camel/blob/master/examples/camel-example-rest-producer/src/main/java/sample/camel/RestRoute.java#L33
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
