[jira] [Created] (CAMEL-18154) camel-kamelet-main - Capture all dependencies
Claus Ibsen created CAMEL-18154: --- Summary: camel-kamelet-main - Capture all dependencies Key: CAMEL-18154 URL: https://issues.apache.org/jira/browse/CAMEL-18154 Project: Camel Issue Type: Dependency upgrade Components: camel-jbang Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.18.0 For camel-jbang and others it would be better to capture all dependencies instead of only what was downloaded due not already on cp -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18153) camel-spring-boot - Upgrade to 2.7.x
Claus Ibsen created CAMEL-18153: --- Summary: camel-spring-boot - Upgrade to 2.7.x Key: CAMEL-18153 URL: https://issues.apache.org/jira/browse/CAMEL-18153 Project: Camel Issue Type: Dependency upgrade Components: camel-spring-boot Reporter: Claus Ibsen Fix For: 3.18.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-17949) camel-netty-http - Infinite loop when setting retries
[
https://issues.apache.org/jira/browse/CAMEL-17949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544000#comment-17544000
]
Rhuan Rocha commented on CAMEL-17949:
-
Should I assign this ticket to me? Any action here?
> camel-netty-http - Infinite loop when setting retries
> -
>
> Key: CAMEL-17949
> URL: https://issues.apache.org/jira/browse/CAMEL-17949
> Project: Camel
> Issue Type: Bug
> Components: camel-netty-http
>Affects Versions: 3.14.2
>Reporter: Gerasimos Kalouris
>Priority: Major
> Attachments: netty-http-bug.zip
>
>
> When setting re-deliveries in case of `NettyHttpOperationFailedException` it
> seems that the exchange is submitted back to netty's executor group without
> incrementing the attempts counter, resulting to an infinite loop. This
> example works as expected when using the `camel-http` component.
> {code:java}
> onException(NettyHttpOperationFailedException.class)
> .maximumRedeliveries(2)
> .retryAttemptedLogLevel(LoggingLevel.WARN)
> .backOffMultiplier(5)
> .maximumRedeliveryDelay(500)
> .useExponentialBackOff()
> .handled(false);
> {code}
> {noformat}
> 12-04-2022 17:41:57[Test worker] [INFO ]
> o.a.camel.test.junit5.CamelTestSupport - Testing:
> retry_when_destination_fails_to_consume() (route.WebhooksRouteBuilderTest)
> 12-04-2022 17:41:57[Test worker] [INFO ]
> o.a.camel.test.junit5.CamelTestSupport -
>
> 12-04-2022 17:41:59[Test worker] [INFO ]
> o.a.camel.component.netty.NettyComponent - Creating shared
> NettyConsumerExecutorGroup with 25 threads
> 12-04-2022 17:41:59[Test worker] [INFO ]
> o.a.c.impl.engine.AbstractCamelContext - Routes startup (total:1 started:1)
> 12-04-2022 17:41:59[Test worker] [INFO ]
> o.a.c.impl.engine.AbstractCamelContext - Started mo-webhook
> (direct://mo-queue)
> 12-04-2022 17:41:59[Test worker] [INFO ]
> o.a.c.impl.engine.AbstractCamelContext - Apache Camel 3.14.2 (camel-1)
> started in 450ms (build:116ms init:225ms start:109ms)
> 12-04-2022 17:42:02[Camel Thread #1 - NettyClientTCPWorker] [WARN ]
> o.a.c.p.errorhandler.DefaultErrorHandler - Failed delivery for (MessageId:
> 0C03F6022475684- on ExchangeId:
> 0C03F6022475684-). On delivery attempt: 0 caught:
> org.apache.camel.component.netty.http.NettyHttpOperationFailedException:
> Netty HTTP operation failed invoking null with statusCode: 500
> 12-04-2022 17:42:02[Camel Thread #2 - NettyClientTCPWorker] [WARN ]
> o.a.c.p.errorhandler.DefaultErrorHandler - Failed delivery for (MessageId:
> 0C03F6022475684- on ExchangeId:
> 0C03F6022475684-). On delivery attempt: 1 caught:
> org.apache.camel.component.netty.http.NettyHttpOperationFailedException:
> Netty HTTP operation failed invoking null with statusCode: 500
> 12-04-2022 17:42:03[Camel Thread #3 - NettyClientTCPWorker] [WARN ]
> o.a.c.p.errorhandler.DefaultErrorHandler - Failed delivery for (MessageId:
> 0C03F6022475684- on ExchangeId:
> 0C03F6022475684-). On delivery attempt: 1 caught:
> org.apache.camel.component.netty.http.NettyHttpOperationFailedException:
> Netty HTTP operation failed invoking null with statusCode: 500
> 12-04-2022 17:42:03[Camel Thread #4 - NettyClientTCPWorker] [WARN ]
> o.a.c.p.errorhandler.DefaultErrorHandler - Failed delivery for (MessageId:
> 0C03F6022475684- on ExchangeId:
> 0C03F6022475684-). On delivery attempt: 1 caught:
> org.apache.camel.component.netty.http.NettyHttpOperationFailedException:
> Netty HTTP operation failed invoking null with statusCode: 500
> 12-04-2022 17:42:04[Camel Thread #5 - NettyClientTCPWorker] [WARN ]
> o.a.c.p.errorhandler.DefaultErrorHandler - Failed delivery for (MessageId:
> 0C03F6022475684- on ExchangeId:
> 0C03F6022475684-). On delivery attempt: 1 caught:
> org.apache.camel.component.netty.http.NettyHttpOperationFailedException:
> Netty HTTP operation failed invoking null with statusCode: 500
> 12-04-2022 17:42:04[Camel Thread #6 - NettyClientTCPWorker] [WARN ]
> o.a.c.p.errorhandler.DefaultErrorHandler - Failed delivery for (MessageId:
> 0C03F6022475684- on ExchangeId:
> 0C03F6022475684-). On delivery attempt: 1 caught:
> org.apache.camel.component.netty.http.NettyHttpOperationFailedException:
> Netty HTTP operation failed invoking null with statusCode: 500
> 12-04-2022 17:42:05[Camel Thread #7 - NettyClientTCPWorker] [WARN ]
> o.a.c.p.errorhandler.DefaultErrorHandler - Failed delivery for (MessageId:
> 0C03F6022475684- on ExchangeId:
> 0C03F6022475684-). On
[jira] [Resolved] (CAMEL-16287) camel-aws2-sqs should use pagination for deciding which aws sqs queues it should create
[ https://issues.apache.org/jira/browse/CAMEL-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-16287. -- Resolution: Fixed > camel-aws2-sqs should use pagination for deciding which aws sqs queues it > should create > --- > > Key: CAMEL-16287 > URL: https://issues.apache.org/jira/browse/CAMEL-16287 > Project: Camel > Issue Type: Bug >Affects Versions: 2.25.3, 3.8.0 >Reporter: Gyorgy Abraham >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.14.4, 3.18.0 > > > There is an auto create queue feature for aws-sqs in camel-sqs component. > Upon camel context creation / route building, it issues an API call to list > all sqs queues, so it skips the creation for already existing ones. If camel > context has a for example consumer route for an sqs queue that is not listed > in the response of this API call, camel will try to to create it. > However, this API only lists the first 1000 queues in the current account. If > there are more then 1000 queues, camel-sqs will try to create a new one, and > might fail. In our company's account, we have 1442 queues in our account and > Camel tried to create a .fifo queue because it thought it wasnt already > existing, resulting in application startup error. > Relevant code: > [https://github.com/apache/camel/blob/master/components/camel-aws2-sqs/src/main/java/org/apache/camel/component/aws2/sqs/Sqs2Endpoint.java#L174] > Relevant API docs at AWS: > [https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/sqs/AmazonSQS.html#listQueues-com.amazonaws.services.sqs.model.ListQueuesRequest-] > Solution is straightforward: use pagination and load all queues. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18152) camel-resume-api: investigate generating the adapter configuration during build
Otavio Rodolfo Piske created CAMEL-18152: Summary: camel-resume-api: investigate generating the adapter configuration during build Key: CAMEL-18152 URL: https://issues.apache.org/jira/browse/CAMEL-18152 Project: Camel Issue Type: Task Reporter: Otavio Rodolfo Piske Assignee: Otavio Rodolfo Piske Currently, we have to write a configuration file for the adapter to be loaded. Ideally, we could check during build if the consumer implements resumableaware of if an adapter is in the component build path, and then generate the file. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-17449) camel-jbang - Create project - Auto discover dependencies as quarkus extensions
[ https://issues.apache.org/jira/browse/CAMEL-17449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17449. - Resolution: Duplicate > camel-jbang - Create project - Auto discover dependencies as quarkus > extensions > --- > > Key: CAMEL-17449 > URL: https://issues.apache.org/jira/browse/CAMEL-17449 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 3.15.0 >Reporter: Claus Ibsen >Priority: Major > > https://camel.apache.org/manual/camel-jbang.html#_create_project > You have to specify the extensions manually via --quarkusDependencies > It would be good if we can find out what camel-xxx JARs are in use, and then > map these to quarkus GAVs > G = org.apache.camel -> org.apache.camel.quarkus > A = camel-timer -> camel-quarkus-timer -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18151) camel-jbang - Export to Quarkus and Spring Boot maven projects
Claus Ibsen created CAMEL-18151: --- Summary: camel-jbang - Export to Quarkus and Spring Boot maven projects Key: CAMEL-18151 URL: https://issues.apache.org/jira/browse/CAMEL-18151 Project: Camel Issue Type: New Feature Components: camel-jbang Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.18.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-17333) camel-jbang - Runtime statistics
[ https://issues.apache.org/jira/browse/CAMEL-17333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-17333. - Resolution: Fixed > camel-jbang - Runtime statistics > > > Key: CAMEL-17333 > URL: https://issues.apache.org/jira/browse/CAMEL-17333 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > > We should gather runtime statistics and be able to expose those for tooling -- This message was sent by Atlassian Jira (v8.20.7#820007)
