[jira] [Created] (CAMEL-19366) camel-core - Trigger reload via dev console make it async
Claus Ibsen created CAMEL-19366: --- Summary: camel-core - Trigger reload via dev console make it async Key: CAMEL-19366 URL: https://issues.apache.org/jira/browse/CAMEL-19366 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.21.0, 4.0-RC1, 4.0 If triggering reload on-demand then it can potentially take some time and you just want to trigger the reload, and let Camel do this in the background. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19364) Rest-openapi: lookup mechanism does not work after changes from Camel-18963
[
https://issues.apache.org/jira/browse/CAMEL-19364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Ondrusek reassigned CAMEL-19364:
-
Assignee: Jiri Ondrusek
> Rest-openapi: lookup mechanism does not work after changes from Camel-18963
> ---
>
> Key: CAMEL-19364
> URL: https://issues.apache.org/jira/browse/CAMEL-19364
> Project: Camel
> Issue Type: Bug
> Components: camel-rest-openapi
>Affects Versions: 4.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Major
>
> I was trying to synchronize camel-quarkus with current Camel from `main`
> branch.
> I noticed failures related to fix
> [https://github.com/apache/camel/commit/e2ad230d86fcbbc1e3c4ad5a9daf01aa3127eb42]
> in the Camel-rest-openapi component.
> According to the doc, the url in component can be specified i.g.
> "classpath:...", "bean:...". At least these 2 options does not work.
> It can be verified by a simple test:
> {code:java}
> @Test
> public void testClasspath() throws Exception{
> Producer p =
> context().getEndpoint("rest-openapi:addPet?specificationUri=classpath:openapi.json").createProducer();
> Assertions.assertNotNull(p);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19367) CamelEvent.RouteCompleted
Pasquale Congiusti created CAMEL-19367: -- Summary: CamelEvent.RouteCompleted Key: CAMEL-19367 URL: https://issues.apache.org/jira/browse/CAMEL-19367 Project: Camel Issue Type: Improvement Affects Versions: 3.20.4 Reporter: Pasquale Congiusti Hello team. While troubleshooting this Camel K issue [1], I've realized we're missing some route event that can tell us that the route was completed. Do you think it would be possible to include the `RouteCompleted` event? From what I can tell, it would be an event generated once all the steps of the route are completed. Without that, we don't know exactly when a route is terminated and it's fine to gracefully stop it. Any feedback or possible workaround is appreciated as well, thanks! [1] https://github.com/apache/camel-k/issues/4343 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19366) camel-core - Trigger reload via dev console make it async
[ https://issues.apache.org/jira/browse/CAMEL-19366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19366. - Resolution: Fixed > camel-core - Trigger reload via dev console make it async > - > > Key: CAMEL-19366 > URL: https://issues.apache.org/jira/browse/CAMEL-19366 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.20.5, 3.21.0, 4.0-RC1, 4.0 > > > If triggering reload on-demand then it can potentially take some time and you > just want to trigger the reload, and let Camel do this in the background. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19366) camel-core - Trigger reload via dev console make it async
[ https://issues.apache.org/jira/browse/CAMEL-19366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19366: Fix Version/s: 3.20.5 > camel-core - Trigger reload via dev console make it async > - > > Key: CAMEL-19366 > URL: https://issues.apache.org/jira/browse/CAMEL-19366 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.20.5, 3.21.0, 4.0-RC1, 4.0 > > > If triggering reload on-demand then it can potentially take some time and you > just want to trigger the reload, and let Camel do this in the background. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19367) CamelEvent.RouteCompleted
[ https://issues.apache.org/jira/browse/CAMEL-19367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723840#comment-17723840 ] Claus Ibsen commented on CAMEL-19367: - route events are just about routes added / removed etc. the exchange events are for messages being routed inside camel. There is already events when an exchange is complete. In your example the split create sub-exchanges, and you can see the last exchange completed in the events list has exchange id that was the first exchange. So you could either capture the created exchange event, and the exchange id listen for completed events until you have a matching exchange id or check inflight registry if the route has 0, or camel context has 0 in general (I assume you want to shutdown all of Camel) so in the listener you can wait for completed exchanges and check inflight registry if its zero (however I need to check if you received the event before camel decrements the inflight counter, as otherwise it would be 1) > CamelEvent.RouteCompleted > - > > Key: CAMEL-19367 > URL: https://issues.apache.org/jira/browse/CAMEL-19367 > Project: Camel > Issue Type: Improvement >Affects Versions: 3.20.4 >Reporter: Pasquale Congiusti >Priority: Major > > Hello team. While troubleshooting this Camel K issue [1], I've realized we're > missing some route event that can tell us that the route was completed. Do > you think it would be possible to include the `RouteCompleted` event? From > what I can tell, it would be an event generated once all the steps of the > route are completed. Without that, we don't know exactly when a route is > terminated and it's fine to gracefully stop it. > Any feedback or possible workaround is appreciated as well, thanks! > [1] https://github.com/apache/camel-k/issues/4343 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19367) CamelEvent.RouteCompleted
[ https://issues.apache.org/jira/browse/CAMEL-19367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723842#comment-17723842 ] Claus Ibsen commented on CAMEL-19367: - As things can potentially be processed out of order, then you can check for inflight = 0 and exchange completed | failed > CamelEvent.RouteCompleted > - > > Key: CAMEL-19367 > URL: https://issues.apache.org/jira/browse/CAMEL-19367 > Project: Camel > Issue Type: Improvement >Affects Versions: 3.20.4 >Reporter: Pasquale Congiusti >Priority: Major > > Hello team. While troubleshooting this Camel K issue [1], I've realized we're > missing some route event that can tell us that the route was completed. Do > you think it would be possible to include the `RouteCompleted` event? From > what I can tell, it would be an event generated once all the steps of the > route are completed. Without that, we don't know exactly when a route is > terminated and it's fine to gracefully stop it. > Any feedback or possible workaround is appreciated as well, thanks! > [1] https://github.com/apache/camel-k/issues/4343 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19367) CamelEvent.RouteCompleted
[
https://issues.apache.org/jira/browse/CAMEL-19367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723843#comment-17723843
]
Pasquale Congiusti commented on CAMEL-19367:
Thanks [~davsclaus], yeah, considering the following example:
{code}
BA60304B47DB867- exchange created
BA60304B47DB867-0001 exchange created
BA60304B47DB867-0001 exchange sending to: mock://result
BA60304B47DB867-0001 exchange completed took: 760ms
BA60304B47DB867-0002 exchange created
BA60304B47DB867-0002 exchange sending to: mock://result
BA60304B47DB867-0002 exchange completed took: 762ms
BA60304B47DB867-0003 exchange created
BA60304B47DB867-0003 exchange sending to: mock://result
BA60304B47DB867-0003 exchange completed took: 762ms
BA60304B47DB867- exchange completed took: 763ms
{code}
I guess I can just watch for the `BA60304B47DB867- exchange
completed took: 763ms` that is when the root step is completed (which is
exactly what I need to know). It sounds fine and I'm going to test it soon to
prove it solves the original issue.
Thanks for the suggestion,
Pasquale.
> CamelEvent.RouteCompleted
> -
>
> Key: CAMEL-19367
> URL: https://issues.apache.org/jira/browse/CAMEL-19367
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 3.20.4
>Reporter: Pasquale Congiusti
>Priority: Major
>
> Hello team. While troubleshooting this Camel K issue [1], I've realized we're
> missing some route event that can tell us that the route was completed. Do
> you think it would be possible to include the `RouteCompleted` event? From
> what I can tell, it would be an event generated once all the steps of the
> route are completed. Without that, we don't know exactly when a route is
> terminated and it's fine to gracefully stop it.
> Any feedback or possible workaround is appreciated as well, thanks!
> [1] https://github.com/apache/camel-k/issues/4343
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19367) CamelEvent.RouteCompleted
[ https://issues.apache.org/jira/browse/CAMEL-19367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723845#comment-17723845 ] Pasquale Congiusti commented on CAMEL-19367: > As things can potentially be processed out of order, then you can check for > inflight = 0 and exchange completed | failed do you think that there is the possibility for BA60304B47DB867- to ends before any subroute created by the split eip? > CamelEvent.RouteCompleted > - > > Key: CAMEL-19367 > URL: https://issues.apache.org/jira/browse/CAMEL-19367 > Project: Camel > Issue Type: Improvement >Affects Versions: 3.20.4 >Reporter: Pasquale Congiusti >Priority: Major > > Hello team. While troubleshooting this Camel K issue [1], I've realized we're > missing some route event that can tell us that the route was completed. Do > you think it would be possible to include the `RouteCompleted` event? From > what I can tell, it would be an event generated once all the steps of the > route are completed. Without that, we don't know exactly when a route is > terminated and it's fine to gracefully stop it. > Any feedback or possible workaround is appreciated as well, thanks! > [1] https://github.com/apache/camel-k/issues/4343 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19367) CamelEvent.RouteCompleted
[ https://issues.apache.org/jira/browse/CAMEL-19367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723851#comment-17723851 ] Claus Ibsen commented on CAMEL-19367: - Yeah they could be out of order depending on what the end user do in the route, if an exchange is processed async, or using wireTap EIP etc. > CamelEvent.RouteCompleted > - > > Key: CAMEL-19367 > URL: https://issues.apache.org/jira/browse/CAMEL-19367 > Project: Camel > Issue Type: Improvement >Affects Versions: 3.20.4 >Reporter: Pasquale Congiusti >Priority: Major > > Hello team. While troubleshooting this Camel K issue [1], I've realized we're > missing some route event that can tell us that the route was completed. Do > you think it would be possible to include the `RouteCompleted` event? From > what I can tell, it would be an event generated once all the steps of the > route are completed. Without that, we don't know exactly when a route is > terminated and it's fine to gracefully stop it. > Any feedback or possible workaround is appreciated as well, thanks! > [1] https://github.com/apache/camel-k/issues/4343 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19368) camel-main - Auto detect custom EventNotifer from registry
Claus Ibsen created CAMEL-19368: --- Summary: camel-main - Auto detect custom EventNotifer from registry Key: CAMEL-19368 URL: https://issues.apache.org/jira/browse/CAMEL-19368 Project: Camel Issue Type: Improvement Components: camel-main Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.0-RC1, 4.0 This makes it easier to provide custom event notifiers which you can just annotate for dependency injection and auto discovered by camel like we do for other stuff -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19368) camel-main - Auto detect custom EventNotifer from registry
[ https://issues.apache.org/jira/browse/CAMEL-19368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723860#comment-17723860 ] Claus Ibsen commented on CAMEL-19368: - Also make it work via camel-jbang > camel-main - Auto detect custom EventNotifer from registry > -- > > Key: CAMEL-19368 > URL: https://issues.apache.org/jira/browse/CAMEL-19368 > Project: Camel > Issue Type: Improvement > Components: camel-main >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0-RC1, 4.0 > > > This makes it easier to provide custom event notifiers which you can just > annotate for dependency injection and auto discovered by camel like we do for > other stuff -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19367) CamelEvent.RouteCompleted
[
https://issues.apache.org/jira/browse/CAMEL-19367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723864#comment-17723864
]
Claus Ibsen commented on CAMEL-19367:
-
You can do something like
public class MyNotifier extends org.apache.camel.support.EventNotifierSupport {
public boolean isEnabled(CamelEvent event) {
return event instanceof CamelEvent.ExchangeCompletedEvent ||
event instanceof CamelEvent.ExchangeFailedEvent;
}
@Override
public void notify(CamelEvent event) throws Exception {
int size = getCamelContext().getInflightRepository().size();
System.out.println("exchange done and " + size + " inflights");
}
}
Which gives me
2023-05-18 11:15:00.403 INFO 42495 --- [tifier_Worker-1] cron.yaml:16
: Parrot
exchange done and 1 inflights
2023-05-18 11:15:00.405 INFO 42495 --- [tifier_Worker-1] cron.yaml:16
: Cockatiel
exchange done and 1 inflights
2023-05-18 11:15:00.407 INFO 42495 --- [tifier_Worker-1] cron.yaml:16
: Pigeon
exchange done and 1 inflights
2023-05-18 11:15:00.408 INFO 42495 --- [tifier_Worker-1] cron.yaml:17
: [Parrot, Cockatiel, Pigeon]
2023-05-18 11:15:00.410 INFO 42495 --- [tifier_Worker-1] cron.yaml:18
: end
exchange done and 0 inflights
> CamelEvent.RouteCompleted
> -
>
> Key: CAMEL-19367
> URL: https://issues.apache.org/jira/browse/CAMEL-19367
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 3.20.4
>Reporter: Pasquale Congiusti
>Priority: Major
>
> Hello team. While troubleshooting this Camel K issue [1], I've realized we're
> missing some route event that can tell us that the route was completed. Do
> you think it would be possible to include the `RouteCompleted` event? From
> what I can tell, it would be an event generated once all the steps of the
> route are completed. Without that, we don't know exactly when a route is
> terminated and it's fine to gracefully stop it.
> Any feedback or possible workaround is appreciated as well, thanks!
> [1] https://github.com/apache/camel-k/issues/4343
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19367) CamelEvent.RouteCompleted
[ https://issues.apache.org/jira/browse/CAMEL-19367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723866#comment-17723866 ] Pasquale Congiusti commented on CAMEL-19367: Perfect, it seems we have a final solution then. Thanks a lot for putting the example together! > CamelEvent.RouteCompleted > - > > Key: CAMEL-19367 > URL: https://issues.apache.org/jira/browse/CAMEL-19367 > Project: Camel > Issue Type: Improvement >Affects Versions: 3.20.4 >Reporter: Pasquale Congiusti >Priority: Major > > Hello team. While troubleshooting this Camel K issue [1], I've realized we're > missing some route event that can tell us that the route was completed. Do > you think it would be possible to include the `RouteCompleted` event? From > what I can tell, it would be an event generated once all the steps of the > route are completed. Without that, we don't know exactly when a route is > terminated and it's fine to gracefully stop it. > Any feedback or possible workaround is appreciated as well, thanks! > [1] https://github.com/apache/camel-k/issues/4343 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19368) camel-main - Auto detect custom EventNotifer from registry
[ https://issues.apache.org/jira/browse/CAMEL-19368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19368. - Fix Version/s: 3.21.0 Resolution: Fixed > camel-main - Auto detect custom EventNotifer from registry > -- > > Key: CAMEL-19368 > URL: https://issues.apache.org/jira/browse/CAMEL-19368 > Project: Camel > Issue Type: Improvement > Components: camel-main >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.21.0, 4.0-RC1, 4.0 > > > This makes it easier to provide custom event notifiers which you can just > annotate for dependency injection and auto discovered by camel like we do for > other stuff -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19367) CamelEvent.RouteCompleted
[ https://issues.apache.org/jira/browse/CAMEL-19367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19367. - Resolution: Information Provided > CamelEvent.RouteCompleted > - > > Key: CAMEL-19367 > URL: https://issues.apache.org/jira/browse/CAMEL-19367 > Project: Camel > Issue Type: Improvement >Affects Versions: 3.20.4 >Reporter: Pasquale Congiusti >Priority: Major > > Hello team. While troubleshooting this Camel K issue [1], I've realized we're > missing some route event that can tell us that the route was completed. Do > you think it would be possible to include the `RouteCompleted` event? From > what I can tell, it would be an event generated once all the steps of the > route are completed. Without that, we don't know exactly when a route is > terminated and it's fine to gracefully stop it. > Any feedback or possible workaround is appreciated as well, thanks! > [1] https://github.com/apache/camel-k/issues/4343 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19369) camel-jbang - Trace command to have endpoint URI information
Claus Ibsen created CAMEL-19369: --- Summary: camel-jbang - Trace command to have endpoint URI information Key: CAMEL-19369 URL: https://issues.apache.org/jira/browse/CAMEL-19369 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen We should improve the information from camel trace, to have endpoint details when an event is from an endpoint (input to a route) or send somewhere (to, toD, etc.) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19370) camel-jbang - Make it possible to show full url for very long endpoints
Claus Ibsen created CAMEL-19370: --- Summary: camel-jbang - Make it possible to show full url for very long endpoints Key: CAMEL-19370 URL: https://issues.apache.org/jira/browse/CAMEL-19370 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen ~/workspace ❯ camel get endpoint PID NAME AGE DIR TOTAL URI 44005 consumer 3m11s log://info?multiline=true&showAll=true 44005 consumer 3m11s in 0 kamelet://kafka-not-secured-source?bootstrapServers=localhost:9092&topic=foobar 44005 consumer 3m11s kamelet://sink?routeId=kafka-not-secured-source-1 44005 consumer 3m11s in 0 kafka://foobar?allowManualCommit=false&autoCommitEnable=true&autoOffsetReset=latest&bro… -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19370) camel-jbang - Make it possible to show full url for very long endpoints
[ https://issues.apache.org/jira/browse/CAMEL-19370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723874#comment-17723874 ] Claus Ibsen commented on CAMEL-19370: - Also add option to show sensitive information (eg passwords) > camel-jbang - Make it possible to show full url for very long endpoints > --- > > Key: CAMEL-19370 > URL: https://issues.apache.org/jira/browse/CAMEL-19370 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > > ~/workspace ❯ camel get endpoint > PID NAME AGE DIR TOTAL URI > 44005 consumer 3m11s log://info?multiline=true&showAll=true > 44005 consumer 3m11s in 0 > kamelet://kafka-not-secured-source?bootstrapServers=localhost:9092&topic=foobar > 44005 consumer 3m11s > kamelet://sink?routeId=kafka-not-secured-source-1 > 44005 consumer 3m11s in 0 > kafka://foobar?allowManualCommit=false&autoCommitEnable=true&autoOffsetReset=latest&bro… -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19370) camel-jbang - Make it possible to show full url for very long endpoints
[ https://issues.apache.org/jira/browse/CAMEL-19370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19370: Fix Version/s: 3.20.5 3.21.0 4.0-RC1 4.0 > camel-jbang - Make it possible to show full url for very long endpoints > --- > > Key: CAMEL-19370 > URL: https://issues.apache.org/jira/browse/CAMEL-19370 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.20.5, 3.21.0, 4.0-RC1, 4.0 > > > ~/workspace ❯ camel get endpoint > PID NAME AGE DIR TOTAL URI > 44005 consumer 3m11s log://info?multiline=true&showAll=true > 44005 consumer 3m11s in 0 > kamelet://kafka-not-secured-source?bootstrapServers=localhost:9092&topic=foobar > 44005 consumer 3m11s > kamelet://sink?routeId=kafka-not-secured-source-1 > 44005 consumer 3m11s in 0 > kafka://foobar?allowManualCommit=false&autoCommitEnable=true&autoOffsetReset=latest&bro… -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19370) camel-jbang - Make it possible to show full url for very long endpoints
[ https://issues.apache.org/jira/browse/CAMEL-19370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-19370: --- Assignee: Claus Ibsen > camel-jbang - Make it possible to show full url for very long endpoints > --- > > Key: CAMEL-19370 > URL: https://issues.apache.org/jira/browse/CAMEL-19370 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.20.5, 3.21.0, 4.0-RC1, 4.0 > > > ~/workspace ❯ camel get endpoint > PID NAME AGE DIR TOTAL URI > 44005 consumer 3m11s log://info?multiline=true&showAll=true > 44005 consumer 3m11s in 0 > kamelet://kafka-not-secured-source?bootstrapServers=localhost:9092&topic=foobar > 44005 consumer 3m11s > kamelet://sink?routeId=kafka-not-secured-source-1 > 44005 consumer 3m11s in 0 > kafka://foobar?allowManualCommit=false&autoCommitEnable=true&autoOffsetReset=latest&bro… -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19370) camel-jbang - Make it possible to show full url for very long endpoints
[ https://issues.apache.org/jira/browse/CAMEL-19370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19370. - Resolution: Fixed > camel-jbang - Make it possible to show full url for very long endpoints > --- > > Key: CAMEL-19370 > URL: https://issues.apache.org/jira/browse/CAMEL-19370 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.20.5, 3.21.0, 4.0-RC1, 4.0 > > > ~/workspace ❯ camel get endpoint > PID NAME AGE DIR TOTAL URI > 44005 consumer 3m11s log://info?multiline=true&showAll=true > 44005 consumer 3m11s in 0 > kamelet://kafka-not-secured-source?bootstrapServers=localhost:9092&topic=foobar > 44005 consumer 3m11s > kamelet://sink?routeId=kafka-not-secured-source-1 > 44005 consumer 3m11s in 0 > kafka://foobar?allowManualCommit=false&autoCommitEnable=true&autoOffsetReset=latest&bro… -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19371) RedeliveryErrorHandler's suppressed exceptions cause memory leak and logging issue
Bence created CAMEL-19371:
-
Summary: RedeliveryErrorHandler's suppressed exceptions cause
memory leak and logging issue
Key: CAMEL-19371
URL: https://issues.apache.org/jira/browse/CAMEL-19371
Project: Camel
Issue Type: Bug
Components: camel-core-processor
Affects Versions: 3.14.1
Reporter: Bence
Attachments: suppressed.log
Hi There,
I am a bit dubious about the behavior of RedeliveryErrorHandler's
handleException() method in camel-core-processor bundle.
Chaining all exceptions in suppressedExceptions of Throwable during the
redelivery process may not be the original intention, at least the comment
below is suggesting that the goal was something else here.
{quote}
if (previous != null && previous != e) {
// a 2nd exception was thrown while handling a previous exception
// so we need to add the previous as suppressed by the new exception
// see also FatalFallbackErrorHandler
{quote}
The consequence of adding the previous exception to the suppressedExceptions
list of the current one is building up an infinite chain of objects, besides a
single log entry can be huge after a couple of retry attempts, see attached log.
I think the best would be to turn this feature on/off by a configuration
parameter.
Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-19372) camel-spring-boot - Upgrade to 2.7.12
[ https://issues.apache.org/jira/browse/CAMEL-19372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19372. - Resolution: Fixed > camel-spring-boot - Upgrade to 2.7.12 > - > > Key: CAMEL-19372 > URL: https://issues.apache.org/jira/browse/CAMEL-19372 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.18.7, 3.20.5, 3.21.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19372) camel-spring-boot - Upgrade to 2.7.12
Claus Ibsen created CAMEL-19372: --- Summary: camel-spring-boot - Upgrade to 2.7.12 Key: CAMEL-19372 URL: https://issues.apache.org/jira/browse/CAMEL-19372 Project: Camel Issue Type: Dependency upgrade Components: camel-spring-boot Reporter: Claus Ibsen Fix For: 3.18.7, 3.20.5, 3.21.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19371) RedeliveryErrorHandler's suppressed exceptions cause memory leak and logging issue
[
https://issues.apache.org/jira/browse/CAMEL-19371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724011#comment-17724011
]
Claus Ibsen commented on CAMEL-19371:
-
Yeah that is a good point about we should likely just keep the last error so
the depth does not grow soo big
> RedeliveryErrorHandler's suppressed exceptions cause memory leak and logging
> issue
> --
>
> Key: CAMEL-19371
> URL: https://issues.apache.org/jira/browse/CAMEL-19371
> Project: Camel
> Issue Type: Bug
> Components: camel-core-processor
>Affects Versions: 3.14.1
>Reporter: Bence
>Priority: Major
> Attachments: suppressed.log
>
>
> Hi There,
> I am a bit dubious about the behavior of RedeliveryErrorHandler's
> handleException() method in camel-core-processor bundle.
> Chaining all exceptions in suppressedExceptions of Throwable during the
> redelivery process may not be the original intention, at least the comment
> below is suggesting that the goal was something else here.
> {quote}
> if (previous != null && previous != e) {
> // a 2nd exception was thrown while handling a previous exception
> // so we need to add the previous as suppressed by the new exception
> // see also FatalFallbackErrorHandler
> {quote}
> The consequence of adding the previous exception to the suppressedExceptions
> list of the current one is building up an infinite chain of objects, besides
> a single log entry can be huge after a couple of retry attempts, see attached
> log.
> I think the best would be to turn this feature on/off by a configuration
> parameter.
> Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19371) RedeliveryErrorHandler's suppressed exceptions cause memory leak and logging issue
[
https://issues.apache.org/jira/browse/CAMEL-19371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19371:
Fix Version/s: 4.0-RC1
4.0
> RedeliveryErrorHandler's suppressed exceptions cause memory leak and logging
> issue
> --
>
> Key: CAMEL-19371
> URL: https://issues.apache.org/jira/browse/CAMEL-19371
> Project: Camel
> Issue Type: Bug
> Components: camel-core-processor
>Affects Versions: 3.14.1
>Reporter: Bence
>Priority: Major
> Fix For: 4.0-RC1, 4.0
>
> Attachments: suppressed.log
>
>
> Hi There,
> I am a bit dubious about the behavior of RedeliveryErrorHandler's
> handleException() method in camel-core-processor bundle.
> Chaining all exceptions in suppressedExceptions of Throwable during the
> redelivery process may not be the original intention, at least the comment
> below is suggesting that the goal was something else here.
> {quote}
> if (previous != null && previous != e) {
> // a 2nd exception was thrown while handling a previous exception
> // so we need to add the previous as suppressed by the new exception
> // see also FatalFallbackErrorHandler
> {quote}
> The consequence of adding the previous exception to the suppressedExceptions
> list of the current one is building up an infinite chain of objects, besides
> a single log entry can be huge after a couple of retry attempts, see attached
> log.
> I think the best would be to turn this feature on/off by a configuration
> parameter.
> Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19371) RedeliveryErrorHandler's suppressed exceptions cause memory leak and logging issue
[
https://issues.apache.org/jira/browse/CAMEL-19371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19371:
Priority: Minor (was: Major)
> RedeliveryErrorHandler's suppressed exceptions cause memory leak and logging
> issue
> --
>
> Key: CAMEL-19371
> URL: https://issues.apache.org/jira/browse/CAMEL-19371
> Project: Camel
> Issue Type: Bug
> Components: camel-core-processor
>Affects Versions: 3.14.1
>Reporter: Bence
>Priority: Minor
> Fix For: 4.0-RC1, 4.0
>
> Attachments: suppressed.log
>
>
> Hi There,
> I am a bit dubious about the behavior of RedeliveryErrorHandler's
> handleException() method in camel-core-processor bundle.
> Chaining all exceptions in suppressedExceptions of Throwable during the
> redelivery process may not be the original intention, at least the comment
> below is suggesting that the goal was something else here.
> {quote}
> if (previous != null && previous != e) {
> // a 2nd exception was thrown while handling a previous exception
> // so we need to add the previous as suppressed by the new exception
> // see also FatalFallbackErrorHandler
> {quote}
> The consequence of adding the previous exception to the suppressedExceptions
> list of the current one is building up an infinite chain of objects, besides
> a single log entry can be huge after a couple of retry attempts, see attached
> log.
> I think the best would be to turn this feature on/off by a configuration
> parameter.
> Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19371) RedeliveryErrorHandler's suppressed exceptions cause memory leak and logging issue
[
https://issues.apache.org/jira/browse/CAMEL-19371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724012#comment-17724012
]
Claus Ibsen commented on CAMEL-19371:
-
its not a memory leak as the memory can be reclaimed, its just a long
stacktrace if retry is many times. And you should not have forever retries then
you have another problem on your hand
> RedeliveryErrorHandler's suppressed exceptions cause memory leak and logging
> issue
> --
>
> Key: CAMEL-19371
> URL: https://issues.apache.org/jira/browse/CAMEL-19371
> Project: Camel
> Issue Type: Bug
> Components: camel-core-processor
>Affects Versions: 3.14.1
>Reporter: Bence
>Priority: Minor
> Fix For: 4.0-RC1, 4.0
>
> Attachments: suppressed.log
>
>
> Hi There,
> I am a bit dubious about the behavior of RedeliveryErrorHandler's
> handleException() method in camel-core-processor bundle.
> Chaining all exceptions in suppressedExceptions of Throwable during the
> redelivery process may not be the original intention, at least the comment
> below is suggesting that the goal was something else here.
> {quote}
> if (previous != null && previous != e) {
> // a 2nd exception was thrown while handling a previous exception
> // so we need to add the previous as suppressed by the new exception
> // see also FatalFallbackErrorHandler
> {quote}
> The consequence of adding the previous exception to the suppressedExceptions
> list of the current one is building up an infinite chain of objects, besides
> a single log entry can be huge after a couple of retry attempts, see attached
> log.
> I think the best would be to turn this feature on/off by a configuration
> parameter.
> Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19364) Rest-openapi: lookup mechanism does not work after changes from Camel-18963
[
https://issues.apache.org/jira/browse/CAMEL-19364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19364:
Priority: Minor (was: Major)
> Rest-openapi: lookup mechanism does not work after changes from Camel-18963
> ---
>
> Key: CAMEL-19364
> URL: https://issues.apache.org/jira/browse/CAMEL-19364
> Project: Camel
> Issue Type: Bug
> Components: camel-rest-openapi
>Affects Versions: 4.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Minor
>
> I was trying to synchronize camel-quarkus with current Camel from `main`
> branch.
> I noticed failures related to fix
> [https://github.com/apache/camel/commit/e2ad230d86fcbbc1e3c4ad5a9daf01aa3127eb42]
> in the Camel-rest-openapi component.
> According to the doc, the url in component can be specified i.g.
> "classpath:...", "bean:...". At least these 2 options does not work.
> It can be verified by a simple test:
> {code:java}
> @Test
> public void testClasspath() throws Exception{
> Producer p =
> context().getEndpoint("rest-openapi:addPet?specificationUri=classpath:openapi.json").createProducer();
> Assertions.assertNotNull(p);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19365) camel-undertow: UndertowHttpsSpringTest broken after upgrade
[ https://issues.apache.org/jira/browse/CAMEL-19365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19365: Priority: Minor (was: Major) > camel-undertow: UndertowHttpsSpringTest broken after upgrade > > > Key: CAMEL-19365 > URL: https://issues.apache.org/jira/browse/CAMEL-19365 > Project: Camel > Issue Type: Task > Components: camel-undertow, tests >Affects Versions: 4.0-M3 >Reporter: Otavio Rodolfo Piske >Priority: Minor > > The [upgrade to Undertow > 2.3.5|https://github.com/apache/camel/commit/5dd5dc6f47ed2b6230836428df6420271b5ea117#diff-b5a06276719e759fe07dfe6f75d781be5f83d2215179d82bdb195ad035348214R479] > broke the UndertowHttpsSpringTest. It is now failing due to a > java.nio.channels.ClosedChannelException. > It seems to me that the > [changes|https://github.com/undertow-io/undertow/pull/1452] from > [UNDERTOW-2252|https://issues.redhat.com/browse/UNDERTOW-2252] may have > broken this test (or the test is wrong). > This needs to be investigated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19364) Rest-openapi: lookup mechanism does not work after changes from Camel-18963
[
https://issues.apache.org/jira/browse/CAMEL-19364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19364:
Fix Version/s: 4.0-RC1
4.0
> Rest-openapi: lookup mechanism does not work after changes from Camel-18963
> ---
>
> Key: CAMEL-19364
> URL: https://issues.apache.org/jira/browse/CAMEL-19364
> Project: Camel
> Issue Type: Bug
> Components: camel-rest-openapi
>Affects Versions: 4.0
>Reporter: Jiri Ondrusek
>Assignee: Jiri Ondrusek
>Priority: Minor
> Fix For: 4.0-RC1, 4.0
>
>
> I was trying to synchronize camel-quarkus with current Camel from `main`
> branch.
> I noticed failures related to fix
> [https://github.com/apache/camel/commit/e2ad230d86fcbbc1e3c4ad5a9daf01aa3127eb42]
> in the Camel-rest-openapi component.
> According to the doc, the url in component can be specified i.g.
> "classpath:...", "bean:...". At least these 2 options does not work.
> It can be verified by a simple test:
> {code:java}
> @Test
> public void testClasspath() throws Exception{
> Producer p =
> context().getEndpoint("rest-openapi:addPet?specificationUri=classpath:openapi.json").createProducer();
> Assertions.assertNotNull(p);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19339) karaf - ConnectionFactory not found when use camel-activemq
[ https://issues.apache.org/jira/browse/CAMEL-19339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724013#comment-17724013 ] Claus Ibsen commented on CAMEL-19339: - You may need to install JMS 1.x specs as it may be that karaf only comes with v2 karaf@root()> exports | grep -i javax.jms javax.jms │ 2.0.0 │ 125 │ org.apache.geronimo.specs.geronimo-jms_2.0_spec > karaf - ConnectionFactory not found when use camel-activemq > --- > > Key: CAMEL-19339 > URL: https://issues.apache.org/jira/browse/CAMEL-19339 > Project: Camel > Issue Type: Bug > Components: karaf >Affects Versions: 3.20.4 > Environment: Java 11 > Karaf 4.3.3 > Camel 3.20.4 >Reporter: Kiryanov Vlad >Priority: Minor > Attachments: TestCamel.zip > > > Hello. > I use Apache Karaf 4.4.3 as an osgi container. When I try to use > camel-activemq 3.20.4 I get an error while deploy bundle: > Caused by: java.lang.NoClassDefFoundError: javax/jms/ConnectionFactory > at > org.apache.camel.component.activemq.ActiveMQComponent.createConfiguration(ActiveMQComponent.java:260) > ~[?:?] > at > org.apache.camel.component.jms.JmsComponent.(JmsComponent.java:76) > ~[?:?] > at > org.apache.camel.component.activemq.ActiveMQComponent.(ActiveMQComponent.java:48) > ~[?:?] > at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > ~[?:?] > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > ~[?:?] > at java.lang.reflect.Constructor.newInstance(Constructor.java:490) ~[?:?] > at > org.apache.aries.blueprint.utils.ReflectionUtils.newInstance(ReflectionUtils.java:369) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.newInstance(BeanRecipe.java:839) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.getInstanceFromType(BeanRecipe.java:350) > ~[?:?] > ... 28 more > Caused by: java.lang.ClassNotFoundException: javax.jms.ConnectionFactory not > found by org.apache.camel.camel-activemq [121] > at > org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591) > ~[?:?] > at > org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79) > ~[?:?] > In Karaf I use commands: > repo-add camel 3.20.4 > feature:install camel > feature:install camel-activemq > My code and full log is in an attachment > On version 3.18.6 this code works -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19339) karaf - ConnectionFactory not found when use camel-activemq
[ https://issues.apache.org/jira/browse/CAMEL-19339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724018#comment-17724018 ] Claus Ibsen commented on CAMEL-19339: - Yeah so in camel-activemq 3.20.4 javax.jms;resolution:=optional;version="[1.1,2)", And in 3.18.6 javax.jms;version="[1.1,2)", > karaf - ConnectionFactory not found when use camel-activemq > --- > > Key: CAMEL-19339 > URL: https://issues.apache.org/jira/browse/CAMEL-19339 > Project: Camel > Issue Type: Bug > Components: karaf >Affects Versions: 3.20.4 > Environment: Java 11 > Karaf 4.3.3 > Camel 3.20.4 >Reporter: Kiryanov Vlad >Priority: Minor > Attachments: TestCamel.zip > > > Hello. > I use Apache Karaf 4.4.3 as an osgi container. When I try to use > camel-activemq 3.20.4 I get an error while deploy bundle: > Caused by: java.lang.NoClassDefFoundError: javax/jms/ConnectionFactory > at > org.apache.camel.component.activemq.ActiveMQComponent.createConfiguration(ActiveMQComponent.java:260) > ~[?:?] > at > org.apache.camel.component.jms.JmsComponent.(JmsComponent.java:76) > ~[?:?] > at > org.apache.camel.component.activemq.ActiveMQComponent.(ActiveMQComponent.java:48) > ~[?:?] > at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > ~[?:?] > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > ~[?:?] > at java.lang.reflect.Constructor.newInstance(Constructor.java:490) ~[?:?] > at > org.apache.aries.blueprint.utils.ReflectionUtils.newInstance(ReflectionUtils.java:369) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.newInstance(BeanRecipe.java:839) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.getInstanceFromType(BeanRecipe.java:350) > ~[?:?] > ... 28 more > Caused by: java.lang.ClassNotFoundException: javax.jms.ConnectionFactory not > found by org.apache.camel.camel-activemq [121] > at > org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591) > ~[?:?] > at > org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79) > ~[?:?] > In Karaf I use commands: > repo-add camel 3.20.4 > feature:install camel > feature:install camel-activemq > My code and full log is in an attachment > On version 3.18.6 this code works -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19339) karaf - ConnectionFactory not found when use camel-activemq
[ https://issues.apache.org/jira/browse/CAMEL-19339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724020#comment-17724020 ] Claus Ibsen commented on CAMEL-19339: - It could be activemq itself and those darn maven plugins that generate that osgi manifest that does this wrong now > karaf - ConnectionFactory not found when use camel-activemq > --- > > Key: CAMEL-19339 > URL: https://issues.apache.org/jira/browse/CAMEL-19339 > Project: Camel > Issue Type: Bug > Components: karaf >Affects Versions: 3.20.4 > Environment: Java 11 > Karaf 4.3.3 > Camel 3.20.4 >Reporter: Kiryanov Vlad >Priority: Minor > Attachments: TestCamel.zip > > > Hello. > I use Apache Karaf 4.4.3 as an osgi container. When I try to use > camel-activemq 3.20.4 I get an error while deploy bundle: > Caused by: java.lang.NoClassDefFoundError: javax/jms/ConnectionFactory > at > org.apache.camel.component.activemq.ActiveMQComponent.createConfiguration(ActiveMQComponent.java:260) > ~[?:?] > at > org.apache.camel.component.jms.JmsComponent.(JmsComponent.java:76) > ~[?:?] > at > org.apache.camel.component.activemq.ActiveMQComponent.(ActiveMQComponent.java:48) > ~[?:?] > at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > ~[?:?] > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > ~[?:?] > at java.lang.reflect.Constructor.newInstance(Constructor.java:490) ~[?:?] > at > org.apache.aries.blueprint.utils.ReflectionUtils.newInstance(ReflectionUtils.java:369) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.newInstance(BeanRecipe.java:839) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.getInstanceFromType(BeanRecipe.java:350) > ~[?:?] > ... 28 more > Caused by: java.lang.ClassNotFoundException: javax.jms.ConnectionFactory not > found by org.apache.camel.camel-activemq [121] > at > org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591) > ~[?:?] > at > org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79) > ~[?:?] > In Karaf I use commands: > repo-add camel 3.20.4 > feature:install camel > feature:install camel-activemq > My code and full log is in an attachment > On version 3.18.6 this code works -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19339) karaf - ConnectionFactory not found when use camel-activemq
[ https://issues.apache.org/jira/browse/CAMEL-19339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19339: Fix Version/s: 3.21.0 > karaf - ConnectionFactory not found when use camel-activemq > --- > > Key: CAMEL-19339 > URL: https://issues.apache.org/jira/browse/CAMEL-19339 > Project: Camel > Issue Type: Bug > Components: karaf >Affects Versions: 3.20.4 > Environment: Java 11 > Karaf 4.3.3 > Camel 3.20.4 >Reporter: Kiryanov Vlad >Priority: Minor > Fix For: 3.20.5, 3.21.0 > > Attachments: TestCamel.zip > > > Hello. > I use Apache Karaf 4.4.3 as an osgi container. When I try to use > camel-activemq 3.20.4 I get an error while deploy bundle: > Caused by: java.lang.NoClassDefFoundError: javax/jms/ConnectionFactory > at > org.apache.camel.component.activemq.ActiveMQComponent.createConfiguration(ActiveMQComponent.java:260) > ~[?:?] > at > org.apache.camel.component.jms.JmsComponent.(JmsComponent.java:76) > ~[?:?] > at > org.apache.camel.component.activemq.ActiveMQComponent.(ActiveMQComponent.java:48) > ~[?:?] > at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > ~[?:?] > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > ~[?:?] > at java.lang.reflect.Constructor.newInstance(Constructor.java:490) ~[?:?] > at > org.apache.aries.blueprint.utils.ReflectionUtils.newInstance(ReflectionUtils.java:369) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.newInstance(BeanRecipe.java:839) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.getInstanceFromType(BeanRecipe.java:350) > ~[?:?] > ... 28 more > Caused by: java.lang.ClassNotFoundException: javax.jms.ConnectionFactory not > found by org.apache.camel.camel-activemq [121] > at > org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591) > ~[?:?] > at > org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79) > ~[?:?] > In Karaf I use commands: > repo-add camel 3.20.4 > feature:install camel > feature:install camel-activemq > My code and full log is in an attachment > On version 3.18.6 this code works -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19339) karaf - ConnectionFactory not found when use camel-activemq
[ https://issues.apache.org/jira/browse/CAMEL-19339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19339: Fix Version/s: 3.20.5 > karaf - ConnectionFactory not found when use camel-activemq > --- > > Key: CAMEL-19339 > URL: https://issues.apache.org/jira/browse/CAMEL-19339 > Project: Camel > Issue Type: Bug > Components: karaf >Affects Versions: 3.20.4 > Environment: Java 11 > Karaf 4.3.3 > Camel 3.20.4 >Reporter: Kiryanov Vlad >Priority: Minor > Fix For: 3.20.5 > > Attachments: TestCamel.zip > > > Hello. > I use Apache Karaf 4.4.3 as an osgi container. When I try to use > camel-activemq 3.20.4 I get an error while deploy bundle: > Caused by: java.lang.NoClassDefFoundError: javax/jms/ConnectionFactory > at > org.apache.camel.component.activemq.ActiveMQComponent.createConfiguration(ActiveMQComponent.java:260) > ~[?:?] > at > org.apache.camel.component.jms.JmsComponent.(JmsComponent.java:76) > ~[?:?] > at > org.apache.camel.component.activemq.ActiveMQComponent.(ActiveMQComponent.java:48) > ~[?:?] > at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > ~[?:?] > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > ~[?:?] > at java.lang.reflect.Constructor.newInstance(Constructor.java:490) ~[?:?] > at > org.apache.aries.blueprint.utils.ReflectionUtils.newInstance(ReflectionUtils.java:369) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.newInstance(BeanRecipe.java:839) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.getInstanceFromType(BeanRecipe.java:350) > ~[?:?] > ... 28 more > Caused by: java.lang.ClassNotFoundException: javax.jms.ConnectionFactory not > found by org.apache.camel.camel-activemq [121] > at > org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591) > ~[?:?] > at > org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79) > ~[?:?] > In Karaf I use commands: > repo-add camel 3.20.4 > feature:install camel > feature:install camel-activemq > My code and full log is in an attachment > On version 3.18.6 this code works -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19339) karaf - ConnectionFactory not found when use camel-activemq
[ https://issues.apache.org/jira/browse/CAMEL-19339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724024#comment-17724024 ] Claus Ibsen commented on CAMEL-19339: - Okay I got a bit further, you now need to install a connection pool Caused by: java.lang.ClassNotFoundException: org.apache.activemq.pool.PooledConnectionFactory not found by org.apache.camel.camel-activemq [121] > karaf - ConnectionFactory not found when use camel-activemq > --- > > Key: CAMEL-19339 > URL: https://issues.apache.org/jira/browse/CAMEL-19339 > Project: Camel > Issue Type: Bug > Components: karaf >Affects Versions: 3.20.4 > Environment: Java 11 > Karaf 4.3.3 > Camel 3.20.4 >Reporter: Kiryanov Vlad >Priority: Minor > Fix For: 3.20.5, 3.21.0 > > Attachments: TestCamel.zip > > > Hello. > I use Apache Karaf 4.4.3 as an osgi container. When I try to use > camel-activemq 3.20.4 I get an error while deploy bundle: > Caused by: java.lang.NoClassDefFoundError: javax/jms/ConnectionFactory > at > org.apache.camel.component.activemq.ActiveMQComponent.createConfiguration(ActiveMQComponent.java:260) > ~[?:?] > at > org.apache.camel.component.jms.JmsComponent.(JmsComponent.java:76) > ~[?:?] > at > org.apache.camel.component.activemq.ActiveMQComponent.(ActiveMQComponent.java:48) > ~[?:?] > at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > ~[?:?] > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > ~[?:?] > at java.lang.reflect.Constructor.newInstance(Constructor.java:490) ~[?:?] > at > org.apache.aries.blueprint.utils.ReflectionUtils.newInstance(ReflectionUtils.java:369) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.newInstance(BeanRecipe.java:839) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.getInstanceFromType(BeanRecipe.java:350) > ~[?:?] > ... 28 more > Caused by: java.lang.ClassNotFoundException: javax.jms.ConnectionFactory not > found by org.apache.camel.camel-activemq [121] > at > org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591) > ~[?:?] > at > org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79) > ~[?:?] > In Karaf I use commands: > repo-add camel 3.20.4 > feature:install camel > feature:install camel-activemq > My code and full log is in an attachment > On version 3.18.6 this code works -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19339) karaf - ConnectionFactory not found when use camel-activemq
[ https://issues.apache.org/jira/browse/CAMEL-19339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724028#comment-17724028 ] Claus Ibsen commented on CAMEL-19339: - Okay this was more work due to bad osgi 23:07:13.536 INFO [pipe-start 141] Blueprint bundle org.example.TestCamel/1.0.0.SNAPSHOT has been started 23:07:13.536 INFO [Blueprint Event Dispatcher: 1] Attempting to start CamelContext: TestNewCamel 23:07:13.615 INFO [Blueprint Event Dispatcher: 1] Apache Camel 3.20.5-SNAPSHOT (TestNewCamel) is starting 23:07:13.811 INFO [Blueprint Event Dispatcher: 1] Routes startup (started:1) 23:07:13.811 INFO [Blueprint Event Dispatcher: 1] Started route1 (activemq://queue:TEST) 23:07:13.811 INFO [Blueprint Event Dispatcher: 1] Apache Camel 3.20.5-SNAPSHOT (TestNewCamel) started in 284ms (build:11ms init:78ms start:195ms) > karaf - ConnectionFactory not found when use camel-activemq > --- > > Key: CAMEL-19339 > URL: https://issues.apache.org/jira/browse/CAMEL-19339 > Project: Camel > Issue Type: Bug > Components: karaf >Affects Versions: 3.20.4 > Environment: Java 11 > Karaf 4.3.3 > Camel 3.20.4 >Reporter: Kiryanov Vlad >Priority: Minor > Fix For: 3.20.5, 3.21.0 > > Attachments: TestCamel.zip > > > Hello. > I use Apache Karaf 4.4.3 as an osgi container. When I try to use > camel-activemq 3.20.4 I get an error while deploy bundle: > Caused by: java.lang.NoClassDefFoundError: javax/jms/ConnectionFactory > at > org.apache.camel.component.activemq.ActiveMQComponent.createConfiguration(ActiveMQComponent.java:260) > ~[?:?] > at > org.apache.camel.component.jms.JmsComponent.(JmsComponent.java:76) > ~[?:?] > at > org.apache.camel.component.activemq.ActiveMQComponent.(ActiveMQComponent.java:48) > ~[?:?] > at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > ~[?:?] > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > ~[?:?] > at java.lang.reflect.Constructor.newInstance(Constructor.java:490) ~[?:?] > at > org.apache.aries.blueprint.utils.ReflectionUtils.newInstance(ReflectionUtils.java:369) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.newInstance(BeanRecipe.java:839) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.getInstanceFromType(BeanRecipe.java:350) > ~[?:?] > ... 28 more > Caused by: java.lang.ClassNotFoundException: javax.jms.ConnectionFactory not > found by org.apache.camel.camel-activemq [121] > at > org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591) > ~[?:?] > at > org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79) > ~[?:?] > In Karaf I use commands: > repo-add camel 3.20.4 > feature:install camel > feature:install camel-activemq > My code and full log is in an attachment > On version 3.18.6 this code works -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19339) karaf - ConnectionFactory not found when use camel-activemq
[ https://issues.apache.org/jira/browse/CAMEL-19339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19339. - Assignee: Claus Ibsen Resolution: Fixed > karaf - ConnectionFactory not found when use camel-activemq > --- > > Key: CAMEL-19339 > URL: https://issues.apache.org/jira/browse/CAMEL-19339 > Project: Camel > Issue Type: Bug > Components: karaf >Affects Versions: 3.20.4 > Environment: Java 11 > Karaf 4.3.3 > Camel 3.20.4 >Reporter: Kiryanov Vlad >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.20.5, 3.21.0 > > Attachments: TestCamel.zip > > > Hello. > I use Apache Karaf 4.4.3 as an osgi container. When I try to use > camel-activemq 3.20.4 I get an error while deploy bundle: > Caused by: java.lang.NoClassDefFoundError: javax/jms/ConnectionFactory > at > org.apache.camel.component.activemq.ActiveMQComponent.createConfiguration(ActiveMQComponent.java:260) > ~[?:?] > at > org.apache.camel.component.jms.JmsComponent.(JmsComponent.java:76) > ~[?:?] > at > org.apache.camel.component.activemq.ActiveMQComponent.(ActiveMQComponent.java:48) > ~[?:?] > at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > ~[?:?] > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > ~[?:?] > at java.lang.reflect.Constructor.newInstance(Constructor.java:490) ~[?:?] > at > org.apache.aries.blueprint.utils.ReflectionUtils.newInstance(ReflectionUtils.java:369) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.newInstance(BeanRecipe.java:839) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.getInstanceFromType(BeanRecipe.java:350) > ~[?:?] > ... 28 more > Caused by: java.lang.ClassNotFoundException: javax.jms.ConnectionFactory not > found by org.apache.camel.camel-activemq [121] > at > org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591) > ~[?:?] > at > org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79) > ~[?:?] > In Karaf I use commands: > repo-add camel 3.20.4 > feature:install camel > feature:install camel-activemq > My code and full log is in an attachment > On version 3.18.6 this code works -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19365) camel-undertow: UndertowHttpsSpringTest broken after upgrade
[
https://issues.apache.org/jira/browse/CAMEL-19365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724032#comment-17724032
]
Freeman Yue Fang commented on CAMEL-19365:
--
Hi [~orpiske],
I happen to know the root cause of this issue.
This is introduced by the fix of
[UNDERTOW-2212|https://issues.redhat.com/browse/UNDERTOW-2212].
Without UNDERTOW-2212, undertow conduit just not check the common name of the
http server host in the tls certificate when using SSL. But since UNDERTOW-2212
fixed this up, and in the UndertowHttpsSpringTest it simply uses a general
certificate which isn't much the test machine's hostname, that's why the test
fails now.
We can
1. run maven test with
-Dio.undertow.client.https.disableEndpointIdentification=true which explicitly
not check the common name(CN) of the host to make the test pass
2. we can configure the Undertow Options somewhere during the SSL conversation
using java code like
{code}
options = OptionMap.builder()
.set(UndertowOptions.ENDPOINT_IDENTIFICATION_ALGORITHM, "")
.getMap();
{code}
for this test to disable common name check.
Cheers
Freeman
> camel-undertow: UndertowHttpsSpringTest broken after upgrade
>
>
> Key: CAMEL-19365
> URL: https://issues.apache.org/jira/browse/CAMEL-19365
> Project: Camel
> Issue Type: Task
> Components: camel-undertow, tests
>Affects Versions: 4.0-M3
>Reporter: Otavio Rodolfo Piske
>Priority: Minor
>
> The [upgrade to Undertow
> 2.3.5|https://github.com/apache/camel/commit/5dd5dc6f47ed2b6230836428df6420271b5ea117#diff-b5a06276719e759fe07dfe6f75d781be5f83d2215179d82bdb195ad035348214R479]
> broke the UndertowHttpsSpringTest. It is now failing due to a
> java.nio.channels.ClosedChannelException.
> It seems to me that the
> [changes|https://github.com/undertow-io/undertow/pull/1452] from
> [UNDERTOW-2252|https://issues.redhat.com/browse/UNDERTOW-2252] may have
> broken this test (or the test is wrong).
> This needs to be investigated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19339) karaf - ConnectionFactory not found when use camel-activemq
[ https://issues.apache.org/jira/browse/CAMEL-19339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724132#comment-17724132 ] Kiryanov Vlad commented on CAMEL-19339: --- Thank you for your response. Waiting for 3.20.5 > karaf - ConnectionFactory not found when use camel-activemq > --- > > Key: CAMEL-19339 > URL: https://issues.apache.org/jira/browse/CAMEL-19339 > Project: Camel > Issue Type: Bug > Components: karaf >Affects Versions: 3.20.4 > Environment: Java 11 > Karaf 4.3.3 > Camel 3.20.4 >Reporter: Kiryanov Vlad >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.20.5, 3.21.0 > > Attachments: TestCamel.zip > > > Hello. > I use Apache Karaf 4.4.3 as an osgi container. When I try to use > camel-activemq 3.20.4 I get an error while deploy bundle: > Caused by: java.lang.NoClassDefFoundError: javax/jms/ConnectionFactory > at > org.apache.camel.component.activemq.ActiveMQComponent.createConfiguration(ActiveMQComponent.java:260) > ~[?:?] > at > org.apache.camel.component.jms.JmsComponent.(JmsComponent.java:76) > ~[?:?] > at > org.apache.camel.component.activemq.ActiveMQComponent.(ActiveMQComponent.java:48) > ~[?:?] > at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) ~[?:?] > at > jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > ~[?:?] > at > jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > ~[?:?] > at java.lang.reflect.Constructor.newInstance(Constructor.java:490) ~[?:?] > at > org.apache.aries.blueprint.utils.ReflectionUtils.newInstance(ReflectionUtils.java:369) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.newInstance(BeanRecipe.java:839) > ~[?:?] > at > org.apache.aries.blueprint.container.BeanRecipe.getInstanceFromType(BeanRecipe.java:350) > ~[?:?] > ... 28 more > Caused by: java.lang.ClassNotFoundException: javax.jms.ConnectionFactory not > found by org.apache.camel.camel-activemq [121] > at > org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591) > ~[?:?] > at > org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79) > ~[?:?] > In Karaf I use commands: > repo-add camel 3.20.4 > feature:install camel > feature:install camel-activemq > My code and full log is in an attachment > On version 3.18.6 this code works -- This message was sent by Atlassian Jira (v8.20.10#820010)
