[jira] [Updated] (CAMEL-18146) camel-kafka - ssl.endpoint.identification.algorithm should be allowed to be an empty string
[ https://issues.apache.org/jira/browse/CAMEL-18146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18146: Fix Version/s: 3.18.0 > camel-kafka - ssl.endpoint.identification.algorithm should be allowed to be > an empty string > --- > > Key: CAMEL-18146 > URL: https://issues.apache.org/jira/browse/CAMEL-18146 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 3.17.0 >Reporter: Jake Mehring >Priority: Major > Fix For: 3.18.0 > > > This property was changed from being defaulted if null to being defaulted if > null or empty in the 3.17 release. Currently the only way to disable server > host name verification is to pass the Kafka consumer an empty string which is > impossible after that change. > > Relevant Code: > https://github.com/apache/camel/blob/main/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConfiguration.java#L436 > Relevant Docs: > [https://docs.confluent.io/platform/current/kafka/authentication_ssl.html#optional-settings] > > Solution is just to revert addPropertyIfNotEmpty to be addPropertyIfNotNull > for this property. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (CAMEL-14970) Implement camel-javascript component
[ https://issues.apache.org/jira/browse/CAMEL-14970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542727#comment-17542727 ] Raymond edited comment on CAMEL-14970 at 5/27/22 12:33 AM: --- This is maybe possible by using J2V8 [https://github.com/eclipsesource/J2V8] or Nashorn OpenJDK [https://mvnrepository.com/artifact/org.openjdk.nashorn/nashorn-core] ([https://github.com/openjdk/nashorn]) or use Rhino [https://github.com/mozilla/rhino] was (Author: skin27): This is maybe possible by using J2V8 (https://github.com/eclipsesource/J2V8) > Implement camel-javascript component > > > Key: CAMEL-14970 > URL: https://issues.apache.org/jira/browse/CAMEL-14970 > Project: Camel > Issue Type: New Feature >Reporter: Jan Bednar >Priority: Minor > > camel-script is removed in 3.x with CAMEL-13113 because of Nashorn Engine > deprecation in JDK11. We should implement camel-javascript based on some > supported engine (possibly graaljs?). > Some users are missing Javascript language in 3.x: > [https://camel.465427.n5.nabble.com/Re-Camel-script-eip-JavaScript-deprecated-tt5857880.html] > [https://stackoverflow.com/questions/61435521/camel-3-2-and-javascript] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-14970) Implement camel-javascript component
[ https://issues.apache.org/jira/browse/CAMEL-14970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542727#comment-17542727 ] Raymond commented on CAMEL-14970: - This is maybe possible by using J2V8 (https://github.com/eclipsesource/J2V8) > Implement camel-javascript component > > > Key: CAMEL-14970 > URL: https://issues.apache.org/jira/browse/CAMEL-14970 > Project: Camel > Issue Type: New Feature >Reporter: Jan Bednar >Priority: Minor > > camel-script is removed in 3.x with CAMEL-13113 because of Nashorn Engine > deprecation in JDK11. We should implement camel-javascript based on some > supported engine (possibly graaljs?). > Some users are missing Javascript language in 3.x: > [https://camel.465427.n5.nabble.com/Re-Camel-script-eip-JavaScript-deprecated-tt5857880.html] > [https://stackoverflow.com/questions/61435521/camel-3-2-and-javascript] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18146) camel-kafka - ssl.endpoint.identification.algorithm should be allowed to be an empty string
[ https://issues.apache.org/jira/browse/CAMEL-18146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jake Mehring updated CAMEL-18146: - Estimated Complexity: Novice (was: Unknown) > camel-kafka - ssl.endpoint.identification.algorithm should be allowed to be > an empty string > --- > > Key: CAMEL-18146 > URL: https://issues.apache.org/jira/browse/CAMEL-18146 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 3.17.0 >Reporter: Jake Mehring >Priority: Major > > This property was changed from being defaulted if null to being defaulted if > null or empty in the 3.17 release. Currently the only way to disable server > host name verification is to pass the Kafka consumer an empty string which is > impossible after that change. > > Relevant Code: > https://github.com/apache/camel/blob/main/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConfiguration.java#L436 > Relevant Docs: > [https://docs.confluent.io/platform/current/kafka/authentication_ssl.html#optional-settings] > > Solution is just to revert addPropertyIfNotEmpty to be addPropertyIfNotNull > for this property. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (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:comment-tabpanel=17542628#comment-17542628 ] Andrea Cosentino commented on CAMEL-16287: -- There is no plan for another 3.17.x release. It's not an LTS. It will be fixed in 3.18.x and LTS. > 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-18146) camel-kafka - ssl.endpoint.identification.algorithm should be allowed to be an empty string
Jake Mehring created CAMEL-18146: Summary: camel-kafka - ssl.endpoint.identification.algorithm should be allowed to be an empty string Key: CAMEL-18146 URL: https://issues.apache.org/jira/browse/CAMEL-18146 Project: Camel Issue Type: Bug Components: camel-kafka Affects Versions: 3.17.0 Reporter: Jake Mehring This property was changed from being defaulted if null to being defaulted if null or empty in the 3.17 release. Currently the only way to disable server host name verification is to pass the Kafka consumer an empty string which is impossible after that change. Relevant Code: https://github.com/apache/camel/blob/main/components/camel-kafka/src/main/java/org/apache/camel/component/kafka/KafkaConfiguration.java#L436 Relevant Docs: [https://docs.confluent.io/platform/current/kafka/authentication_ssl.html#optional-settings] Solution is just to revert addPropertyIfNotEmpty to be addPropertyIfNotNull for this property. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (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:comment-tabpanel=17542586#comment-17542586 ] Zoltán Nébli commented on CAMEL-16287: -- Please treat this with high prio and possibly create a minor release like 3.17.1 because this is very annoying and affecting us also. > 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] [Assigned] (CAMEL-18145) camel-aws-secretsmanager - Test failure in rotateSecrets
[ https://issues.apache.org/jira/browse/CAMEL-18145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18145: Assignee: Andrea Cosentino > camel-aws-secretsmanager - Test failure in rotateSecrets > > > Key: CAMEL-18145 > URL: https://issues.apache.org/jira/browse/CAMEL-18145 > Project: Camel > Issue Type: Test > Components: camel-aws >Affects Versions: 3.18.0 >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 3.18.0 > > > Message History (source location and message history is disabled) > --- > Source ID > Processor Elapsed (ms) > route6/route6 > from[direct://rotateSecret] 29 > ... > route6/to8 > aws-secrets-manager://test?operation=rotateSecret 0 > Stacktrace > --- > software.amazon.awssdk.services.secretsmanager.model.ResourceNotFoundException: > Lambda does not exist or could not be accessed (Service: SecretsManager, > Status Code: 400, Request ID: > KYCVGVN52HR0PX630EFH1HN44VH32JHHJC8DOFTB0GWO9LHG4OIO) > at > software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handleErrorResponse(CombinedResponseHandler.java:125) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handleResponse(CombinedResponseHandler.java:82) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handle(CombinedResponseHandler.java:60) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handle(CombinedResponseHandler.java:41) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.HandleResponseStage.execute(HandleResponseStage.java:40) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.HandleResponseStage.execute(HandleResponseStage.java:30) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:73) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:42) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:78) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:40) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:50) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:36) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:81) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:36) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:56) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:36) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.executeWithTimer(ApiCallTimeoutTrackingStage.java:80) > ~[sdk-core-2.17.198.jar:?] > at >
[jira] [Updated] (CAMEL-18145) camel-aws-secretsmanager - Test failure in rotateSecrets
[ https://issues.apache.org/jira/browse/CAMEL-18145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18145: Priority: Minor (was: Major) > camel-aws-secretsmanager - Test failure in rotateSecrets > > > Key: CAMEL-18145 > URL: https://issues.apache.org/jira/browse/CAMEL-18145 > Project: Camel > Issue Type: Test > Components: camel-aws >Affects Versions: 3.18.0 >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.18.0 > > > Message History (source location and message history is disabled) > --- > Source ID > Processor Elapsed (ms) > route6/route6 > from[direct://rotateSecret] 29 > ... > route6/to8 > aws-secrets-manager://test?operation=rotateSecret 0 > Stacktrace > --- > software.amazon.awssdk.services.secretsmanager.model.ResourceNotFoundException: > Lambda does not exist or could not be accessed (Service: SecretsManager, > Status Code: 400, Request ID: > KYCVGVN52HR0PX630EFH1HN44VH32JHHJC8DOFTB0GWO9LHG4OIO) > at > software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handleErrorResponse(CombinedResponseHandler.java:125) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handleResponse(CombinedResponseHandler.java:82) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handle(CombinedResponseHandler.java:60) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handle(CombinedResponseHandler.java:41) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.HandleResponseStage.execute(HandleResponseStage.java:40) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.HandleResponseStage.execute(HandleResponseStage.java:30) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:73) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:42) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:78) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:40) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:50) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:36) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:81) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:36) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:56) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:36) > ~[sdk-core-2.17.198.jar:?] > at > software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.executeWithTimer(ApiCallTimeoutTrackingStage.java:80) > ~[sdk-core-2.17.198.jar:?] > at >
[jira] [Created] (CAMEL-18145) camel-aws-secretsmanager - Test failure in rotateSecrets
Claus Ibsen created CAMEL-18145: --- Summary: camel-aws-secretsmanager - Test failure in rotateSecrets Key: CAMEL-18145 URL: https://issues.apache.org/jira/browse/CAMEL-18145 Project: Camel Issue Type: Test Components: camel-aws Affects Versions: 3.18.0 Reporter: Claus Ibsen Fix For: 3.18.0 Message History (source location and message history is disabled) --- Source ID Processor Elapsed (ms) route6/route6 from[direct://rotateSecret] 29 ... route6/to8 aws-secrets-manager://test?operation=rotateSecret 0 Stacktrace --- software.amazon.awssdk.services.secretsmanager.model.ResourceNotFoundException: Lambda does not exist or could not be accessed (Service: SecretsManager, Status Code: 400, Request ID: KYCVGVN52HR0PX630EFH1HN44VH32JHHJC8DOFTB0GWO9LHG4OIO) at software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handleErrorResponse(CombinedResponseHandler.java:125) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handleResponse(CombinedResponseHandler.java:82) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handle(CombinedResponseHandler.java:60) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handle(CombinedResponseHandler.java:41) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.pipeline.stages.HandleResponseStage.execute(HandleResponseStage.java:40) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.pipeline.stages.HandleResponseStage.execute(HandleResponseStage.java:30) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:73) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:42) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:78) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:40) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:50) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:36) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:81) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:36) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:56) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:36) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.executeWithTimer(ApiCallTimeoutTrackingStage.java:80) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:60) ~[sdk-core-2.17.198.jar:?] at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:42) ~[sdk-core-2.17.198.jar:?] at
[jira] [Updated] (CAMEL-18143) Autowire quartz scheduler in quartz component
[ https://issues.apache.org/jira/browse/CAMEL-18143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18143: Priority: Minor (was: Major) > Autowire quartz scheduler in quartz component > - > > Key: CAMEL-18143 > URL: https://issues.apache.org/jira/browse/CAMEL-18143 > Project: Camel > Issue Type: Improvement > Components: camel-quartz >Affects Versions: 3.17.0 >Reporter: Joe Siponen >Priority: Minor > Fix For: 3.x > > > I suggest that the [scheduler > option|https://camel.apache.org/components/3.17.x/quartz-component.html#_component_options] > is autowired for the quartz component. > The instructions for the QUARKUS BASED configuration of the quartz-component > seems to (implicitly) assume that it is: > [https://camel.apache.org/camel-quarkus/2.7.x/reference/extensions/quartz.html] > However, the documentation does not mark scheduler as being autowired so the > quarkus based documentation is not correct as it leaves out the part required > for wiring the quarkus provided scheduler with camel's quartz component. > However, one could argue that the sceduler should be autowired in order to > reduce the necessity for boilerplate code when there is clear candidate for > autowiring. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18143) Autowire quartz scheduler in quartz component
[ https://issues.apache.org/jira/browse/CAMEL-18143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18143: Fix Version/s: 3.x (was: Future) > Autowire quartz scheduler in quartz component > - > > Key: CAMEL-18143 > URL: https://issues.apache.org/jira/browse/CAMEL-18143 > Project: Camel > Issue Type: Improvement > Components: camel-quartz >Affects Versions: 3.17.0 >Reporter: Joe Siponen >Priority: Major > Fix For: 3.x > > > I suggest that the [scheduler > option|https://camel.apache.org/components/3.17.x/quartz-component.html#_component_options] > is autowired for the quartz component. > The instructions for the QUARKUS BASED configuration of the quartz-component > seems to (implicitly) assume that it is: > [https://camel.apache.org/camel-quarkus/2.7.x/reference/extensions/quartz.html] > However, the documentation does not mark scheduler as being autowired so the > quarkus based documentation is not correct as it leaves out the part required > for wiring the quarkus provided scheduler with camel's quartz component. > However, one could argue that the sceduler should be autowired in order to > reduce the necessity for boilerplate code when there is clear candidate for > autowiring. > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18144) camel-milo: Update Eclipse Milo from 0.3.7 to 0.6.6
[ https://issues.apache.org/jira/browse/CAMEL-18144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18144. - Resolution: Fixed > camel-milo: Update Eclipse Milo from 0.3.7 to 0.6.6 > --- > > Key: CAMEL-18144 > URL: https://issues.apache.org/jira/browse/CAMEL-18144 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-milo >Affects Versions: 3.17.0 >Reporter: Andreas Klug >Priority: Minor > Fix For: 3.18.0 > > > Update Eclipse Milo from 0.3.7 to 0.6.6. > Out of my perspective, there were significant changes, especially the timing > of the notifications (client subscription) seems to behave slightly different > using Eclipse Milo 0.6.6 (or is subject to a misunderstanding on my side), > e.g. there is an additional, early notification with a node value "null" > after route-startup, as at this time the node value hasn't been set yet. I > saw these kind of timing issues with 0.3.7, too, but less often. In order to > avoid changing the unit tests too much, I introduced a new omitNullValues > parameter on the client endpoint, which defaults to "true" in order to avoid > that notification and to avoid flaking unit tests, too. > Would be great if somebody out there with experience with Eclipse Milo could > test that in specific scenarios, too. -- This message was sent by Atlassian Jira (v8.20.7#820007)
