[jira] [Assigned] (CAMEL-11580) Add JMX api RouteController and SupervisingRouteController
[ https://issues.apache.org/jira/browse/CAMEL-11580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli reassigned CAMEL-11580: --- Assignee: Luca Burgazzoli > Add JMX api RouteController and SupervisingRouteController > -- > > Key: CAMEL-11580 > URL: https://issues.apache.org/jira/browse/CAMEL-11580 > Project: Camel > Issue Type: New Feature > Components: camel-core, jmx >Reporter: Claus Ibsen >Assignee: Luca Burgazzoli > Fix For: 2.20.0 > > > We should have some JMX API that can expose the state of the route, with JMX > attributes. Then there should be an extended for SupervisingRouteController > which can shows the state of each of those routes, and the backoff > configuration etc. > eg today there is little visibility for end users what is going on with the > SupervisingRouteController. We need to expose that in JMX. > Then we can leverage that also for Spring Boot and have an actuator endpoint > (/camel/route-controller) where we can report this state as json. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11579) Add unit test / example for SupervisingRouteController
[ https://issues.apache.org/jira/browse/CAMEL-11579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli reassigned CAMEL-11579: --- Assignee: Luca Burgazzoli > Add unit test / example for SupervisingRouteController > -- > > Key: CAMEL-11579 > URL: https://issues.apache.org/jira/browse/CAMEL-11579 > Project: Camel > Issue Type: Task > Components: camel-core, examples >Reporter: Claus Ibsen >Assignee: Luca Burgazzoli > Fix For: 2.20.0 > > > This new experimental code needs a bit more unit tests and also it would be > good to build an example in the examples that uses it so end users can play > with it. > The example should demonstrate that CamelContext startup but the routes are > failing during startup and they are re-attempted to start. Then there can be > some other JVM that the user can start which then allows the route to > startup, for example the JVM can have an embedded SQL database or something. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11588) SupervisingRouteController - Routes may be started in wrong order
[
https://issues.apache.org/jira/browse/CAMEL-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097747#comment-16097747
]
Claus Ibsen commented on CAMEL-11588:
-
I looked briefly at this and its a bit harder to do. So its okay for this to be
a known issue, but down the road we should ideally have this new way of
starting up routes support all existing ways, so it in the future can be the
new default way.
> SupervisingRouteController - Routes may be started in wrong order
> -
>
> Key: CAMEL-11588
> URL: https://issues.apache.org/jira/browse/CAMEL-11588
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
> Fix For: 2.20.0
>
>
> If you run the example and turn off the supervising
> Then the routes are started correct order
> {code}
> 2017-07-23 10:40:37.825 INFO 33034 --- [ main]
> o.a.camel.spring.SpringCamelContext : Route: bar started and consuming
> from: timer://bar?period=5s
> 2017-07-23 10:40:37.825 INFO 33034 --- [ main]
> o.a.camel.spring.SpringCamelContext : Route: foo started and consuming
> from: timer://foo?period=5s
> 2017-07-23 10:40:37.830 INFO 33034 --- [ main]
> o.a.c.c.undertow.DefaultUndertowHost : Starting Undertow server on
> http://localhost:9011
> 2017-07-23 10:40:37.877 INFO 33034 --- [ main]
> o.a.camel.spring.SpringCamelContext : Route: undertow started and
> consuming from: http://localhost:9011
> {code}
> eg with lowest startup order first, 1,2, (no number).
> But if you turn on supervising, then they are started: (no number), 1, 2
> {code}
> 2017-07-23 10:37:39.266 INFO 32985 --- [ main]
> o.a.c.c.undertow.DefaultUndertowHost : Starting Undertow server on
> http://localhost:9011
> 2017-07-23 10:37:39.311 INFO 32985 --- [ main]
> o.a.camel.spring.SpringCamelContext : Route: undertow started and
> consuming from: http://localhost:9011
> 2017-07-23 10:37:39.313 INFO 32985 --- [ main]
> o.a.camel.spring.SpringCamelContext : Route: bar started and consuming
> from: timer://bar?period=5s
> 2017-07-23 10:37:39.314 INFO 32985 --- [ main]
> o.a.camel.spring.SpringCamelContext : Route: foo started and consuming
> from: timer://foo?period=5s
> {code}
> eg the undertow route is the (no number) and should therefore be started last
> (it will have auto assigned number 1001).
> eg we need to use the RouteStartupOrder that can tell the correct order.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (CAMEL-11584) Add javadoc to spring boot auto configuration of camel.supervising.controller
[ https://issues.apache.org/jira/browse/CAMEL-11584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli reassigned CAMEL-11584: --- Assignee: Luca Burgazzoli > Add javadoc to spring boot auto configuration of camel.supervising.controller > - > > Key: CAMEL-11584 > URL: https://issues.apache.org/jira/browse/CAMEL-11584 > Project: Camel > Issue Type: Improvement > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Luca Burgazzoli > Fix For: 2.20.0 > > > There is no javadoc for that auto configuration classes which means there is > no end user documentation in the tooling etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11581) SupervisingRouteController should have spring-boot auto configuration
[ https://issues.apache.org/jira/browse/CAMEL-11581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli reassigned CAMEL-11581: --- Assignee: Luca Burgazzoli > SupervisingRouteController should have spring-boot auto configuration > - > > Key: CAMEL-11581 > URL: https://issues.apache.org/jira/browse/CAMEL-11581 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Luca Burgazzoli > Fix For: 2.20.0 > > > We should make it easy to configure this stuff via spring boot auto > configuration. For example that ticket with an example we can let that > example run in spring-boot and then configure the backoff stuff in the > application.properties file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11578) Add javadoc to util.backoff
[ https://issues.apache.org/jira/browse/CAMEL-11578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli reassigned CAMEL-11578: --- Assignee: Luca Burgazzoli > Add javadoc to util.backoff > --- > > Key: CAMEL-11578 > URL: https://issues.apache.org/jira/browse/CAMEL-11578 > Project: Camel > Issue Type: Task > Components: camel-core >Reporter: Claus Ibsen >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 2.20.0 > > > We should have javadoc for all our classes in camel-core -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11588) SupervisingRouteController - Routes may be started in wrong order
[
https://issues.apache.org/jira/browse/CAMEL-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Burgazzoli reassigned CAMEL-11588:
---
Assignee: Luca Burgazzoli
> SupervisingRouteController - Routes may be started in wrong order
> -
>
> Key: CAMEL-11588
> URL: https://issues.apache.org/jira/browse/CAMEL-11588
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
> Fix For: 2.20.0
>
>
> If you run the example and turn off the supervising
> Then the routes are started correct order
> {code}
> 2017-07-23 10:40:37.825 INFO 33034 --- [ main]
> o.a.camel.spring.SpringCamelContext : Route: bar started and consuming
> from: timer://bar?period=5s
> 2017-07-23 10:40:37.825 INFO 33034 --- [ main]
> o.a.camel.spring.SpringCamelContext : Route: foo started and consuming
> from: timer://foo?period=5s
> 2017-07-23 10:40:37.830 INFO 33034 --- [ main]
> o.a.c.c.undertow.DefaultUndertowHost : Starting Undertow server on
> http://localhost:9011
> 2017-07-23 10:40:37.877 INFO 33034 --- [ main]
> o.a.camel.spring.SpringCamelContext : Route: undertow started and
> consuming from: http://localhost:9011
> {code}
> eg with lowest startup order first, 1,2, (no number).
> But if you turn on supervising, then they are started: (no number), 1, 2
> {code}
> 2017-07-23 10:37:39.266 INFO 32985 --- [ main]
> o.a.c.c.undertow.DefaultUndertowHost : Starting Undertow server on
> http://localhost:9011
> 2017-07-23 10:37:39.311 INFO 32985 --- [ main]
> o.a.camel.spring.SpringCamelContext : Route: undertow started and
> consuming from: http://localhost:9011
> 2017-07-23 10:37:39.313 INFO 32985 --- [ main]
> o.a.camel.spring.SpringCamelContext : Route: bar started and consuming
> from: timer://bar?period=5s
> 2017-07-23 10:37:39.314 INFO 32985 --- [ main]
> o.a.camel.spring.SpringCamelContext : Route: foo started and consuming
> from: timer://foo?period=5s
> {code}
> eg the undertow route is the (no number) and should therefore be started last
> (it will have auto assigned number 1001).
> eg we need to use the RouteStartupOrder that can tell the correct order.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (CAMEL-11587) Backoff - Add option for initial delay
[
https://issues.apache.org/jira/browse/CAMEL-11587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Burgazzoli reassigned CAMEL-11587:
---
Assignee: Luca Burgazzoli
> Backoff - Add option for initial delay
> --
>
> Key: CAMEL-11587
> URL: https://issues.apache.org/jira/browse/CAMEL-11587
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
> Fix For: 2.20.0
>
>
> So you can set an initial delay, so the routes are not started asap.
> For example
> {code}
> camel.supervising.controller.routes.undertow.back-off.initial-delay = 10s
> camel.supervising.controller.routes.undertow.back-off.delay = 20s
> camel.supervising.controller.routes.undertow.back-off.max-attempts = 3
> {code}
> Then the first start is initially started after 10 seconds.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (CAMEL-11582) SupervisingRouteController should have better INFO logging on startup
[ https://issues.apache.org/jira/browse/CAMEL-11582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli reassigned CAMEL-11582: --- Assignee: Luca Burgazzoli > SupervisingRouteController should have better INFO logging on startup > - > > Key: CAMEL-11582 > URL: https://issues.apache.org/jira/browse/CAMEL-11582 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Luca Burgazzoli > Fix For: 2.20.0 > > > Try this example: > https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot-routecontroller > And configure it at INFO logging. We need to better tell the end user that > Camel is using the supervising route controller and therefore routes are > deferred being started. > And when all the routes has been successfully started then we should log > something at INFO that all routes are now started. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11583) SupervisingRouteController should honor if a route was explicit set to autoStartup=false
[
https://issues.apache.org/jira/browse/CAMEL-11583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Burgazzoli reassigned CAMEL-11583:
---
Assignee: Luca Burgazzoli
> SupervisingRouteController should honor if a route was explicit set to
> autoStartup=false
>
>
> Key: CAMEL-11583
> URL: https://issues.apache.org/jira/browse/CAMEL-11583
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Luca Burgazzoli
> Fix For: 2.20.0
>
>
> If the end user explict configure a route to not auto startup, then the route
> should not be under supervision.
> eg that route is only intended to be started manually by the end user.
> Currently I think the SupervisingRouteController will set all routes to auto
> startup false, and then start all of them. So it need to check the existing
> route configuration and if its autoStartup=false, then skip that route.
> We should do some kind of summary logging at INFO level when we have detected
> this and tell the user about it
> Maybe we should do a better summary INFO than we have today with
> {code}
> Total 3 routes, of which 0 are started
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (CAMEL-11563) Add predicate option to @Consume so the bean is only called if its evaluated to true
[
https://issues.apache.org/jira/browse/CAMEL-11563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-11563.
-
Resolution: Fixed
> Add predicate option to @Consume so the bean is only called if its evaluated
> to true
>
>
> Key: CAMEL-11563
> URL: https://issues.apache.org/jira/browse/CAMEL-11563
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.20.0
>
>
> This allows users to specify multiple @Consume on POJO beans methods so they
> can consume from the same endpoint but have it call different method
> depending on the predicate.
> {code}
> @Consume("jms:queue:cheese", predicate = "${body} contains 'blue'")
> public void blueCheese(String body) {
>...
> }
> @Consume("jms:queue:cheese", predicate = "${body} contains 'hawaii'")
> public void hawaiiCheese(String body) {
>...
> }
> {code}
> The predicate can be evaluated using the simple language, so users can do
> basic predicates.
> If no predicates matches then the exchange is silently dropped. If 1 or more
> predicates matches then we should either
> - send to first matching
> - send to all matching in sequence (need to do defensive copy to prevent side
> effects) also mind of streaming, so users may need to turn on stream caching,
> and we should ensure that its part of the POJO consuming (I cannot remember)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (CAMEL-11563) Add predicate option to @Consume so the bean is only called if its evaluated to true
[
https://issues.apache.org/jira/browse/CAMEL-11563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-11563:
Fix Version/s: (was: Future)
2.20.0
> Add predicate option to @Consume so the bean is only called if its evaluated
> to true
>
>
> Key: CAMEL-11563
> URL: https://issues.apache.org/jira/browse/CAMEL-11563
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: 2.20.0
>
>
> This allows users to specify multiple @Consume on POJO beans methods so they
> can consume from the same endpoint but have it call different method
> depending on the predicate.
> {code}
> @Consume("jms:queue:cheese", predicate = "${body} contains 'blue'")
> public void blueCheese(String body) {
>...
> }
> @Consume("jms:queue:cheese", predicate = "${body} contains 'hawaii'")
> public void hawaiiCheese(String body) {
>...
> }
> {code}
> The predicate can be evaluated using the simple language, so users can do
> basic predicates.
> If no predicates matches then the exchange is silently dropped. If 1 or more
> predicates matches then we should either
> - send to first matching
> - send to all matching in sequence (need to do defensive copy to prevent side
> effects) also mind of streaming, so users may need to turn on stream caching,
> and we should ensure that its part of the POJO consuming (I cannot remember)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (CAMEL-11563) Add predicate option to @Consume so the bean is only called if its evaluated to true
[
https://issues.apache.org/jira/browse/CAMEL-11563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-11563:
---
Assignee: Claus Ibsen
> Add predicate option to @Consume so the bean is only called if its evaluated
> to true
>
>
> Key: CAMEL-11563
> URL: https://issues.apache.org/jira/browse/CAMEL-11563
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
> Fix For: Future
>
>
> This allows users to specify multiple @Consume on POJO beans methods so they
> can consume from the same endpoint but have it call different method
> depending on the predicate.
> {code}
> @Consume("jms:queue:cheese", predicate = "${body} contains 'blue'")
> public void blueCheese(String body) {
>...
> }
> @Consume("jms:queue:cheese", predicate = "${body} contains 'hawaii'")
> public void hawaiiCheese(String body) {
>...
> }
> {code}
> The predicate can be evaluated using the simple language, so users can do
> basic predicates.
> If no predicates matches then the exchange is silently dropped. If 1 or more
> predicates matches then we should either
> - send to first matching
> - send to all matching in sequence (need to do defensive copy to prevent side
> effects) also mind of streaming, so users may need to turn on stream caching,
> and we should ensure that its part of the POJO consuming (I cannot remember)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11563) Add predicate option to @Consume so the bean is only called if its evaluated to true
[
https://issues.apache.org/jira/browse/CAMEL-11563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097608#comment-16097608
]
Claus Ibsen commented on CAMEL-11563:
-
This is a bit more tricky as we want to reuse the same consumer, and then we
have lifecycle issues to deal with, eg if a bean with a predicate is stopped,
then any other beans must still run, until there are no more.
> Add predicate option to @Consume so the bean is only called if its evaluated
> to true
>
>
> Key: CAMEL-11563
> URL: https://issues.apache.org/jira/browse/CAMEL-11563
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
> Fix For: Future
>
>
> This allows users to specify multiple @Consume on POJO beans methods so they
> can consume from the same endpoint but have it call different method
> depending on the predicate.
> {code}
> @Consume("jms:queue:cheese", predicate = "${body} contains 'blue'")
> public void blueCheese(String body) {
>...
> }
> @Consume("jms:queue:cheese", predicate = "${body} contains 'hawaii'")
> public void hawaiiCheese(String body) {
>...
> }
> {code}
> The predicate can be evaluated using the simple language, so users can do
> basic predicates.
> If no predicates matches then the exchange is silently dropped. If 1 or more
> predicates matches then we should either
> - send to first matching
> - send to all matching in sequence (need to do defensive copy to prevent side
> effects) also mind of streaming, so users may need to turn on stream caching,
> and we should ensure that its part of the POJO consuming (I cannot remember)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (CAMEL-11563) Add predicate option to @Consume so the bean is only called if its evaluated to true
[
https://issues.apache.org/jira/browse/CAMEL-11563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-11563:
Estimated Complexity: Moderate (was: Unknown)
> Add predicate option to @Consume so the bean is only called if its evaluated
> to true
>
>
> Key: CAMEL-11563
> URL: https://issues.apache.org/jira/browse/CAMEL-11563
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Claus Ibsen
> Fix For: Future
>
>
> This allows users to specify multiple @Consume on POJO beans methods so they
> can consume from the same endpoint but have it call different method
> depending on the predicate.
> {code}
> @Consume("jms:queue:cheese", predicate = "${body} contains 'blue'")
> public void blueCheese(String body) {
>...
> }
> @Consume("jms:queue:cheese", predicate = "${body} contains 'hawaii'")
> public void hawaiiCheese(String body) {
>...
> }
> {code}
> The predicate can be evaluated using the simple language, so users can do
> basic predicates.
> If no predicates matches then the exchange is silently dropped. If 1 or more
> predicates matches then we should either
> - send to first matching
> - send to all matching in sequence (need to do defensive copy to prevent side
> effects) also mind of streaming, so users may need to turn on stream caching,
> and we should ensure that its part of the POJO consuming (I cannot remember)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11573) Enable MultipleConsumersSupport for Jt400Endpoint
[ https://issues.apache.org/jira/browse/CAMEL-11573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097605#comment-16097605 ] Claus Ibsen commented on CAMEL-11573: - You are welcome to provide a patch or github PR with a implementation of this. > Enable MultipleConsumersSupport for Jt400Endpoint > - > > Key: CAMEL-11573 > URL: https://issues.apache.org/jira/browse/CAMEL-11573 > Project: Camel > Issue Type: New Feature > Components: camel-jt400 >Reporter: Rafał Gała >Priority: Minor > Fix For: 2.20.0 > > > We set up a Camel route that consumes messages from AS400 data queue in 20 > concurrent tasks using a secure connection. The problem is that on AS400 > system all communication is handled by a single thread and maximum throughput > we can achieve is somewhere around 300mbps. It simply reaches a CPU > processing limit and just cannot do more bceause all communication is being > done within a single connection to AS400 system. If Jt400Endpoint class > implemented MultipleConsumersSupport interface, we would be able to set up > multiple consumers for this endpoint which would result in more than one > connection to AS400 thus the processing would be split to many threads on > AS400 system. > When we disable security and the traffic is unencrypted, the problem goes > away, but we really would like to stick with encrypted traffic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11573) Enable MultipleConsumersSupport for Jt400Endpoint
[ https://issues.apache.org/jira/browse/CAMEL-11573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11573: Fix Version/s: 2.20.0 > Enable MultipleConsumersSupport for Jt400Endpoint > - > > Key: CAMEL-11573 > URL: https://issues.apache.org/jira/browse/CAMEL-11573 > Project: Camel > Issue Type: New Feature > Components: camel-jt400 >Reporter: Rafał Gała >Priority: Minor > Fix For: 2.20.0 > > > We set up a Camel route that consumes messages from AS400 data queue in 20 > concurrent tasks using a secure connection. The problem is that on AS400 > system all communication is handled by a single thread and maximum throughput > we can achieve is somewhere around 300mbps. It simply reaches a CPU > processing limit and just cannot do more bceause all communication is being > done within a single connection to AS400 system. If Jt400Endpoint class > implemented MultipleConsumersSupport interface, we would be able to set up > multiple consumers for this endpoint which would result in more than one > connection to AS400 thus the processing would be split to many threads on > AS400 system. > When we disable security and the traffic is unencrypted, the problem goes > away, but we really would like to stick with encrypted traffic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (CAMEL-11573) Enable MultipleConsumersSupport for Jt400Endpoint
[ https://issues.apache.org/jira/browse/CAMEL-11573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11573: Estimated Complexity: Novice (was: Unknown) > Enable MultipleConsumersSupport for Jt400Endpoint > - > > Key: CAMEL-11573 > URL: https://issues.apache.org/jira/browse/CAMEL-11573 > Project: Camel > Issue Type: New Feature > Components: camel-jt400 >Reporter: Rafał Gała >Priority: Minor > Fix For: 2.20.0 > > > We set up a Camel route that consumes messages from AS400 data queue in 20 > concurrent tasks using a secure connection. The problem is that on AS400 > system all communication is handled by a single thread and maximum throughput > we can achieve is somewhere around 300mbps. It simply reaches a CPU > processing limit and just cannot do more bceause all communication is being > done within a single connection to AS400 system. If Jt400Endpoint class > implemented MultipleConsumersSupport interface, we would be able to set up > multiple consumers for this endpoint which would result in more than one > connection to AS400 thus the processing would be split to many threads on > AS400 system. > When we disable security and the traffic is unencrypted, the problem goes > away, but we really would like to stick with encrypted traffic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11553) Upgrade to Brave 4
[
https://issues.apache.org/jira/browse/CAMEL-11553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097604#comment-16097604
]
Claus Ibsen commented on CAMEL-11553:
-
Ah okay, so its a matter of using the newer api than the older one. A PR is
much welcome.
> Upgrade to Brave 4
> --
>
> Key: CAMEL-11553
> URL: https://issues.apache.org/jira/browse/CAMEL-11553
> Project: Camel
> Issue Type: Task
> Components: camel-zipkin
>Affects Versions: 2.19.1
>Reporter: Radek Mensik
>Assignee: Kevin Earls
>Priority: Minor
> Fix For: 2.20.0
>
>
> It would be nice to have up to date library not using deprecated code,
> because:
> Brave v. 4 allows you to use _brave.Tracing_ so one can easily register
> https://github.com/openzipkin/brave/tree/master/context/slf4j which allows
> you to have in each log line info about spans:
> {code:java}
> 2017-07-17 17:44:08.526 INFO [proxy,b805c5edbe362a7c,b805c5edbe362a7c,true]
> {code}
> Then it is easy to copy and use span id to zipkin UI in case of debugging.
> (btw currently there is Long value of span instead of Hexadecimal printed).
> There is possibility to overlap with version 3 and 4 ->
> https://github.com/openzipkin/brave/tree/master/brave#upgrading-from-brave-3
> so this could be good start.
> Also _brave.sampler.Sampler_ should be used in stead of
> _com.github.kristofa.brave.Sampler_
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (CAMEL-11553) Upgrade to Brave 4
[
https://issues.apache.org/jira/browse/CAMEL-11553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-11553:
Fix Version/s: 2.20.0
> Upgrade to Brave 4
> --
>
> Key: CAMEL-11553
> URL: https://issues.apache.org/jira/browse/CAMEL-11553
> Project: Camel
> Issue Type: Task
> Components: camel-zipkin
>Affects Versions: 2.19.1
>Reporter: Radek Mensik
>Assignee: Kevin Earls
>Priority: Minor
> Fix For: 2.20.0
>
>
> It would be nice to have up to date library not using deprecated code,
> because:
> Brave v. 4 allows you to use _brave.Tracing_ so one can easily register
> https://github.com/openzipkin/brave/tree/master/context/slf4j which allows
> you to have in each log line info about spans:
> {code:java}
> 2017-07-17 17:44:08.526 INFO [proxy,b805c5edbe362a7c,b805c5edbe362a7c,true]
> {code}
> Then it is easy to copy and use span id to zipkin UI in case of debugging.
> (btw currently there is Long value of span instead of Hexadecimal printed).
> There is possibility to overlap with version 3 and 4 ->
> https://github.com/openzipkin/brave/tree/master/brave#upgrading-from-brave-3
> so this could be good start.
> Also _brave.sampler.Sampler_ should be used in stead of
> _com.github.kristofa.brave.Sampler_
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (CAMEL-11455) Automatic transform String to DBObject after previous conversion error
[ https://issues.apache.org/jira/browse/CAMEL-11455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-11455. - Resolution: Fixed > Automatic transform String to DBObject after previous conversion error > -- > > Key: CAMEL-11455 > URL: https://issues.apache.org/jira/browse/CAMEL-11455 > Project: Camel > Issue Type: Bug > Components: camel-mongodb, camel-mongodb3 >Affects Versions: 2.19.1 >Reporter: Fabrizio Spataro >Assignee: Claus Ibsen > Fix For: 2.20.0, 2.19.3 > > Attachments: jsonFormatterDisappear.zip > > > Hello, > i found a bug. To reproduce it you can execute the code (see attachment file). > The bug is simple: > After an invalid conversion, the automatic String -> JSON transformation used > to put a document into MongoDB collection, fail! > Application flow: > # First document can be convert to JSON, Mongodb create a document (correct) > # Second document has an error, Mongodb cannot create a document (correct) > # Third document can be convert to JSON but Mongodb cannot create a document > into collection because automatic conversion is broken!!! (BUG) > Kings regards -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11455) Automatic transform String to DBObject after previous conversion error
[ https://issues.apache.org/jira/browse/CAMEL-11455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097572#comment-16097572 ] Fabrizio Spataro commented on CAMEL-11455: -- sorry guys but i cannot fix it before 1st August! > Automatic transform String to DBObject after previous conversion error > -- > > Key: CAMEL-11455 > URL: https://issues.apache.org/jira/browse/CAMEL-11455 > Project: Camel > Issue Type: Bug > Components: camel-mongodb, camel-mongodb3 >Affects Versions: 2.19.1 >Reporter: Fabrizio Spataro >Assignee: Claus Ibsen > Fix For: 2.20.0, 2.19.3 > > Attachments: jsonFormatterDisappear.zip > > > Hello, > i found a bug. To reproduce it you can execute the code (see attachment file). > The bug is simple: > After an invalid conversion, the automatic String -> JSON transformation used > to put a document into MongoDB collection, fail! > Application flow: > # First document can be convert to JSON, Mongodb create a document (correct) > # Second document has an error, Mongodb cannot create a document (correct) > # Third document can be convert to JSON but Mongodb cannot create a document > into collection because automatic conversion is broken!!! (BUG) > Kings regards -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (CAMEL-11455) Automatic transform String to DBObject after previous conversion error
[ https://issues.apache.org/jira/browse/CAMEL-11455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-11455: --- Assignee: Claus Ibsen (was: Fabrizio Spataro) > Automatic transform String to DBObject after previous conversion error > -- > > Key: CAMEL-11455 > URL: https://issues.apache.org/jira/browse/CAMEL-11455 > Project: Camel > Issue Type: Bug > Components: camel-mongodb, camel-mongodb3 >Affects Versions: 2.19.1 >Reporter: Fabrizio Spataro >Assignee: Claus Ibsen > Fix For: 2.20.0, 2.19.3 > > Attachments: jsonFormatterDisappear.zip > > > Hello, > i found a bug. To reproduce it you can execute the code (see attachment file). > The bug is simple: > After an invalid conversion, the automatic String -> JSON transformation used > to put a document into MongoDB collection, fail! > Application flow: > # First document can be convert to JSON, Mongodb create a document (correct) > # Second document has an error, Mongodb cannot create a document (correct) > # Third document can be convert to JSON but Mongodb cannot create a document > into collection because automatic conversion is broken!!! (BUG) > Kings regards -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11588) SupervisingRouteController - Routes may be started in wrong order
Claus Ibsen created CAMEL-11588:
---
Summary: SupervisingRouteController - Routes may be started in
wrong order
Key: CAMEL-11588
URL: https://issues.apache.org/jira/browse/CAMEL-11588
Project: Camel
Issue Type: Bug
Components: camel-core
Reporter: Claus Ibsen
Fix For: 2.20.0
If you run the example and turn off the supervising
Then the routes are started correct order
{code}
2017-07-23 10:40:37.825 INFO 33034 --- [ main]
o.a.camel.spring.SpringCamelContext : Route: bar started and consuming
from: timer://bar?period=5s
2017-07-23 10:40:37.825 INFO 33034 --- [ main]
o.a.camel.spring.SpringCamelContext : Route: foo started and consuming
from: timer://foo?period=5s
2017-07-23 10:40:37.830 INFO 33034 --- [ main]
o.a.c.c.undertow.DefaultUndertowHost : Starting Undertow server on
http://localhost:9011
2017-07-23 10:40:37.877 INFO 33034 --- [ main]
o.a.camel.spring.SpringCamelContext : Route: undertow started and
consuming from: http://localhost:9011
{code}
eg with lowest startup order first, 1,2, (no number).
But if you turn on supervising, then they are started: (no number), 1, 2
{code}
2017-07-23 10:37:39.266 INFO 32985 --- [ main]
o.a.c.c.undertow.DefaultUndertowHost : Starting Undertow server on
http://localhost:9011
2017-07-23 10:37:39.311 INFO 32985 --- [ main]
o.a.camel.spring.SpringCamelContext : Route: undertow started and
consuming from: http://localhost:9011
2017-07-23 10:37:39.313 INFO 32985 --- [ main]
o.a.camel.spring.SpringCamelContext : Route: bar started and consuming
from: timer://bar?period=5s
2017-07-23 10:37:39.314 INFO 32985 --- [ main]
o.a.camel.spring.SpringCamelContext : Route: foo started and consuming
from: timer://foo?period=5s
{code}
eg the undertow route is the (no number) and should therefore be started last
(it will have auto assigned number 1001).
eg we need to use the RouteStartupOrder that can tell the correct order.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (CAMEL-11587) Backoff - Add option for initial delay
Claus Ibsen created CAMEL-11587:
---
Summary: Backoff - Add option for initial delay
Key: CAMEL-11587
URL: https://issues.apache.org/jira/browse/CAMEL-11587
Project: Camel
Issue Type: Improvement
Components: camel-core
Reporter: Claus Ibsen
Fix For: 2.20.0
So you can set an initial delay, so the routes are not started asap.
For example
{code}
camel.supervising.controller.routes.undertow.back-off.initial-delay = 10s
camel.supervising.controller.routes.undertow.back-off.delay = 20s
camel.supervising.controller.routes.undertow.back-off.max-attempts = 3
{code}
Then the first start is initially started after 10 seconds.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (CAMEL-11586) camel-spring-boot - Have default value for endpoints.camelroutes.path
Claus Ibsen created CAMEL-11586:
---
Summary: camel-spring-boot - Have default value for
endpoints.camelroutes.path
Key: CAMEL-11586
URL: https://issues.apache.org/jira/browse/CAMEL-11586
Project: Camel
Issue Type: Improvement
Components: camel-spring-boot
Reporter: Claus Ibsen
Fix For: 2.20.0
We dont have a default value for endpoints.camelroutes.path so users must
configure it
{code}
endpoints.camelroutes.path = /camel/routes
endpoints.camelroutes.enabled = true
{code}
We should have a default value as above. And its default enabled anyway, so end
users don't have to do anything its just there OOTB.
See the file additional-spring-configuration-metadata.json
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (CAMEL-11586) camel-spring-boot - Have default value for endpoints.camelroutes.path
[
https://issues.apache.org/jira/browse/CAMEL-11586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-11586:
Estimated Complexity: Novice (was: Unknown)
> camel-spring-boot - Have default value for endpoints.camelroutes.path
> -
>
> Key: CAMEL-11586
> URL: https://issues.apache.org/jira/browse/CAMEL-11586
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot
>Reporter: Claus Ibsen
> Fix For: 2.20.0
>
>
> We dont have a default value for endpoints.camelroutes.path so users must
> configure it
> {code}
> endpoints.camelroutes.path = /camel/routes
> endpoints.camelroutes.enabled = true
> {code}
> We should have a default value as above. And its default enabled anyway, so
> end users don't have to do anything its just there OOTB.
> See the file additional-spring-configuration-metadata.json
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (CAMEL-11585) camel-spring-boot - Allow to reset route statistics via actuator
Claus Ibsen created CAMEL-11585:
---
Summary: camel-spring-boot - Allow to reset route statistics via
actuator
Key: CAMEL-11585
URL: https://issues.apache.org/jira/browse/CAMEL-11585
Project: Camel
Issue Type: Improvement
Components: camel-spring-boot
Reporter: Claus Ibsen
Priority: Minor
Fix For: 2.20.0
You can start/stop/suspend/resume routes etc. But it would also be nice to be
able to reset the JMX statistics.
for example if you stop and start a route, then it continues with the existing
JMX stats (but sometimes you want to be able to reset).
{code}
8080/camel/routes/bar/info
{"id":"bar","uptimeMillis":0,"status":"Stopped","details":{"deltaProcessingTime":0,"exchangesInflight":0,"exchangesTotal":103,"externalRedeliveries":0,"failuresHandled":0,"firstExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-1","firstExchangeCompletedTimestamp":1500797883793,"lastExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-205","lastExchangeCompletedTimestamp":1500798394054,"lastProcessingTime":0,"maxProcessingTime":4,"meanProcessingTime":0,"minProcessingTime":0,"redeliveries":0,"totalProcessingTime":30,"hasRouteController":false}}davsclaus:/Users/davsclaus/$
curl -XGET -s http://localhost:8080/camel/routes/bar/info^C
davsclaus:/Users/davsclaus/$ ^C
davsclaus:/Users/davsclaus/$ ^C
davsclaus:/Users/davsclaus/$ curl -XGET -s
http://localhost:8080/camel/routes/bar^C
davsclaus:/Users/davsclaus/$ curl -XPOST -s
http://localhost:8080/camel/routes/bar/start
davsclaus:/Users/davsclaus/$ curl -XGET -s
http://localhost:8080/camel/routes/bar/info
{"id":"bar","uptime":"1.701
seconds","uptimeMillis":1701,"status":"Started","details":{"deltaProcessingTime":0,"exchangesInflight":0,"exchangesTotal":104,"externalRedeliveries":0,"failuresHandled":0,"firstExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-1","firstExchangeCompletedTimestamp":1500797883793,"lastExchangeCompletedExchangeId":"ID-davsclaus-pro-local-1500797880917-0-218","lastExchangeCompletedTimestamp":1500798449710,"lastProcessingTime":0,"maxProcessingTime":4,"meanProcessingTime":0,"minProcessingTime":0,"redeliveries":0,"totalProcessingTime":30,"hasRouteController":true}}davsclaus:/Users/davsclaus/$
curl -XGET -s http://localhost:8080/camel/routes/bar/info
{code}
So we need a reset command
curl -XPOST -s http://localhost:8080/camel/routes/bar/reset
That just calls the JMX reset operation on the route mbean. It should also
reset the processors, eg call this with true
@ManagedOperation(description = "Reset counters")
void reset(boolean includeProcessors) throws Exception;
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CAMEL-11581) SupervisingRouteController should have spring-boot auto configuration
[ https://issues.apache.org/jira/browse/CAMEL-11581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097552#comment-16097552 ] Claus Ibsen commented on CAMEL-11581: - Oh the auto configuration was in the wrong place, it should be moved from platforms/spring-boot/components-starter/camel-core-starter/src/main/java/org/apache/camel/impl/springboot/SupervisingRouteControllerConfiguration.java to the real camel-spring-boot component so we have it all there. Ideally those -starter components are primary just auto generated via the tooling that creates those source files. > SupervisingRouteController should have spring-boot auto configuration > - > > Key: CAMEL-11581 > URL: https://issues.apache.org/jira/browse/CAMEL-11581 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Claus Ibsen > Fix For: 2.20.0 > > > We should make it easy to configure this stuff via spring boot auto > configuration. For example that ticket with an example we can let that > example run in spring-boot and then configure the backoff stuff in the > application.properties file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (CAMEL-11581) SupervisingRouteController should have spring-boot auto configuration
[ https://issues.apache.org/jira/browse/CAMEL-11581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reopened CAMEL-11581: - > SupervisingRouteController should have spring-boot auto configuration > - > > Key: CAMEL-11581 > URL: https://issues.apache.org/jira/browse/CAMEL-11581 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Claus Ibsen > Fix For: 2.20.0 > > > We should make it easy to configure this stuff via spring boot auto > configuration. For example that ticket with an example we can let that > example run in spring-boot and then configure the backoff stuff in the > application.properties file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11584) Add javadoc to spring boot auto configuration of camel.supervising.controller
Claus Ibsen created CAMEL-11584: --- Summary: Add javadoc to spring boot auto configuration of camel.supervising.controller Key: CAMEL-11584 URL: https://issues.apache.org/jira/browse/CAMEL-11584 Project: Camel Issue Type: Improvement Components: camel-spring-boot Reporter: Claus Ibsen Fix For: 2.20.0 There is no javadoc for that auto configuration classes which means there is no end user documentation in the tooling etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11583) SupervisingRouteController should honor if a route was explicit set to autoStartup=false
Claus Ibsen created CAMEL-11583:
---
Summary: SupervisingRouteController should honor if a route was
explicit set to autoStartup=false
Key: CAMEL-11583
URL: https://issues.apache.org/jira/browse/CAMEL-11583
Project: Camel
Issue Type: Improvement
Components: camel-core
Reporter: Claus Ibsen
Fix For: 2.20.0
If the end user explict configure a route to not auto startup, then the route
should not be under supervision.
eg that route is only intended to be started manually by the end user.
Currently I think the SupervisingRouteController will set all routes to auto
startup false, and then start all of them. So it need to check the existing
route configuration and if its autoStartup=false, then skip that route.
We should do some kind of summary logging at INFO level when we have detected
this and tell the user about it
Maybe we should do a better summary INFO than we have today with
{code}
Total 3 routes, of which 0 are started
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (CAMEL-11582) SupervisingRouteController should have better INFO logging on startup
Claus Ibsen created CAMEL-11582: --- Summary: SupervisingRouteController should have better INFO logging on startup Key: CAMEL-11582 URL: https://issues.apache.org/jira/browse/CAMEL-11582 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 2.20.0 Try this example: https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot-routecontroller And configure it at INFO logging. We need to better tell the end user that Camel is using the supervising route controller and therefore routes are deferred being started. And when all the routes has been successfully started then we should log something at INFO that all routes are now started. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11580) Add JMX api RouteController and SupervisingRouteController
[ https://issues.apache.org/jira/browse/CAMEL-11580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097547#comment-16097547 ] Claus Ibsen commented on CAMEL-11580: - eg we should be able to see from JMX and spring-boot actuator each state of those supervised routes, with their backoff configuration and their current values and the exception message of the last error (and possible to obtain the stacktrace as well). And maybe also a value that indicate when the route will be attempt to start again (eg a count down of seconds until next attempt). > Add JMX api RouteController and SupervisingRouteController > -- > > Key: CAMEL-11580 > URL: https://issues.apache.org/jira/browse/CAMEL-11580 > Project: Camel > Issue Type: New Feature > Components: camel-core, jmx >Reporter: Claus Ibsen > Fix For: 2.20.0 > > > We should have some JMX API that can expose the state of the route, with JMX > attributes. Then there should be an extended for SupervisingRouteController > which can shows the state of each of those routes, and the backoff > configuration etc. > eg today there is little visibility for end users what is going on with the > SupervisingRouteController. We need to expose that in JMX. > Then we can leverage that also for Spring Boot and have an actuator endpoint > (/camel/route-controller) where we can report this state as json. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (CAMEL-11581) SupervisingRouteController should have spring-boot auto configuration
[ https://issues.apache.org/jira/browse/CAMEL-11581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-11581. - Resolution: Implemented Ah doh it was already implemented. Didn't spot that, need one more coffee. > SupervisingRouteController should have spring-boot auto configuration > - > > Key: CAMEL-11581 > URL: https://issues.apache.org/jira/browse/CAMEL-11581 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Claus Ibsen > Fix For: 2.20.0 > > > We should make it easy to configure this stuff via spring boot auto > configuration. For example that ticket with an example we can let that > example run in spring-boot and then configure the backoff stuff in the > application.properties file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11579) Add unit test / example for SupervisingRouteController
[ https://issues.apache.org/jira/browse/CAMEL-11579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097546#comment-16097546 ] Claus Ibsen commented on CAMEL-11579: - There is an example at https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot-routecontroller So its likely a bit more unit tests which we lack > Add unit test / example for SupervisingRouteController > -- > > Key: CAMEL-11579 > URL: https://issues.apache.org/jira/browse/CAMEL-11579 > Project: Camel > Issue Type: Task > Components: camel-core, examples >Reporter: Claus Ibsen > Fix For: 2.20.0 > > > This new experimental code needs a bit more unit tests and also it would be > good to build an example in the examples that uses it so end users can play > with it. > The example should demonstrate that CamelContext startup but the routes are > failing during startup and they are re-attempted to start. Then there can be > some other JVM that the user can start which then allows the route to > startup, for example the JVM can have an embedded SQL database or something. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11581) SupervisingRouteController should have spring-boot auto configuration
Claus Ibsen created CAMEL-11581: --- Summary: SupervisingRouteController should have spring-boot auto configuration Key: CAMEL-11581 URL: https://issues.apache.org/jira/browse/CAMEL-11581 Project: Camel Issue Type: New Feature Components: camel-spring-boot Reporter: Claus Ibsen Fix For: 2.20.0 We should make it easy to configure this stuff via spring boot auto configuration. For example that ticket with an example we can let that example run in spring-boot and then configure the backoff stuff in the application.properties file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11580) Add JMX api RouteController and SupervisingRouteController
Claus Ibsen created CAMEL-11580: --- Summary: Add JMX api RouteController and SupervisingRouteController Key: CAMEL-11580 URL: https://issues.apache.org/jira/browse/CAMEL-11580 Project: Camel Issue Type: New Feature Components: camel-core, jmx Reporter: Claus Ibsen Fix For: 2.20.0 We should have some JMX API that can expose the state of the route, with JMX attributes. Then there should be an extended for SupervisingRouteController which can shows the state of each of those routes, and the backoff configuration etc. eg today there is little visibility for end users what is going on with the SupervisingRouteController. We need to expose that in JMX. Then we can leverage that also for Spring Boot and have an actuator endpoint (/camel/route-controller) where we can report this state as json. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11579) Add unit test / example for SupervisingRouteController
Claus Ibsen created CAMEL-11579: --- Summary: Add unit test / example for SupervisingRouteController Key: CAMEL-11579 URL: https://issues.apache.org/jira/browse/CAMEL-11579 Project: Camel Issue Type: Task Components: camel-core, examples Reporter: Claus Ibsen Fix For: 2.20.0 This new experimental code needs a bit more unit tests and also it would be good to build an example in the examples that uses it so end users can play with it. The example should demonstrate that CamelContext startup but the routes are failing during startup and they are re-attempted to start. Then there can be some other JVM that the user can start which then allows the route to startup, for example the JVM can have an embedded SQL database or something. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (CAMEL-11578) Add javadoc to util.backoff
Claus Ibsen created CAMEL-11578: --- Summary: Add javadoc to util.backoff Key: CAMEL-11578 URL: https://issues.apache.org/jira/browse/CAMEL-11578 Project: Camel Issue Type: Task Components: camel-core Reporter: Claus Ibsen Priority: Minor Fix For: 2.20.0 We should have javadoc for all our classes in camel-core -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CAMEL-11292) support for Scala 2.12.x
[ https://issues.apache.org/jira/browse/CAMEL-11292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097541#comment-16097541 ] Claus Ibsen commented on CAMEL-11292: - I upgraded a few components that was using scala 2.10 to 2.11 so they are all aligned, so everything is using Scala 2.11. > support for Scala 2.12.x > > > Key: CAMEL-11292 > URL: https://issues.apache.org/jira/browse/CAMEL-11292 > Project: Camel > Issue Type: New Feature > Components: camel-scala >Affects Versions: 2.19.0 >Reporter: Sarunas Valaskevicius > > currently camel-scala depends on Scala 2.11. could this be upgraded to 2.12.x > release? > Same with scalatest. > All possible updates can be seen here - > https://mvnrepository.com/artifact/org.apache.camel/camel-scala/2.19.0 > Thanks -- This message was sent by Atlassian JIRA (v6.4.14#64029)
