[jira] [Commented] (CAMEL-18444) camel-caffeine - Caffeine-cache query parameter action does not work
[
https://issues.apache.org/jira/browse/CAMEL-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598187#comment-17598187
]
Andrea Cosentino commented on CAMEL-18444:
--
In the example with the header it is working just because the endpoint it is
the same "caffeine-cache://cache?key=1", in that case the endpoint will be
re-used. In the case of invoking action the endpoint will be different between
first and second invocation, so you'll have a new "cache" cache and the GET
won't return any result.
> camel-caffeine - Caffeine-cache query parameter action does not work
>
>
> Key: CAMEL-18444
> URL: https://issues.apache.org/jira/browse/CAMEL-18444
> Project: Camel
> Issue Type: Bug
> Components: camel-caffeine
>Affects Versions: 3.18.1
>Reporter: Marat Gubaidullin
>Priority: Major
> Fix For: 3.18.2, 3.19.0
>
>
> Caffeine-cache example using headers works fine:
> {code:java}
> from("timer:test2")
> .setBody(constant("VALUE_1"))
> .setHeader("CamelCaffeineAction", constant("PUT"))
> .to("caffeine-cache://cache?key=1")
> .setBody(constant("VALUE_2"))
> .setHeader("CamelCaffeineAction", constant("GET"))
> .to("caffeine-cache://cache?key=1")
> .log("Result2: ${body},
> ${header.CamelCaffeineActionHasResult}");
> {code}
> Same code using query parameter action does not work:
> {code:java}
> from("timer:test1")
> .setBody(constant("VALUE_1"))
> .to("caffeine-cache://cache?action=PUT=1")
> .setBody(constant("VALUE_2"))
> .to("caffeine-cache://cache?key=1=GET")
> .log("Result1: ${body},
> ${header.CamelCaffeineActionHasResult}");
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18444) camel-caffeine - Caffeine-cache query parameter action does not work
[
https://issues.apache.org/jira/browse/CAMEL-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598186#comment-17598186
]
Andrea Cosentino commented on CAMEL-18444:
--
You need to bind the cache "cache" to the registry, otherwise in the GET action
a cache named "cache" will be re-instantiated from scratch.
> camel-caffeine - Caffeine-cache query parameter action does not work
>
>
> Key: CAMEL-18444
> URL: https://issues.apache.org/jira/browse/CAMEL-18444
> Project: Camel
> Issue Type: Bug
> Components: camel-caffeine
>Affects Versions: 3.18.1
>Reporter: Marat Gubaidullin
>Priority: Major
> Fix For: 3.18.2, 3.19.0
>
>
> Caffeine-cache example using headers works fine:
> {code:java}
> from("timer:test2")
> .setBody(constant("VALUE_1"))
> .setHeader("CamelCaffeineAction", constant("PUT"))
> .to("caffeine-cache://cache?key=1")
> .setBody(constant("VALUE_2"))
> .setHeader("CamelCaffeineAction", constant("GET"))
> .to("caffeine-cache://cache?key=1")
> .log("Result2: ${body},
> ${header.CamelCaffeineActionHasResult}");
> {code}
> Same code using query parameter action does not work:
> {code:java}
> from("timer:test1")
> .setBody(constant("VALUE_1"))
> .to("caffeine-cache://cache?action=PUT=1")
> .setBody(constant("VALUE_2"))
> .to("caffeine-cache://cache?key=1=GET")
> .log("Result1: ${body},
> ${header.CamelCaffeineActionHasResult}");
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18438) camel-main - Add option to configure context description
[ https://issues.apache.org/jira/browse/CAMEL-18438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18438. - Resolution: Fixed > camel-main - Add option to configure context description > > > Key: CAMEL-18438 > URL: https://issues.apache.org/jira/browse/CAMEL-18438 > Project: Camel > Issue Type: Improvement > Components: camel-main >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.19.0 > > > You can set name via > camel.main.name = foo > But we should have a description so you can do > camel.main.name = account-to-payroll > camel.main.description = Reconciles the bank accounts with the payroll system > And we can show the description in tooling that can allow users to quicker > understand what this camel app does -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18444) Caffeine-cache query parameter action does not work
[
https://issues.apache.org/jira/browse/CAMEL-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18444:
Fix Version/s: 3.18.2
3.19.0
> Caffeine-cache query parameter action does not work
> ---
>
> Key: CAMEL-18444
> URL: https://issues.apache.org/jira/browse/CAMEL-18444
> Project: Camel
> Issue Type: Bug
> Components: camel-caffeine
>Affects Versions: 3.18.1
>Reporter: Marat Gubaidullin
>Priority: Major
> Fix For: 3.18.2, 3.19.0
>
>
> Caffeine-cache example using headers works fine:
> {code:java}
> from("timer:test2")
> .setBody(constant("VALUE_1"))
> .setHeader("CamelCaffeineAction", constant("PUT"))
> .to("caffeine-cache://cache?key=1")
> .setBody(constant("VALUE_2"))
> .setHeader("CamelCaffeineAction", constant("GET"))
> .to("caffeine-cache://cache?key=1")
> .log("Result2: ${body},
> ${header.CamelCaffeineActionHasResult}");
> {code}
> Same code using query parameter action does not work:
> {code:java}
> from("timer:test1")
> .setBody(constant("VALUE_1"))
> .to("caffeine-cache://cache?action=PUT=1")
> .setBody(constant("VALUE_2"))
> .to("caffeine-cache://cache?key=1=GET")
> .log("Result1: ${body},
> ${header.CamelCaffeineActionHasResult}");
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18444) camel-caffeine - Caffeine-cache query parameter action does not work
[
https://issues.apache.org/jira/browse/CAMEL-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18444:
Summary: camel-caffeine - Caffeine-cache query parameter action does not
work (was: Caffeine-cache query parameter action does not work)
> camel-caffeine - Caffeine-cache query parameter action does not work
>
>
> Key: CAMEL-18444
> URL: https://issues.apache.org/jira/browse/CAMEL-18444
> Project: Camel
> Issue Type: Bug
> Components: camel-caffeine
>Affects Versions: 3.18.1
>Reporter: Marat Gubaidullin
>Priority: Major
> Fix For: 3.18.2, 3.19.0
>
>
> Caffeine-cache example using headers works fine:
> {code:java}
> from("timer:test2")
> .setBody(constant("VALUE_1"))
> .setHeader("CamelCaffeineAction", constant("PUT"))
> .to("caffeine-cache://cache?key=1")
> .setBody(constant("VALUE_2"))
> .setHeader("CamelCaffeineAction", constant("GET"))
> .to("caffeine-cache://cache?key=1")
> .log("Result2: ${body},
> ${header.CamelCaffeineActionHasResult}");
> {code}
> Same code using query parameter action does not work:
> {code:java}
> from("timer:test1")
> .setBody(constant("VALUE_1"))
> .to("caffeine-cache://cache?action=PUT=1")
> .setBody(constant("VALUE_2"))
> .to("caffeine-cache://cache?key=1=GET")
> .log("Result1: ${body},
> ${header.CamelCaffeineActionHasResult}");
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18131) camel-health - Add health checks for components that has extension for connectivity verification
[ https://issues.apache.org/jira/browse/CAMEL-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598164#comment-17598164 ] Claus Ibsen commented on CAMEL-18131: - - aws-s3 *DONE* > camel-health - Add health checks for components that has extension for > connectivity verification > > > Key: CAMEL-18131 > URL: https://issues.apache.org/jira/browse/CAMEL-18131 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Rhuan Rocha >Priority: Major > Fix For: 3.19.0 > > > A number of components have the old component extension verification (see > aws-s3) - we can migrate that into health-checks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18444) Caffeine-cache query parameter action does not work
Marat Gubaidullin created CAMEL-18444:
-
Summary: Caffeine-cache query parameter action does not work
Key: CAMEL-18444
URL: https://issues.apache.org/jira/browse/CAMEL-18444
Project: Camel
Issue Type: Bug
Components: camel-caffeine
Affects Versions: 3.18.1
Reporter: Marat Gubaidullin
Caffeine-cache example using headers works fine:
{code:java}
from("timer:test2")
.setBody(constant("VALUE_1"))
.setHeader("CamelCaffeineAction", constant("PUT"))
.to("caffeine-cache://cache?key=1")
.setBody(constant("VALUE_2"))
.setHeader("CamelCaffeineAction", constant("GET"))
.to("caffeine-cache://cache?key=1")
.log("Result2: ${body},
${header.CamelCaffeineActionHasResult}");
{code}
Same code using query parameter action does not work:
{code:java}
from("timer:test1")
.setBody(constant("VALUE_1"))
.to("caffeine-cache://cache?action=PUT=1")
.setBody(constant("VALUE_2"))
.to("caffeine-cache://cache?key=1=GET")
.log("Result1: ${body},
${header.CamelCaffeineActionHasResult}");
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18442) camel-github - Github commit consumer does not work
[
https://issues.apache.org/jira/browse/CAMEL-18442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18442:
Summary: camel-github - Github commit consumer does not work (was: Github
commit consumer does not work)
> camel-github - Github commit consumer does not work
> ---
>
> Key: CAMEL-18442
> URL: https://issues.apache.org/jira/browse/CAMEL-18442
> Project: Camel
> Issue Type: Bug
> Components: camel-github
>Affects Versions: 3.18.1
>Reporter: Marat Gubaidullin
>Priority: Major
> Fix For: 3.18.2, 3.19.0
>
>
> Try to execute github commit polling
> {code:java}
> from("github://commit/main?" +
> "repoOwner=YOUR_OWNER" +
> "=YOUR_REPO" +
> "=5000" +
> "=last" +
> "=true" +
> "=YOUR_TOKEN")
> .log("${body}");
> {code}
> Commit something to repo. As the result you'll have `null`.
> In case `startingSha=beginning` all previous commits retrieved but new
> commits won't be pulled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18442) Github commit consumer does not work
[
https://issues.apache.org/jira/browse/CAMEL-18442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18442:
Fix Version/s: 3.18.2
3.19.0
> Github commit consumer does not work
>
>
> Key: CAMEL-18442
> URL: https://issues.apache.org/jira/browse/CAMEL-18442
> Project: Camel
> Issue Type: Bug
> Components: camel-github
>Affects Versions: 3.18.1
>Reporter: Marat Gubaidullin
>Priority: Major
> Fix For: 3.18.2, 3.19.0
>
>
> Try to execute github commit polling
> {code:java}
> from("github://commit/main?" +
> "repoOwner=YOUR_OWNER" +
> "=YOUR_REPO" +
> "=5000" +
> "=last" +
> "=true" +
> "=YOUR_TOKEN")
> .log("${body}");
> {code}
> Commit something to repo. As the result you'll have `null`.
> In case `startingSha=beginning` all previous commits retrieved but new
> commits won't be pulled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18443) Problem using AdviceWith on routes with try-catch-finally
[
https://issues.apache.org/jira/browse/CAMEL-18443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18443:
Priority: Minor (was: Major)
> Problem using AdviceWith on routes with try-catch-finally
> -
>
> Key: CAMEL-18443
> URL: https://issues.apache.org/jira/browse/CAMEL-18443
> Project: Camel
> Issue Type: Bug
> Components: camel-test
>Affects Versions: 3.18.1
>Reporter: Lars Haugaard Kristensen
>Priority: Minor
>
> When upgrading to 3.18.1 I see a problem with some of my project's existing
> tests that break. I've isolated the problem to tests that use AdviceWith on
> routes that make use of try-catch-finally.
> Here is a test that succeeds in 3.18.0 but fails in 3.18.1:
> {code:java}
> import static org.apache.camel.builder.AdviceWith.adviceWith;
> import org.apache.camel.RoutesBuilder;
> import org.apache.camel.builder.RouteBuilder;
> import org.apache.camel.test.junit5.CamelTestSupport;
> import org.junit.jupiter.api.Test;
> public class TryCatchFinallyTest extends CamelTestSupport {
> @Test
> public void tryCatchFinallyUsingAdviceWith() throws Exception {
> adviceWith(context, "my-route", a ->
> a.weaveById("replace-me")
> .replace()
> .to("mock:replaced")
> );
> context.start();
> }
>
> @Override
> public boolean isUseAdviceWith() {
> return true;
> }
>
> @Override
> protected RoutesBuilder createRouteBuilder() {
> return new RouteBuilder() {
> @Override
> public void configure() {
> from("direct:start")
> .routeId("my-route")
> .doTry()
> .log("try")
> .to("mock:replace-me").id("replace-me")
> .doCatch(Exception.class)
> .log("catch")
> .doFinally()
> .log("finally")
> .end();
> }
> };
> }
>
> } {code}
> The stack trace:
> {noformat}
> Failed to create route my-route at: >>> DoTry[[Log[try], To[mock:replaced],
> DoCatch[ [class java.lang.Exception] -> [Log[catch]]],
> DoFinally[[Log[finally] <<< in route: Route(my-route)[From[direct:start]
> -> [DoTry[[Log[try], To[m... because of Multiple finally clauses added:
> DoFinally[[Log[finally]]] and DoFinally[[Log[finally]]]
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> my-route at: >>> DoTry[[Log[try], To[mock:replaced], DoCatch[ [class
> java.lang.Exception] -> [Log[catch]]], DoFinally[[Log[finally] <<< in
> route: Route(my-route)[From[direct:start] -> [DoTry[[Log[try], To[m...
> because of Multiple finally clauses added: DoFinally[[Log[finally]]] and
> DoFinally[[Log[finally]]]
> at
> app//org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:240)
> at
> app//org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:74)
> at
> app//org.apache.camel.impl.DefaultModelReifierFactory.createRoute(DefaultModelReifierFactory.java:49)
> at
> app//org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:862)
> at
> app//org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:750)
> at
> app//org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2947)
> at
> app//org.apache.camel.support.service.BaseService.init(BaseService.java:83)
> at
> app//org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2630)
> at
> app//org.apache.camel.support.service.BaseService.start(BaseService.java:111)
> at
> app//org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2649)
> at
> app//org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:262)
> at
> app//TryCatchFinallyTest.tryCatchFinallyUsingAdviceWith(TryCatchFinallyTest.java:18)
> at
> java.base@11.0.16/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base@11.0.16/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base@11.0.16/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base@11.0.16/java.lang.reflect.Method.invoke(Method.java:566)
> at
> app//org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:725)
> at
> app//org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
> at
> app//org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
> at
> app//org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
> at
>
[jira] [Created] (CAMEL-18443) Problem using AdviceWith on routes with try-catch-finally
Lars Haugaard Kristensen created CAMEL-18443:
Summary: Problem using AdviceWith on routes with try-catch-finally
Key: CAMEL-18443
URL: https://issues.apache.org/jira/browse/CAMEL-18443
Project: Camel
Issue Type: Bug
Components: camel-test
Affects Versions: 3.18.1
Reporter: Lars Haugaard Kristensen
When upgrading to 3.18.1 I see a problem with some of my project's existing
tests that break. I've isolated the problem to tests that use AdviceWith on
routes that make use of try-catch-finally.
Here is a test that succeeds in 3.18.0 but fails in 3.18.1:
{code:java}
import static org.apache.camel.builder.AdviceWith.adviceWith;
import org.apache.camel.RoutesBuilder;
import org.apache.camel.builder.RouteBuilder;
import org.apache.camel.test.junit5.CamelTestSupport;
import org.junit.jupiter.api.Test;
public class TryCatchFinallyTest extends CamelTestSupport {
@Test
public void tryCatchFinallyUsingAdviceWith() throws Exception {
adviceWith(context, "my-route", a ->
a.weaveById("replace-me")
.replace()
.to("mock:replaced")
);
context.start();
}
@Override
public boolean isUseAdviceWith() {
return true;
}
@Override
protected RoutesBuilder createRouteBuilder() {
return new RouteBuilder() {
@Override
public void configure() {
from("direct:start")
.routeId("my-route")
.doTry()
.log("try")
.to("mock:replace-me").id("replace-me")
.doCatch(Exception.class)
.log("catch")
.doFinally()
.log("finally")
.end();
}
};
}
} {code}
The stack trace:
{noformat}
Failed to create route my-route at: >>> DoTry[[Log[try], To[mock:replaced],
DoCatch[ [class java.lang.Exception] -> [Log[catch]]],
DoFinally[[Log[finally] <<< in route: Route(my-route)[From[direct:start] ->
[DoTry[[Log[try], To[m... because of Multiple finally clauses added:
DoFinally[[Log[finally]]] and DoFinally[[Log[finally]]]
org.apache.camel.FailedToCreateRouteException: Failed to create route my-route
at: >>> DoTry[[Log[try], To[mock:replaced], DoCatch[ [class
java.lang.Exception] -> [Log[catch]]], DoFinally[[Log[finally] <<< in
route: Route(my-route)[From[direct:start] -> [DoTry[[Log[try], To[m... because
of Multiple finally clauses added: DoFinally[[Log[finally]]] and
DoFinally[[Log[finally]]]
at
app//org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:240)
at
app//org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:74)
at
app//org.apache.camel.impl.DefaultModelReifierFactory.createRoute(DefaultModelReifierFactory.java:49)
at
app//org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:862)
at
app//org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:750)
at
app//org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2947)
at
app//org.apache.camel.support.service.BaseService.init(BaseService.java:83)
at
app//org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2630)
at
app//org.apache.camel.support.service.BaseService.start(BaseService.java:111)
at
app//org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2649)
at
app//org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:262)
at
app//TryCatchFinallyTest.tryCatchFinallyUsingAdviceWith(TryCatchFinallyTest.java:18)
at
java.base@11.0.16/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
java.base@11.0.16/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base@11.0.16/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base@11.0.16/java.lang.reflect.Method.invoke(Method.java:566)
at
app//org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:725)
at
app//org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
at
app//org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
at
app//org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
at
app//org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
at
app//org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:84)
at
app//org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(ExecutableInvoker.java:115)
at
[jira] [Created] (CAMEL-18442) Github commit consumer does not work
Marat Gubaidullin created CAMEL-18442:
-
Summary: Github commit consumer does not work
Key: CAMEL-18442
URL: https://issues.apache.org/jira/browse/CAMEL-18442
Project: Camel
Issue Type: Bug
Components: camel-github
Affects Versions: 3.18.1
Reporter: Marat Gubaidullin
Try to execute github commit polling
{code:java}
from("github://commit/main?" +
"repoOwner=YOUR_OWNER" +
"=YOUR_REPO" +
"=5000" +
"=last" +
"=true" +
"=YOUR_TOKEN")
.log("${body}");
{code}
Commit something to repo. As the result you'll have `null`.
In case `startingSha=beginning` all previous commits retrieved but new commits
won't be pulled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-18438) camel-main - Add option to configure context description
[ https://issues.apache.org/jira/browse/CAMEL-18438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-18438: --- Assignee: Claus Ibsen > camel-main - Add option to configure context description > > > Key: CAMEL-18438 > URL: https://issues.apache.org/jira/browse/CAMEL-18438 > Project: Camel > Issue Type: Improvement > Components: camel-main >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.19.0 > > > You can set name via > camel.main.name = foo > But we should have a description so you can do > camel.main.name = account-to-payroll > camel.main.description = Reconciles the bank accounts with the payroll system > And we can show the description in tooling that can allow users to quicker > understand what this camel app does -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18439) camel-github - Consumer that polls commits crashed when repository has more than 100 commits
[
https://issues.apache.org/jira/browse/CAMEL-18439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18439.
-
Resolution: Fixed
> camel-github - Consumer that polls commits crashed when repository has more
> than 100 commits
>
>
> Key: CAMEL-18439
> URL: https://issues.apache.org/jira/browse/CAMEL-18439
> Project: Camel
> Issue Type: Bug
> Components: camel-github
>Affects Versions: 3.18.1
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.18.2, 3.19.0
>
>
> Following code:
> {code:java}
> from("github://commit/main?" +
> "repoOwner=apache" +
> "=camel-karavan" +
> "=YOUR_TOKEN")
> .log("${body}");
> {code}
> Throws
> {code:java}
> java.lang.IllegalStateException: Queue full
> at java.base/java.util.AbstractQueue.add(AbstractQueue.java:98)
> at
> java.base/java.util.concurrent.ArrayBlockingQueue.add(ArrayBlockingQueue.java:326)
> at
> org.apache.camel.component.github.consumer.CommitConsumer.doStart(CommitConsumer.java:80)
> {code}
> here
> https://github.com/apache/camel/blob/884c7eae744bfe8bf074751ef2863dbf6729ed0c/components/camel-github/src/main/java/org/apache/camel/component/github/consumer/CommitConsumer.java#L80
> because of queue size = 100
> {code:java}
> private final Queue commitHashes = new ArrayBlockingQueue<>(100);
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18406) camel-jbang - CLI to control routes such as suspend/resume/stats
[ https://issues.apache.org/jira/browse/CAMEL-18406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18406. - Resolution: Fixed > camel-jbang - CLI to control routes such as suspend/resume/stats > > > Key: CAMEL-18406 > URL: https://issues.apache.org/jira/browse/CAMEL-18406 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > It would be good if we could > - control routes such as start/stop/suspend/resume *DONE* > - context statistics *DONE* > - route statistics so you can see their state, number of messages processed > etc *DONE* > - show health check status as well in the get commands *DONE* > - show camel and runtime version *DONE* > - show memory usage *DONE* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18439) camel-github - Consumer that polls commits crashed when repository has more than 100 commits
[
https://issues.apache.org/jira/browse/CAMEL-18439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-18439:
---
Assignee: Claus Ibsen
> camel-github - Consumer that polls commits crashed when repository has more
> than 100 commits
>
>
> Key: CAMEL-18439
> URL: https://issues.apache.org/jira/browse/CAMEL-18439
> Project: Camel
> Issue Type: Bug
> Components: camel-github
>Affects Versions: 3.18.1
>Reporter: Marat Gubaidullin
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.18.2, 3.19.0
>
>
> Following code:
> {code:java}
> from("github://commit/main?" +
> "repoOwner=apache" +
> "=camel-karavan" +
> "=YOUR_TOKEN")
> .log("${body}");
> {code}
> Throws
> {code:java}
> java.lang.IllegalStateException: Queue full
> at java.base/java.util.AbstractQueue.add(AbstractQueue.java:98)
> at
> java.base/java.util.concurrent.ArrayBlockingQueue.add(ArrayBlockingQueue.java:326)
> at
> org.apache.camel.component.github.consumer.CommitConsumer.doStart(CommitConsumer.java:80)
> {code}
> here
> https://github.com/apache/camel/blob/884c7eae744bfe8bf074751ef2863dbf6729ed0c/components/camel-github/src/main/java/org/apache/camel/component/github/consumer/CommitConsumer.java#L80
> because of queue size = 100
> {code:java}
> private final Queue commitHashes = new ArrayBlockingQueue<>(100);
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18406) camel-jbang - CLI to control routes such as suspend/resume/stats
[ https://issues.apache.org/jira/browse/CAMEL-18406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597366#comment-17597366 ] Claus Ibsen edited comment on CAMEL-18406 at 8/30/22 10:38 AM: --- - camel run * (name should be first founds DSL file) *DONE* - camel run foo.java (name should be foo) *DONE* - camel get (use name) *DONE* - pattern to support comma (foo,bar) *DONE* - camel cmd -all flag for all routes so you can quickly stop all of them, or start all of them *DONE* - update documentation *DONE* was (Author: davsclaus): - camel run * (name should be first founds DSL file) *DONE* - camel run foo.java (name should be foo) *DONE* - camel get (use name) *DONE* - pattern to support comma (foo,bar) *DONE* - camel cmd -all flag for all routes so you can quickly stop all of them, or start all of them *DONE* - update documentation > camel-jbang - CLI to control routes such as suspend/resume/stats > > > Key: CAMEL-18406 > URL: https://issues.apache.org/jira/browse/CAMEL-18406 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > It would be good if we could > - control routes such as start/stop/suspend/resume *DONE* > - context statistics *DONE* > - route statistics so you can see their state, number of messages processed > etc *DONE* > - show health check status as well in the get commands *DONE* > - show camel and runtime version *DONE* > - show memory usage *DONE* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18417) StopWatch may provide incorrect measurements
[ https://issues.apache.org/jira/browse/CAMEL-18417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-18417. -- Resolution: Fixed Closing as it is fixed. > StopWatch may provide incorrect measurements > > > Key: CAMEL-18417 > URL: https://issues.apache.org/jira/browse/CAMEL-18417 > Project: Camel > Issue Type: Improvement >Affects Versions: 3.14.5, 3.18.1 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Minor > Fix For: 3.19.0 > > > The StopWatch in camel-util is based on the System clock and uses it to > calculate durations. However, the system clock is not an appropriate source > for measuring durations because it can go back in time or have time leaps > that do not reflect reality (ex.: when changing standard time to daylight > saving and vice versa, when having micro adjustments due to NTP > synchronization, when the date is manually changed, etc). > > We should probably investigating replacing the source with Java's high > resolution timer or (potentially) the Duration class. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18432) DockerConfiguration malformerd UriPath for variable operation
[ https://issues.apache.org/jira/browse/CAMEL-18432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-18432: - Affects Version/s: 3.18.1 3.14.5 > DockerConfiguration malformerd UriPath for variable operation > - > > Key: CAMEL-18432 > URL: https://issues.apache.org/jira/browse/CAMEL-18432 > Project: Camel > Issue Type: Bug > Components: camel-docker >Affects Versions: 3.14.5, 3.17.0, 3.18.1 > Environment: IDE: eclipse > OS: linux Debian 11 > Camel 3.17.0 >Reporter: Marco Pernigo >Assignee: Otavio Rodolfo Piske >Priority: Minor > Fix For: 3.14.6, 3.18.2, 3.19.0 > > Attachments: Screenshot from 2022-08-26 13-56-37.png > > Original Estimate: 1h > Remaining Estimate: 1h > > In DockerConfiguration.java, the enums passed to the UriPath annotation for > the private variable operation is malformed: in the string concatenation are > missing commans on the new lines. > Furthermore, the following three operations are missing: > networkconnect,networkcreate,networkremove. > > Functionally it works, but the Eclipse IDE and the documentation on the > official site report errors > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18432) DockerConfiguration malformerd UriPath for variable operation
[ https://issues.apache.org/jira/browse/CAMEL-18432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-18432. -- Fix Version/s: 3.14.6 Resolution: Fixed Backported to 3.14 and 3.18 branches. Closing ... > DockerConfiguration malformerd UriPath for variable operation > - > > Key: CAMEL-18432 > URL: https://issues.apache.org/jira/browse/CAMEL-18432 > Project: Camel > Issue Type: Bug > Components: camel-docker >Affects Versions: 3.17.0 > Environment: IDE: eclipse > OS: linux Debian 11 > Camel 3.17.0 >Reporter: Marco Pernigo >Assignee: Otavio Rodolfo Piske >Priority: Minor > Fix For: 3.14.6, 3.18.2, 3.19.0 > > Attachments: Screenshot from 2022-08-26 13-56-37.png > > Original Estimate: 1h > Remaining Estimate: 1h > > In DockerConfiguration.java, the enums passed to the UriPath annotation for > the private variable operation is malformed: in the string concatenation are > missing commans on the new lines. > Furthermore, the following three operations are missing: > networkconnect,networkcreate,networkremove. > > Functionally it works, but the Eclipse IDE and the documentation on the > official site report errors > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18406) camel-jbang - CLI to control routes such as suspend/resume/stats
[ https://issues.apache.org/jira/browse/CAMEL-18406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18406: Description: It would be good if we could - control routes such as start/stop/suspend/resume *DONE* - context statistics *DONE* - route statistics so you can see their state, number of messages processed etc *DONE* - show health check status as well in the get commands *DONE* - show camel and runtime version *DONE* - show memory usage *DONE* was: It would be good if we could - control routes such as start/stop/suspend/resume - context statistics *DONE* - route statistics so you can see their state, number of messages processed etc *DONE* - show health check status as well in the get commands *DONE* - show camel and runtime version *DONE* - show memory usage *DONE* > camel-jbang - CLI to control routes such as suspend/resume/stats > > > Key: CAMEL-18406 > URL: https://issues.apache.org/jira/browse/CAMEL-18406 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > It would be good if we could > - control routes such as start/stop/suspend/resume *DONE* > - context statistics *DONE* > - route statistics so you can see their state, number of messages processed > etc *DONE* > - show health check status as well in the get commands *DONE* > - show camel and runtime version *DONE* > - show memory usage *DONE* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18406) camel-jbang - CLI to control routes such as suspend/resume/stats
[ https://issues.apache.org/jira/browse/CAMEL-18406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597366#comment-17597366 ] Claus Ibsen edited comment on CAMEL-18406 at 8/30/22 9:08 AM: -- - camel run * (name should be first founds DSL file) *DONE* - camel run foo.java (name should be foo) *DONE* - camel get (use name) *DONE* - pattern to support comma (foo,bar) *DONE* - camel cmd -all flag for all routes so you can quickly stop all of them, or start all of them *DONE* - update documentation was (Author: davsclaus): - camel run * (name should be first founds DSL file) - camel run foo.java (name should be foo) - camel get (use name) - pattern to support comma (foo,bar) *DONE* - camel cmd -all flag for all routes so you can quickly stop all of them, or start all of them *DONE* - update documentation > camel-jbang - CLI to control routes such as suspend/resume/stats > > > Key: CAMEL-18406 > URL: https://issues.apache.org/jira/browse/CAMEL-18406 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > It would be good if we could > - control routes such as start/stop/suspend/resume > - context statistics *DONE* > - route statistics so you can see their state, number of messages processed > etc *DONE* > - show health check status as well in the get commands *DONE* > - show camel and runtime version *DONE* > - show memory usage *DONE* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18440) camel-core - Stopping routes via management APIs should not make health-check fail
Claus Ibsen created CAMEL-18440:
---
Summary: camel-core - Stopping routes via management APIs should
not make health-check fail
Key: CAMEL-18440
URL: https://issues.apache.org/jira/browse/CAMEL-18440
Project: Camel
Issue Type: Improvement
Components: camel-core, jmx
Reporter: Claus Ibsen
Fix For: 3.19.0
If you stop routes via JMX or some other management APIs then the health-check
is reporting this as down.
Here we have stopped the chuck app and 0 out of 3 routes is running and the
ready is 0/6 (eg down)
{code}
PID NAMECAMELPLATFORM READY STATUSAGEROUTE
TOTAL FAILED INFLIGHT SINCE-LAST
64673 bar.yaml3.19.0-SNAPSHOT JBang 1/1 Running 28m11s1/1
1617 0 0 0s
64686 chuck.yaml 3.19.0-SNAPSHOT JBang 0/6 Running 28m9s0/3
224 2 0 15m25s
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18425) camel-cli - Make regular Camel applications work with Camel CLI
[ https://issues.apache.org/jira/browse/CAMEL-18425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597644#comment-17597644 ] Vinod Pahuja commented on CAMEL-18425: -- Is it wise to abstract camel-cli to a parent dependency having implementation using different runtime ? like one we already have using jbang and another could be implemented using spring-boot-cli I tried to run a standalone camel route using spring-boot-cli and it just works fine but still need some operational fine tuning. https://github.com/apache/camel-spring-boot-examples/pull/79 > camel-cli - Make regular Camel applications work with Camel CLI > --- > > Key: CAMEL-18425 > URL: https://issues.apache.org/jira/browse/CAMEL-18425 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > The Camel CLI has commands to get status and start/stop camel applications, > but its limited to camel-jbang based integrations. > We can look at having a camel-cli dependency that you can add to > camel-spring-boot or camel-main etc when you want your app to be able to work > with the Camel CLI. > This dependency should only be used for development purposes. > You could then have a mvn spring-boot:run app and then also a camel-jbang app > that work together and you need to control them via the camel cli, to have a > better UX. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18406) camel-jbang - CLI to control routes such as suspend/resume/stats
[ https://issues.apache.org/jira/browse/CAMEL-18406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597366#comment-17597366 ] Claus Ibsen edited comment on CAMEL-18406 at 8/30/22 7:47 AM: -- - camel run * (name should be first founds DSL file) - camel run foo.java (name should be foo) - camel get (use name) - pattern to support comma (foo,bar) *DONE* - camel cmd -all flag for all routes so you can quickly stop all of them, or start all of them *DONE* - update documentation was (Author: davsclaus): - camel run * (name should be first founds DSL file) - camel run foo.java (name should be foo) - camel get (use name) - pattern to support comma (foo,bar) - camel cmd -all flag for all routes so you can quickly stop all of them, or start all of them *DONE* - update documentation > camel-jbang - CLI to control routes such as suspend/resume/stats > > > Key: CAMEL-18406 > URL: https://issues.apache.org/jira/browse/CAMEL-18406 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > It would be good if we could > - control routes such as start/stop/suspend/resume > - context statistics *DONE* > - route statistics so you can see their state, number of messages processed > etc *DONE* > - show health check status as well in the get commands *DONE* > - show camel and runtime version *DONE* > - show memory usage *DONE* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18406) camel-jbang - CLI to control routes such as suspend/resume/stats
[ https://issues.apache.org/jira/browse/CAMEL-18406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597366#comment-17597366 ] Claus Ibsen edited comment on CAMEL-18406 at 8/30/22 7:36 AM: -- - camel run * (name should be first founds DSL file) - camel run foo.java (name should be foo) - camel get (use name) - pattern to support comma (foo,bar) - camel cmd -all flag for all routes so you can quickly stop all of them, or start all of them *DONE* - update documentation was (Author: davsclaus): - camel run * (name should be first founds DSL file) - camel run foo.java (name should be foo) - camel get (use name) - pattern to support comma (foo,bar) - camel cmd -all flag for all routes so you can quickly stop all of them, or start all of them *DONE* > camel-jbang - CLI to control routes such as suspend/resume/stats > > > Key: CAMEL-18406 > URL: https://issues.apache.org/jira/browse/CAMEL-18406 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > It would be good if we could > - control routes such as start/stop/suspend/resume > - context statistics *DONE* > - route statistics so you can see their state, number of messages processed > etc *DONE* > - show health check status as well in the get commands *DONE* > - show camel and runtime version *DONE* > - show memory usage *DONE* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18406) camel-jbang - CLI to control routes such as suspend/resume/stats
[ https://issues.apache.org/jira/browse/CAMEL-18406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597366#comment-17597366 ] Claus Ibsen edited comment on CAMEL-18406 at 8/30/22 7:35 AM: -- - camel run * (name should be first founds DSL file) - camel run foo.java (name should be foo) - camel get (use name) - pattern to support comma (foo,bar) - camel cmd -all flag for all routes so you can quickly stop all of them, or start all of them *DONE* was (Author: davsclaus): - camel run * (name should be first founds DSL file) - camel run foo.java (name should be foo) - camel get (use name) - pattern to support comma (foo,bar) - camel cmd -all flag for all routes so you can quickly stop all of them, or start all of them > camel-jbang - CLI to control routes such as suspend/resume/stats > > > Key: CAMEL-18406 > URL: https://issues.apache.org/jira/browse/CAMEL-18406 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > It would be good if we could > - control routes such as start/stop/suspend/resume > - context statistics *DONE* > - route statistics so you can see their state, number of messages processed > etc *DONE* > - show health check status as well in the get commands *DONE* > - show camel and runtime version *DONE* > - show memory usage *DONE* -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18431) camel-spring-security feature
[
https://issues.apache.org/jira/browse/CAMEL-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597569#comment-17597569
]
Vincent commented on CAMEL-18431:
-
Hello,
Thank you for your answer.
I asked to the user mailing list but I haven't received an answer yet.
> camel-spring-security feature
> -
>
> Key: CAMEL-18431
> URL: https://issues.apache.org/jira/browse/CAMEL-18431
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-security
>Affects Versions: 3.15.0
>Reporter: Vincent
>Priority: Major
>
> Hi,
> I would like to install camel-spring-security in my Karaf 4.3.6.
>
> It seems that feature _camel-spring-security_ has disappeared in version
> 3.15.0 :
> https://repo1.maven.org/maven2/org/apache/camel/karaf/apache-camel/3.15.0/apache-camel-3.15.0-features.xml.
> So I tried to install it without feature :
> {code:java}
> feature:install spring-security
> install -s mvn:org.apache.camel/camel-spring-security/3.15.0 {code}
> But Karaf gives me the following error :
> {code:java}
> Error executing command: Error installing bundles:
> Unable to start bundle mvn:org.apache.camel/camel-spring-security/3.15.0:
> org.osgi.framework.BundleException: Unable to resolve
> org.apache.camel.camel-spring-security [263](R 263.0): missing requirement
> [org.apache.camel.camel-spring-security [263](R 263.0)] osgi.wiring.package;
> (&(osgi.wiring.package=org.springframework.security.access)(version>=4.0.0)(!(version>=5.0.0)))
> Unresolved requirements: [[org.apache.camel.camel-spring-security [263](R
> 263.0)] osgi.wiring.package;
> (&(osgi.wiring.package=org.springframework.security.access)(version>=4.0.0)(!(version>=5.0.0)))]{code}
> When I look at the pom, I see that camel-spring-security depends on
> spring-core in version 5.3.15 :
> {code:java}
>
>org.springframework
>spring-core
>5.3.15
>compile
> {code}
> But when I look at the Manifest, it requires the following version :
> {code:java}
> org.springframework.security.core.
> context;version="[4,5)" {code}
> All 4.x.y version but not 5.x.y version.
>
> Do you have an idea?
>
> Thank you for your help
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18405) camel-karaf - Camel-file ResumeAware
[ https://issues.apache.org/jira/browse/CAMEL-18405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17597561#comment-17597561 ] TARTIERE commented on CAMEL-18405: -- So what can we do or modify to have a working version? > camel-karaf - Camel-file ResumeAware > > > Key: CAMEL-18405 > URL: https://issues.apache.org/jira/browse/CAMEL-18405 > Project: Camel > Issue Type: Bug >Affects Versions: 3.18.1 >Reporter: TARTIERE >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.18.2 > > > Unable to start application with routes listening for files. > java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: > org/apache/camel/resume/ResumeAware > at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:?] > at java.util.concurrent.FutureTask.get(FutureTask.java:191) ~[?:?] > at > java.util.concurrent.AbstractExecutorService.doInvokeAny(AbstractExecutorService.java:199) > ~[?:?] > at > java.util.concurrent.AbstractExecutorService.invokeAny(AbstractExecutorService.java:230) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$4.call(ScheduledExecutorServiceWrapper.java:185) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper$15.call(ScheduledExecutorServiceWrapper.java:446) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.RWLock.runReadOperation(RWLock.java:33) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.runUnlessShutdown(ScheduledExecutorServiceWrapper.java:443) > ~[?:?] > at > org.apache.aries.blueprint.utils.threading.ScheduledExecutorServiceWrapper.invokeAny(ScheduledExecutorServiceWrapper.java:180) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListener(BlueprintEventDispatcher.java:195) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.callListeners(BlueprintEventDispatcher.java:178) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintEventDispatcher.blueprintEvent(BlueprintEventDispatcher.java:133) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:447) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:298) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:335) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:288) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:284) > ~[?:?] > at > org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:274) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463) > ~[?:?] > at > org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422) > ~[?:?] > at > org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1180) > ~[?:?] > at > org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730) > ~[?:?] > at > org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485) > ~[?:?] > at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4817) > ~[?:?] > at org.apache.felix.framework.Felix.startBundle(Felix.java:2336) ~[?:?] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?] > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) ~[?:?] > at > org.apache.karaf.features.internal.service.BundleInstallSupportImpl.startBundle(BundleInstallSupportImpl.java:165) > ~[?:?] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1160) > ~[?:?] > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:1041) > ~[?:?] > at > org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1069) > ~[?:?] > at >
