[jira] [Created] (CAMEL-19624) Upgrade Derby used for testing
Claus Ibsen created CAMEL-19624: --- Summary: Upgrade Derby used for testing Key: CAMEL-19624 URL: https://issues.apache.org/jira/browse/CAMEL-19624 Project: Camel Issue Type: Dependency upgrade Components: tests Reporter: Claus Ibsen org.apache.derby:derby ( from 10.14.2.0 to 10.16.1.1 ) It may be that embedded derby is changed a bit so the upgrade may require some changes in affected components -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19613) Convert components to use the camel-test-infra-core
[ https://issues.apache.org/jira/browse/CAMEL-19613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano Marcondes Machado updated CAMEL-19613: -- Description: As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a CamelContext into the tests. This moves the management of the context lifecycle to JUnit and can simplify debugging the code. Although it is not a drop-in replacement to the CamelTestSupport, a [conversion guide covering the basics of the process is available along with the test infra code|https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-core/README.md]. The following components need to be converted: - -camel-arangodb- - -camel-as2- - -camel-asn1- - camel-asterisk - camel-atmosphere-websocket - camel-atom - camel-attachments - camel-avro - camel-avro-rpc - camel-aws - camel-azure - camel-barcode - camel-base64 - camel-bean-validator - camel-bindy - camel-bonita - camel-box - camel-braintree - camel-caffeine - camel-cassandraql - camel-cbor - camel-chatscript - camel-chunk - camel-coap - camel-cometd - camel-consul - camel-corda - camel-couchbase - camel-couchdb - camel-cron - camel-crypto - camel-csimple-joor - camel-csv - camel-cxf - camel-datasonnet - camel-debezium - camel-dhis2 - camel-digitalocean - camel-disruptor - camel-djl - camel-dns - camel-docker - camel-drill - camel-dropbox - camel-dynamic-router - camel-ehcache - camel-elasticsearch - camel-elytron - camel-etcd3 - camel-exec - camel-facebook - camel-fastjson - camel-fhir - camel-file-watch - camel-flatpack - camel-flink - camel-fop - camel-freemarker - camel-ftp - camel-geocoder - camel-git - camel-github - camel-google - camel-graphql - camel-grok - camel-groovy - camel-grpc - camel-gson - camel-guava-eventbus - camel-hashicorp-vault - camel-hazelcast - camel-hdfs - camel-headersmap - camel-hl7 - camel-http - camel-http-common - camel-huawei - camel-hyperledger-aries - camel-ical - camel-iec60870 - camel-ignite - camel-infinispan - camel-influxdb - camel-influxdb2 - camel-irc - camel-ironmq - camel-jackson - camel-jackson-avro - camel-jackson-protobuf - camel-jacksonxml - camel-jasypt - camel-javascript - camel-jaxb - camel-jcache - camel-jcr - camel-jdbc - camel-jetty - camel-jgroups - camel-jgroups-raft - camel-jira - camel-jms - camel-jmx - camel-jolt - camel-jooq - camel-joor - camel-jpa - camel-jq - camel-jsch - camel-jslt - camel-json-patch - camel-json-validator - camel-jsonapi - camel-jsonata - camel-jsonb - camel-jsonpath - camel-jt400 - camel-kamelet - camel-kubernetes - camel-kudu - camel-ldif - camel-leveldb - camel-lra - camel-lucene - camel-lumberjack - camel-lzf - camel-mail - camel-mapstruct - camel-master - camel-metrics - camel-micrometer - camel-microprofile - camel-mina - camel-minio - camel-mllp - camel-mongodb - camel-mongodb-gridfs - camel-mustache - camel-mvel - camel-mybatis - camel-nats - camel-netty - camel-netty-http - camel-nitrite - camel-oaipmh - camel-observation - camel-ognl - camel-olingo2 - camel-olingo4 - camel-openapi-java - camel-opensearch - camel-openstack - camel-opentelemetry - camel-optaplanner - camel-paho - camel-paho-mqtt5 - camel-parquet-avro - camel-pdf - camel-pg-replication-slot - camel-pgevent - camel-platform-http-vertx - camel-plc4x - camel-printer - camel-protobuf - camel-pubnub - camel-pulsar - camel-python - camel-quartz - camel-quickfix - camel-reactive-executor-tomcat - camel-reactive-executor-vertx - camel-reactive-streams - camel-reactor - camel-redis - camel-resilience4j - camel-resourceresolver-github - camel-rest-openapi - camel-robotframework - camel-rocketmq - camel-rss - camel-rxjava - camel-salesforce - camel-sap-netweaver - camel-saxon - camel-schematron - camel-servicenow - camel-servlet - camel-shiro - camel-sjms - camel-sjms2 - camel-slack - camel-smpp - camel-snakeyaml - camel-snmp - camel-soap - camel-splunk - camel-splunk-hec - camel-spring-batch - camel-spring-jdbc - camel-spring-ldap - camel-spring-main - camel-spring-rabbitmq - camel-spring-redis - camel-spring-ws - camel-spring-xml - camel-sql - camel-ssh - camel-stax - camel-stitch - camel-stomp - camel-stream - camel-stringtemplate - camel-swift - camel-syslog - camel-tarfile - camel-telegram - camel-test - camel-threadpoolfactory-vertx - camel-thrift - camel-tika - camel-twilio - camel-twitter - camel-undertow - camel-undertow-spring-security - camel-univocity-parsers - camel-velocity - camel-vertx - camel-weather - camel-web3j - camel-webhook - camel-whatsapp - camel-wordpress - camel-workday - camel-xchange - camel-xj - camel-xmlsecurity - camel-xmpp - camel-xslt-saxon - camel-zeebe - camel-zendesk - camel-zip-deflater -
[jira] [Resolved] (CAMEL-19599) camel-jbang - Export to camel-main - Add support for Kubernetes
[ https://issues.apache.org/jira/browse/CAMEL-19599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19599. - Resolution: Fixed > camel-jbang - Export to camel-main - Add support for Kubernetes > --- > > Key: CAMEL-19599 > URL: https://issues.apache.org/jira/browse/CAMEL-19599 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0-RC2, 4.0.0 > > > It should be possible to export to plain Camel Main and have k8s supported > builds and manifests via well known maven plugins (jkube and jib). > This allows end users to choose CSB, CEQ or pure Camel. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19613) Convert components to use the camel-test-infra-core
[ https://issues.apache.org/jira/browse/CAMEL-19613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano Marcondes Machado updated CAMEL-19613: -- Description: As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a CamelContext into the tests. This moves the management of the context lifecycle to JUnit and can simplify debugging the code. Although it is not a drop-in replacement to the CamelTestSupport, a [conversion guide covering the basics of the process is available along with the test infra code|https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-core/README.md]. The following components need to be converted: - -camel-arangodb- - -camel-as2- - camel-asn1 - camel-asterisk - camel-atmosphere-websocket - camel-atom - camel-attachments - camel-avro - camel-avro-rpc - camel-aws - camel-azure - camel-barcode - camel-base64 - camel-bean-validator - camel-bindy - camel-bonita - camel-box - camel-braintree - camel-caffeine - camel-cassandraql - camel-cbor - camel-chatscript - camel-chunk - camel-coap - camel-cometd - camel-consul - camel-corda - camel-couchbase - camel-couchdb - camel-cron - camel-crypto - camel-csimple-joor - camel-csv - camel-cxf - camel-datasonnet - camel-debezium - camel-dhis2 - camel-digitalocean - camel-disruptor - camel-djl - camel-dns - camel-docker - camel-drill - camel-dropbox - camel-dynamic-router - camel-ehcache - camel-elasticsearch - camel-elytron - camel-etcd3 - camel-exec - camel-facebook - camel-fastjson - camel-fhir - camel-file-watch - camel-flatpack - camel-flink - camel-fop - camel-freemarker - camel-ftp - camel-geocoder - camel-git - camel-github - camel-google - camel-graphql - camel-grok - camel-groovy - camel-grpc - camel-gson - camel-guava-eventbus - camel-hashicorp-vault - camel-hazelcast - camel-hdfs - camel-headersmap - camel-hl7 - camel-http - camel-http-common - camel-huawei - camel-hyperledger-aries - camel-ical - camel-iec60870 - camel-ignite - camel-infinispan - camel-influxdb - camel-influxdb2 - camel-irc - camel-ironmq - camel-jackson - camel-jackson-avro - camel-jackson-protobuf - camel-jacksonxml - camel-jasypt - camel-javascript - camel-jaxb - camel-jcache - camel-jcr - camel-jdbc - camel-jetty - camel-jgroups - camel-jgroups-raft - camel-jira - camel-jms - camel-jmx - camel-jolt - camel-jooq - camel-joor - camel-jpa - camel-jq - camel-jsch - camel-jslt - camel-json-patch - camel-json-validator - camel-jsonapi - camel-jsonata - camel-jsonb - camel-jsonpath - camel-jt400 - camel-kamelet - camel-kubernetes - camel-kudu - camel-ldif - camel-leveldb - camel-lra - camel-lucene - camel-lumberjack - camel-lzf - camel-mail - camel-mapstruct - camel-master - camel-metrics - camel-micrometer - camel-microprofile - camel-mina - camel-minio - camel-mllp - camel-mongodb - camel-mongodb-gridfs - camel-mustache - camel-mvel - camel-mybatis - camel-nats - camel-netty - camel-netty-http - camel-nitrite - camel-oaipmh - camel-observation - camel-ognl - camel-olingo2 - camel-olingo4 - camel-openapi-java - camel-opensearch - camel-openstack - camel-opentelemetry - camel-optaplanner - camel-paho - camel-paho-mqtt5 - camel-parquet-avro - camel-pdf - camel-pg-replication-slot - camel-pgevent - camel-platform-http-vertx - camel-plc4x - camel-printer - camel-protobuf - camel-pubnub - camel-pulsar - camel-python - camel-quartz - camel-quickfix - camel-reactive-executor-tomcat - camel-reactive-executor-vertx - camel-reactive-streams - camel-reactor - camel-redis - camel-resilience4j - camel-resourceresolver-github - camel-rest-openapi - camel-robotframework - camel-rocketmq - camel-rss - camel-rxjava - camel-salesforce - camel-sap-netweaver - camel-saxon - camel-schematron - camel-servicenow - camel-servlet - camel-shiro - camel-sjms - camel-sjms2 - camel-slack - camel-smpp - camel-snakeyaml - camel-snmp - camel-soap - camel-splunk - camel-splunk-hec - camel-spring-batch - camel-spring-jdbc - camel-spring-ldap - camel-spring-main - camel-spring-rabbitmq - camel-spring-redis - camel-spring-ws - camel-spring-xml - camel-sql - camel-ssh - camel-stax - camel-stitch - camel-stomp - camel-stream - camel-stringtemplate - camel-swift - camel-syslog - camel-tarfile - camel-telegram - camel-test - camel-threadpoolfactory-vertx - camel-thrift - camel-tika - camel-twilio - camel-twitter - camel-undertow - camel-undertow-spring-security - camel-univocity-parsers - camel-velocity - camel-vertx - camel-weather - camel-web3j - camel-webhook - camel-whatsapp - camel-wordpress - camel-workday - camel-xchange - camel-xj - camel-xmlsecurity - camel-xmpp - camel-xslt-saxon - camel-zeebe - camel-zendesk - camel-zip-deflater -
[jira] [Comment Edited] (CAMEL-19599) camel-jbang - Export to camel-main - Add support for Kubernetes
[ https://issues.apache.org/jira/browse/CAMEL-19599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741993#comment-17741993 ] Claus Ibsen edited comment on CAMEL-19599 at 7/19/23 4:35 PM: -- TODO: health-check (probes) *SUB TICKET* TODO: docs in camel-jbang was (Author: davsclaus): TODO: health-check (probes) TODO: docs in camel-jbang > camel-jbang - Export to camel-main - Add support for Kubernetes > --- > > Key: CAMEL-19599 > URL: https://issues.apache.org/jira/browse/CAMEL-19599 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0-RC2, 4.0.0 > > > It should be possible to export to plain Camel Main and have k8s supported > builds and manifests via well known maven plugins (jkube and jib). > This allows end users to choose CSB, CEQ or pure Camel. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19623) camel-jbang - Export to camel-main - Add support for health probes
Claus Ibsen created CAMEL-19623: --- Summary: camel-jbang - Export to camel-main - Add support for health probes Key: CAMEL-19623 URL: https://issues.apache.org/jira/browse/CAMEL-19623 Project: Camel Issue Type: Sub-task Components: camel-jbang Reporter: Claus Ibsen This requires jkube to make it possible to generate yaml manifest for health probes for general apps (they have special for SB or Quarkus). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19369) camel-jbang - Trace command to have endpoint URI information
[ https://issues.apache.org/jira/browse/CAMEL-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19369: Fix Version/s: (was: 4.0-RC2) > 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 >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0.0 > > > 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] [Updated] (CAMEL-19588) camel-jbang - Starting via jbang --verbose should output more details on startup
[ https://issues.apache.org/jira/browse/CAMEL-19588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19588: Fix Version/s: (was: 4.0-RC2) > camel-jbang - Starting via jbang --verbose should output more details on > startup > > > Key: CAMEL-19588 > URL: https://issues.apache.org/jira/browse/CAMEL-19588 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0.0 > > > jbang has --verbose that outputs all sorts of stuff on startup. But it would > nice if camel-jbang and its dynamic downloader could also output in verbose > mode, about each JAR being resolving/resolved downloading/downloaded etc for > trouble shooting. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19619) Throttle when used in camel-kafka route creates thread leak
[ https://issues.apache.org/jira/browse/CAMEL-19619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19619. - Resolution: Information Provided > Throttle when used in camel-kafka route creates thread leak > --- > > Key: CAMEL-19619 > URL: https://issues.apache.org/jira/browse/CAMEL-19619 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.14.9 >Reporter: Kartik >Priority: Minor > Attachments: image-2023-07-19-19-33-10-591.png, > image-2023-07-19-19-33-33-151.png, image-2023-07-19-20-05-52-306.png > > > I have used throttle in the camel Kafka route to control the message flow and > I have 10 routes running initially there will be no throttle thread created > as soon as the message comes to the Kafka topic and read huge number of > throttle threads are created. > > For 10 routes I see 88 throttle "threads" threads created and are doing no > work. > > !image-2023-07-19-19-33-10-591.png! > > !image-2023-07-19-19-33-33-151.png! > > Stack trace of each throttle thread. > "Camel (InfaDefaultCamelContext) thread #51 - Throttle" #135 daemon prio=5 > os_prio=0 tid=0x01dfee834000 nid=0x2dbc waiting on condition > [0x00d5a2dff000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073da9aaf0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #50 - Throttle" #134 daemon prio=5 > os_prio=0 tid=0x01dfee835800 nid=0x71d4 waiting on condition > [0x00d5a2cfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073db8c0c0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #49 - Throttle" #133 daemon prio=5 > os_prio=0 tid=0x01dfee82b000 nid=0x5574 waiting on condition > [0x00d5a2bfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073de977d8> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable
[jira] [Commented] (CAMEL-19619) Throttle when used in camel-kafka route creates thread leak
[ https://issues.apache.org/jira/browse/CAMEL-19619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744704#comment-17744704 ] Claus Ibsen commented on CAMEL-19619: - Please use the user mailing list or chat room for discussing. JIRA is not intended for that. > Throttle when used in camel-kafka route creates thread leak > --- > > Key: CAMEL-19619 > URL: https://issues.apache.org/jira/browse/CAMEL-19619 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.14.9 >Reporter: Kartik >Priority: Minor > Attachments: image-2023-07-19-19-33-10-591.png, > image-2023-07-19-19-33-33-151.png, image-2023-07-19-20-05-52-306.png > > > I have used throttle in the camel Kafka route to control the message flow and > I have 10 routes running initially there will be no throttle thread created > as soon as the message comes to the Kafka topic and read huge number of > throttle threads are created. > > For 10 routes I see 88 throttle "threads" threads created and are doing no > work. > > !image-2023-07-19-19-33-10-591.png! > > !image-2023-07-19-19-33-33-151.png! > > Stack trace of each throttle thread. > "Camel (InfaDefaultCamelContext) thread #51 - Throttle" #135 daemon prio=5 > os_prio=0 tid=0x01dfee834000 nid=0x2dbc waiting on condition > [0x00d5a2dff000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073da9aaf0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #50 - Throttle" #134 daemon prio=5 > os_prio=0 tid=0x01dfee835800 nid=0x71d4 waiting on condition > [0x00d5a2cfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073db8c0c0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #49 - Throttle" #133 daemon prio=5 > os_prio=0 tid=0x01dfee82b000 nid=0x5574 waiting on condition > [0x00d5a2bfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073de977d8> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at >
[jira] [Updated] (CAMEL-19619) Throttle when used in camel-kafka route creates thread leak
[ https://issues.apache.org/jira/browse/CAMEL-19619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19619: Priority: Minor (was: Critical) > Throttle when used in camel-kafka route creates thread leak > --- > > Key: CAMEL-19619 > URL: https://issues.apache.org/jira/browse/CAMEL-19619 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.14.9 >Reporter: Kartik >Priority: Minor > Attachments: image-2023-07-19-19-33-10-591.png, > image-2023-07-19-19-33-33-151.png, image-2023-07-19-20-05-52-306.png > > > I have used throttle in the camel Kafka route to control the message flow and > I have 10 routes running initially there will be no throttle thread created > as soon as the message comes to the Kafka topic and read huge number of > throttle threads are created. > > For 10 routes I see 88 throttle "threads" threads created and are doing no > work. > > !image-2023-07-19-19-33-10-591.png! > > !image-2023-07-19-19-33-33-151.png! > > Stack trace of each throttle thread. > "Camel (InfaDefaultCamelContext) thread #51 - Throttle" #135 daemon prio=5 > os_prio=0 tid=0x01dfee834000 nid=0x2dbc waiting on condition > [0x00d5a2dff000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073da9aaf0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #50 - Throttle" #134 daemon prio=5 > os_prio=0 tid=0x01dfee835800 nid=0x71d4 waiting on condition > [0x00d5a2cfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073db8c0c0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #49 - Throttle" #133 daemon prio=5 > os_prio=0 tid=0x01dfee82b000 nid=0x5574 waiting on condition > [0x00d5a2bfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073de977d8> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable
[jira] [Resolved] (CAMEL-19615) camel-ftp: chmodDirectory option try for each junk to change the directory permission and fails
[
https://issues.apache.org/jira/browse/CAMEL-19615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-19615.
-
Resolution: Fixed
Thanks for the PR
> camel-ftp: chmodDirectory option try for each junk to change the directory
> permission and fails
> ---
>
> Key: CAMEL-19615
> URL: https://issues.apache.org/jira/browse/CAMEL-19615
> Project: Camel
> Issue Type: Improvement
> Components: camel-sftp
>Affects Versions: 3.18.2
>Reporter: Michael Rambichler
>Priority: Major
> Fix For: 3.14.10, 3.20.7, 3.21.1, 3.22.0, 4.0-RC2, 4.0.0
>
>
> We have a blocking issue with the current chmodDirectory option.
> [https://camel.apache.org/components/3.20.x/sftp-component.html#_endpoint_query_option_chmodDirectory]
>
> *Steps to reproduce:*
> SFTP Directory: ../home/user/restricted/dir/subdir (where restricted e.g.
> does not have change rights for the current user)
> Component Call:
> "sftp://localhost:21/home/user/restricted/dir/subdir/newDir; +
> "?username=admin=admin=777=770"
>
> *Behaviour:*
> The current implementation steps down the directory and try to create each
> junk. If the chmodDirectory option is set then i{color:#FF}t will try for
> each (already existing junk) to change the directory permission and
> fails.{color}
>
> *Expected Behaviour:*
> It should only try to change the permission if the directory does not yet
> exists
>
> I have already created a fix and added a Testcase for better debugging (but
> the Testcase does not reproduce the error because it would remove the
> permission for the current user and afterwards your need root rights to
> delete the Testdirectory again. Not suitable pipeline builds)
> [https://github.com/michael-salzburg/camel]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19613) Convert components to use the camel-test-infra-core
[ https://issues.apache.org/jira/browse/CAMEL-19613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-19613: - Description: As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a CamelContext into the tests. This moves the management of the context lifecycle to JUnit and can simplify debugging the code. Although it is not a drop-in replacement to the CamelTestSupport, a [conversion guide covering the basics of the process is available along with the test infra code|https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-core/README.md]. The following components need to be converted: - -camel-arangodb- - -camel-as2- - camel-asn1 - camel-asterisk - camel-atmosphere-websocket - camel-atom - camel-attachments - camel-avro - camel-avro-rpc - camel-aws - camel-azure - camel-barcode - camel-base64 - camel-bean-validator - camel-bindy - camel-bonita - camel-box - camel-braintree - camel-caffeine - In Progress - camel-cassandraql - camel-cbor - camel-chatscript - camel-chunk - camel-coap - camel-cometd - camel-consul - camel-corda - camel-couchbase - camel-couchdb - camel-cron - camel-crypto - camel-csimple-joor - camel-csv - camel-cxf - camel-datasonnet - camel-debezium - camel-dhis2 - camel-digitalocean - camel-disruptor - camel-djl - camel-dns - camel-docker - camel-drill - camel-dropbox - camel-dynamic-router - camel-ehcache - camel-elasticsearch - camel-elytron - camel-etcd3 - camel-exec - camel-facebook - camel-fastjson - camel-fhir - camel-file-watch - camel-flatpack - camel-flink - camel-fop - camel-freemarker - camel-ftp - camel-geocoder - camel-git - camel-github - camel-google - camel-graphql - camel-grok - camel-groovy - camel-grpc - camel-gson - camel-guava-eventbus - camel-hashicorp-vault - camel-hazelcast - camel-hdfs - camel-headersmap - camel-hl7 - camel-http - camel-http-common - camel-huawei - camel-hyperledger-aries - camel-ical - camel-iec60870 - camel-ignite - camel-infinispan - camel-influxdb - camel-influxdb2 - camel-irc - camel-ironmq - camel-jackson - camel-jackson-avro - camel-jackson-protobuf - camel-jacksonxml - camel-jasypt - camel-javascript - camel-jaxb - camel-jcache - camel-jcr - camel-jdbc - camel-jetty - camel-jgroups - camel-jgroups-raft - camel-jira - camel-jms - camel-jmx - camel-jolt - camel-jooq - camel-joor - camel-jpa - camel-jq - camel-jsch - camel-jslt - camel-json-patch - camel-json-validator - camel-jsonapi - camel-jsonata - camel-jsonb - camel-jsonpath - camel-jt400 - camel-kamelet - camel-kubernetes - camel-kudu - camel-ldif - camel-leveldb - camel-lra - camel-lucene - camel-lumberjack - camel-lzf - camel-mail - camel-mapstruct - camel-master - camel-metrics - camel-micrometer - camel-microprofile - camel-mina - camel-minio - camel-mllp - camel-mongodb - camel-mongodb-gridfs - camel-mustache - camel-mvel - camel-mybatis - camel-nats - camel-netty - camel-netty-http - camel-nitrite - camel-oaipmh - camel-observation - camel-ognl - camel-olingo2 - camel-olingo4 - camel-openapi-java - camel-opensearch - camel-openstack - camel-opentelemetry - camel-optaplanner - camel-paho - camel-paho-mqtt5 - camel-parquet-avro - camel-pdf - camel-pg-replication-slot - camel-pgevent - camel-platform-http-vertx - camel-plc4x - camel-printer - camel-protobuf - camel-pubnub - camel-pulsar - camel-python - camel-quartz - camel-quickfix - camel-reactive-executor-tomcat - camel-reactive-executor-vertx - camel-reactive-streams - camel-reactor - camel-redis - camel-resilience4j - camel-resourceresolver-github - camel-rest-openapi - camel-robotframework - camel-rocketmq - camel-rss - camel-rxjava - camel-salesforce - camel-sap-netweaver - camel-saxon - camel-schematron - camel-servicenow - camel-servlet - camel-shiro - camel-sjms - camel-sjms2 - camel-slack - camel-smpp - camel-snakeyaml - camel-snmp - camel-soap - camel-splunk - camel-splunk-hec - camel-spring-batch - camel-spring-jdbc - camel-spring-ldap - camel-spring-main - camel-spring-rabbitmq - camel-spring-redis - camel-spring-ws - camel-spring-xml - camel-sql - camel-ssh - camel-stax - camel-stitch - camel-stomp - camel-stream - camel-stringtemplate - camel-swift - camel-syslog - camel-tarfile - camel-telegram - camel-test - camel-threadpoolfactory-vertx - camel-thrift - camel-tika - camel-twilio - camel-twitter - camel-undertow - camel-undertow-spring-security - camel-univocity-parsers - camel-velocity - camel-vertx - camel-weather - camel-web3j - camel-webhook - camel-whatsapp - camel-wordpress - camel-workday - camel-xchange - camel-xj - camel-xmlsecurity - camel-xmpp - camel-xslt-saxon - camel-zeebe - camel-zendesk - camel-zip-deflater - camel-zipfile
[jira] [Commented] (CAMEL-19619) Throttle when used in camel-kafka route creates thread leak
[ https://issues.apache.org/jira/browse/CAMEL-19619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744662#comment-17744662 ] Kartik commented on CAMEL-19619: So according to you, each route will spin 2 thread pool each with 10 threads as we have 2 throttles; also I want to know why the thread is needed for throttling. we can use one polling thread at regular intervals which resumes the consumer if time has elapsed and the consumer will block itself if exceeded the limit after processing the exchange. Also can't we use something like Quartz scheduler triggers? Looks like an enhancement to me. Meanwhile, if I provide a shared thread pool with 4 threads in the pool and 4 of my user consumes more messages than allowed and are blocked what happens to the 5th user when he/she exhausts the allowed limit as there are no thread to handle? > Throttle when used in camel-kafka route creates thread leak > --- > > Key: CAMEL-19619 > URL: https://issues.apache.org/jira/browse/CAMEL-19619 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.14.9 >Reporter: Kartik >Priority: Critical > Attachments: image-2023-07-19-19-33-10-591.png, > image-2023-07-19-19-33-33-151.png, image-2023-07-19-20-05-52-306.png > > > I have used throttle in the camel Kafka route to control the message flow and > I have 10 routes running initially there will be no throttle thread created > as soon as the message comes to the Kafka topic and read huge number of > throttle threads are created. > > For 10 routes I see 88 throttle "threads" threads created and are doing no > work. > > !image-2023-07-19-19-33-10-591.png! > > !image-2023-07-19-19-33-33-151.png! > > Stack trace of each throttle thread. > "Camel (InfaDefaultCamelContext) thread #51 - Throttle" #135 daemon prio=5 > os_prio=0 tid=0x01dfee834000 nid=0x2dbc waiting on condition > [0x00d5a2dff000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073da9aaf0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #50 - Throttle" #134 daemon prio=5 > os_prio=0 tid=0x01dfee835800 nid=0x71d4 waiting on condition > [0x00d5a2cfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073db8c0c0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #49 - Throttle" #133 daemon prio=5 > os_prio=0 tid=0x01dfee82b000 nid=0x5574 waiting on condition > [0x00d5a2bfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073de977d8> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at >
[jira] [Updated] (CAMEL-19622) Convert DSLs to use the camel-test-infra-core
[ https://issues.apache.org/jira/browse/CAMEL-19622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-19622: - Description: As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a CamelContext into the tests. This moves the management of the context lifecycle to JUnit and can simplify debugging the code. Although it is not a drop-in replacement to the CamelTestSupport, a [conversion guide covering the basics of the process is available along with the test infra code|https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-core/README.md]. The following components need to be converted: - camel-componentdsl - camel-endpointdsl - camel-dsl-modeline - camel-xml-io-dsl - IN PROGRESS was: As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a CamelContext into the tests. This moves the management of the context lifecycle to JUnit and can simplify debugging the code. Although it is not a drop-in replacement to the CamelTestSupport, a [conversion guide covering the basics of the process is available along with the test infra code|https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-core/README.md]. The following components need to be converted: - > Convert DSLs to use the camel-test-infra-core > - > > Key: CAMEL-19622 > URL: https://issues.apache.org/jira/browse/CAMEL-19622 > Project: Camel > Issue Type: Test > Components: camel-test-infra-core >Affects Versions: 4.0.0 >Reporter: Otavio Rodolfo Piske >Priority: Major > Labels: easy, help-wanted > > As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a > CamelContext into the tests. This moves the management of the context > lifecycle to JUnit and can simplify debugging the code. Although it is not a > drop-in replacement to the CamelTestSupport, a [conversion guide covering the > basics of the process is available along with the test infra > code|https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-core/README.md]. > > The following components need to be converted: > - camel-componentdsl > - camel-endpointdsl > - camel-dsl-modeline > - camel-xml-io-dsl - IN PROGRESS -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19622) Convert DSLs to use the camel-test-infra-core
[ https://issues.apache.org/jira/browse/CAMEL-19622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-19622: - Description: As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a CamelContext into the tests. This moves the management of the context lifecycle to JUnit and can simplify debugging the code. Although it is not a drop-in replacement to the CamelTestSupport, a [conversion guide covering the basics of the process is available along with the test infra code|https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-core/README.md]. The following components need to be converted: - was: As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a CamelContext into the tests. This moves the management of the context lifecycle to JUnit and can simplify debugging the code. Although it is not a drop-in replacement to the CamelTestSupport, a [conversion guide covering the basics of the process is available along with the test infra code|https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-core/README.md]. The following components need to be converted: - -camel-arangodb- - camel-as2 - IN PROGRESS - camel-asn1 - camel-asterisk - camel-atmosphere-websocket - camel-atom - camel-attachments - camel-avro - camel-avro-rpc - camel-aws - camel-azure - camel-barcode - camel-base64 - camel-bean-validator - camel-bindy - camel-bonita - camel-box - camel-braintree - camel-caffeine - In Progress - camel-cassandraql - camel-cbor - camel-chatscript - camel-chunk - camel-coap - camel-cometd - camel-consul - camel-corda - camel-couchbase - camel-couchdb - camel-cron - camel-crypto - camel-csimple-joor - camel-csv - camel-cxf - camel-datasonnet - camel-debezium - camel-dhis2 - camel-digitalocean - camel-disruptor - camel-djl - camel-dns - camel-docker - camel-drill - camel-dropbox - camel-dynamic-router - camel-ehcache - camel-elasticsearch - camel-elytron - camel-etcd3 - camel-exec - camel-facebook - camel-fastjson - camel-fhir - camel-file-watch - camel-flatpack - camel-flink - camel-fop - camel-freemarker - camel-ftp - camel-geocoder - camel-git - camel-github - camel-google - camel-graphql - camel-grok - camel-groovy - camel-grpc - camel-gson - camel-guava-eventbus - camel-hashicorp-vault - camel-hazelcast - camel-hdfs - camel-headersmap - camel-hl7 - camel-http - camel-http-common - camel-huawei - camel-hyperledger-aries - camel-ical - camel-iec60870 - camel-ignite - camel-infinispan - camel-influxdb - camel-influxdb2 - camel-irc - camel-ironmq - camel-jackson - camel-jackson-avro - camel-jackson-protobuf - camel-jacksonxml - camel-jasypt - camel-javascript - camel-jaxb - camel-jcache - camel-jcr - camel-jdbc - camel-jetty - camel-jgroups - camel-jgroups-raft - camel-jira - camel-jms - camel-jmx - camel-jolt - camel-jooq - camel-joor - camel-jpa - camel-jq - camel-jsch - camel-jslt - camel-json-patch - camel-json-validator - camel-jsonapi - camel-jsonata - camel-jsonb - camel-jsonpath - camel-jt400 - camel-kamelet - camel-kubernetes - camel-kudu - camel-ldif - camel-leveldb - camel-lra - camel-lucene - camel-lumberjack - camel-lzf - camel-mail - camel-mapstruct - camel-master - camel-metrics - camel-micrometer - camel-microprofile - camel-mina - camel-minio - camel-mllp - camel-mongodb - camel-mongodb-gridfs - camel-mustache - camel-mvel - camel-mybatis - camel-nats - camel-netty - camel-netty-http - camel-nitrite - camel-oaipmh - camel-observation - camel-ognl - camel-olingo2 - camel-olingo4 - camel-openapi-java - camel-opensearch - camel-openstack - camel-opentelemetry - camel-optaplanner - camel-paho - camel-paho-mqtt5 - camel-parquet-avro - camel-pdf - camel-pg-replication-slot - camel-pgevent - camel-platform-http-vertx - camel-plc4x - camel-printer - camel-protobuf - camel-pubnub - camel-pulsar - camel-python - camel-quartz - camel-quickfix - camel-reactive-executor-tomcat - camel-reactive-executor-vertx - camel-reactive-streams - camel-reactor - camel-redis - camel-resilience4j - camel-resourceresolver-github - camel-rest-openapi - camel-robotframework - camel-rocketmq - camel-rss - camel-rxjava - camel-salesforce - camel-sap-netweaver - camel-saxon - camel-schematron - camel-servicenow - camel-servlet - camel-shiro - camel-sjms - camel-sjms2 - camel-slack - camel-smpp - camel-snakeyaml - camel-snmp - camel-soap - camel-splunk - camel-splunk-hec - camel-spring-batch - camel-spring-jdbc - camel-spring-ldap - camel-spring-main - camel-spring-rabbitmq - camel-spring-redis - camel-spring-ws - camel-spring-xml - camel-sql - camel-ssh - camel-stax - camel-stitch - camel-stomp - camel-stream - camel-stringtemplate -
[jira] [Created] (CAMEL-19622) Convert DSLs to use the camel-test-infra-core
Otavio Rodolfo Piske created CAMEL-19622: Summary: Convert DSLs to use the camel-test-infra-core Key: CAMEL-19622 URL: https://issues.apache.org/jira/browse/CAMEL-19622 Project: Camel Issue Type: Test Components: camel-test-infra-core Affects Versions: 4.0.0 Reporter: Otavio Rodolfo Piske As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a CamelContext into the tests. This moves the management of the context lifecycle to JUnit and can simplify debugging the code. Although it is not a drop-in replacement to the CamelTestSupport, a [conversion guide covering the basics of the process is available along with the test infra code|https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-core/README.md]. The following components need to be converted: - -camel-arangodb- - camel-as2 - IN PROGRESS - camel-asn1 - camel-asterisk - camel-atmosphere-websocket - camel-atom - camel-attachments - camel-avro - camel-avro-rpc - camel-aws - camel-azure - camel-barcode - camel-base64 - camel-bean-validator - camel-bindy - camel-bonita - camel-box - camel-braintree - camel-caffeine - In Progress - camel-cassandraql - camel-cbor - camel-chatscript - camel-chunk - camel-coap - camel-cometd - camel-consul - camel-corda - camel-couchbase - camel-couchdb - camel-cron - camel-crypto - camel-csimple-joor - camel-csv - camel-cxf - camel-datasonnet - camel-debezium - camel-dhis2 - camel-digitalocean - camel-disruptor - camel-djl - camel-dns - camel-docker - camel-drill - camel-dropbox - camel-dynamic-router - camel-ehcache - camel-elasticsearch - camel-elytron - camel-etcd3 - camel-exec - camel-facebook - camel-fastjson - camel-fhir - camel-file-watch - camel-flatpack - camel-flink - camel-fop - camel-freemarker - camel-ftp - camel-geocoder - camel-git - camel-github - camel-google - camel-graphql - camel-grok - camel-groovy - camel-grpc - camel-gson - camel-guava-eventbus - camel-hashicorp-vault - camel-hazelcast - camel-hdfs - camel-headersmap - camel-hl7 - camel-http - camel-http-common - camel-huawei - camel-hyperledger-aries - camel-ical - camel-iec60870 - camel-ignite - camel-infinispan - camel-influxdb - camel-influxdb2 - camel-irc - camel-ironmq - camel-jackson - camel-jackson-avro - camel-jackson-protobuf - camel-jacksonxml - camel-jasypt - camel-javascript - camel-jaxb - camel-jcache - camel-jcr - camel-jdbc - camel-jetty - camel-jgroups - camel-jgroups-raft - camel-jira - camel-jms - camel-jmx - camel-jolt - camel-jooq - camel-joor - camel-jpa - camel-jq - camel-jsch - camel-jslt - camel-json-patch - camel-json-validator - camel-jsonapi - camel-jsonata - camel-jsonb - camel-jsonpath - camel-jt400 - camel-kamelet - camel-kubernetes - camel-kudu - camel-ldif - camel-leveldb - camel-lra - camel-lucene - camel-lumberjack - camel-lzf - camel-mail - camel-mapstruct - camel-master - camel-metrics - camel-micrometer - camel-microprofile - camel-mina - camel-minio - camel-mllp - camel-mongodb - camel-mongodb-gridfs - camel-mustache - camel-mvel - camel-mybatis - camel-nats - camel-netty - camel-netty-http - camel-nitrite - camel-oaipmh - camel-observation - camel-ognl - camel-olingo2 - camel-olingo4 - camel-openapi-java - camel-opensearch - camel-openstack - camel-opentelemetry - camel-optaplanner - camel-paho - camel-paho-mqtt5 - camel-parquet-avro - camel-pdf - camel-pg-replication-slot - camel-pgevent - camel-platform-http-vertx - camel-plc4x - camel-printer - camel-protobuf - camel-pubnub - camel-pulsar - camel-python - camel-quartz - camel-quickfix - camel-reactive-executor-tomcat - camel-reactive-executor-vertx - camel-reactive-streams - camel-reactor - camel-redis - camel-resilience4j - camel-resourceresolver-github - camel-rest-openapi - camel-robotframework - camel-rocketmq - camel-rss - camel-rxjava - camel-salesforce - camel-sap-netweaver - camel-saxon - camel-schematron - camel-servicenow - camel-servlet - camel-shiro - camel-sjms - camel-sjms2 - camel-slack - camel-smpp - camel-snakeyaml - camel-snmp - camel-soap - camel-splunk - camel-splunk-hec - camel-spring-batch - camel-spring-jdbc - camel-spring-ldap - camel-spring-main - camel-spring-rabbitmq - camel-spring-redis - camel-spring-ws - camel-spring-xml - camel-sql - camel-ssh - camel-stax - camel-stitch - camel-stomp - camel-stream - camel-stringtemplate - camel-swift - camel-syslog - camel-tarfile - camel-telegram - camel-test - camel-threadpoolfactory-vertx - camel-thrift - camel-tika - camel-twilio - camel-twitter - camel-undertow - camel-undertow-spring-security - camel-univocity-parsers - camel-velocity - camel-vertx - camel-weather - camel-web3j -
[jira] [Resolved] (CAMEL-19621) camel-elytron - Deprecate this component
[ https://issues.apache.org/jira/browse/CAMEL-19621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19621. - Resolution: Fixed > camel-elytron - Deprecate this component > > > Key: CAMEL-19621 > URL: https://issues.apache.org/jira/browse/CAMEL-19621 > Project: Camel > Issue Type: Task > Components: camel-undertow >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0-RC2, 4.0.0 > > > This component is not really much in use, and has no use in SB or Quarkus and > in modern apps. Its difficult to maintain as its use the huge complex > elytryon project that are tied to EAP/WildFly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19621) camel-elytron - Deprecate this component
Claus Ibsen created CAMEL-19621: --- Summary: camel-elytron - Deprecate this component Key: CAMEL-19621 URL: https://issues.apache.org/jira/browse/CAMEL-19621 Project: Camel Issue Type: Task Components: camel-undertow Reporter: Claus Ibsen Fix For: 4.0-RC2, 4.0.0 This component is not really much in use, and has no use in SB or Quarkus and in modern apps. Its difficult to maintain as its use the huge complex elytryon project that are tied to EAP/WildFly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19619) Throttle when used in camel-kafka route creates thread leak
[ https://issues.apache.org/jira/browse/CAMEL-19619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744648#comment-17744648 ] Claus Ibsen commented on CAMEL-19619: - Well each throttler has a thread pool (scheduled) that by default has 10 core threads. You can configure this see the threading docs - or provide a shared thread pool for them to reuse. > Throttle when used in camel-kafka route creates thread leak > --- > > Key: CAMEL-19619 > URL: https://issues.apache.org/jira/browse/CAMEL-19619 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.14.9 >Reporter: Kartik >Priority: Critical > Attachments: image-2023-07-19-19-33-10-591.png, > image-2023-07-19-19-33-33-151.png, image-2023-07-19-20-05-52-306.png > > > I have used throttle in the camel Kafka route to control the message flow and > I have 10 routes running initially there will be no throttle thread created > as soon as the message comes to the Kafka topic and read huge number of > throttle threads are created. > > For 10 routes I see 88 throttle "threads" threads created and are doing no > work. > > !image-2023-07-19-19-33-10-591.png! > > !image-2023-07-19-19-33-33-151.png! > > Stack trace of each throttle thread. > "Camel (InfaDefaultCamelContext) thread #51 - Throttle" #135 daemon prio=5 > os_prio=0 tid=0x01dfee834000 nid=0x2dbc waiting on condition > [0x00d5a2dff000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073da9aaf0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #50 - Throttle" #134 daemon prio=5 > os_prio=0 tid=0x01dfee835800 nid=0x71d4 waiting on condition > [0x00d5a2cfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073db8c0c0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #49 - Throttle" #133 daemon prio=5 > os_prio=0 tid=0x01dfee82b000 nid=0x5574 waiting on condition > [0x00d5a2bfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073de977d8> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at >
[jira] [Updated] (CAMEL-19613) Convert components to use the camel-test-infra-core
[ https://issues.apache.org/jira/browse/CAMEL-19613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-19613: - Description: As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a CamelContext into the tests. This moves the management of the context lifecycle to JUnit and can simplify debugging the code. Although it is not a drop-in replacement to the CamelTestSupport, a [conversion guide covering the basics of the process is available along with the test infra code|https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-core/README.md]. The following components need to be converted: - -camel-arangodb- - camel-as2 - IN PROGRESS - camel-asn1 - camel-asterisk - camel-atmosphere-websocket - camel-atom - camel-attachments - camel-avro - camel-avro-rpc - camel-aws - camel-azure - camel-barcode - camel-base64 - camel-bean-validator - camel-bindy - camel-bonita - camel-box - camel-braintree - camel-caffeine - In Progress - camel-cassandraql - camel-cbor - camel-chatscript - camel-chunk - camel-coap - camel-cometd - camel-consul - camel-corda - camel-couchbase - camel-couchdb - camel-cron - camel-crypto - camel-csimple-joor - camel-csv - camel-cxf - camel-datasonnet - camel-debezium - camel-dhis2 - camel-digitalocean - camel-disruptor - camel-djl - camel-dns - camel-docker - camel-drill - camel-dropbox - camel-dynamic-router - camel-ehcache - camel-elasticsearch - camel-elytron - camel-etcd3 - camel-exec - camel-facebook - camel-fastjson - camel-fhir - camel-file-watch - camel-flatpack - camel-flink - camel-fop - camel-freemarker - camel-ftp - camel-geocoder - camel-git - camel-github - camel-google - camel-graphql - camel-grok - camel-groovy - camel-grpc - camel-gson - camel-guava-eventbus - camel-hashicorp-vault - camel-hazelcast - camel-hdfs - camel-headersmap - camel-hl7 - camel-http - camel-http-common - camel-huawei - camel-hyperledger-aries - camel-ical - camel-iec60870 - camel-ignite - camel-infinispan - camel-influxdb - camel-influxdb2 - camel-irc - camel-ironmq - camel-jackson - camel-jackson-avro - camel-jackson-protobuf - camel-jacksonxml - camel-jasypt - camel-javascript - camel-jaxb - camel-jcache - camel-jcr - camel-jdbc - camel-jetty - camel-jgroups - camel-jgroups-raft - camel-jira - camel-jms - camel-jmx - camel-jolt - camel-jooq - camel-joor - camel-jpa - camel-jq - camel-jsch - camel-jslt - camel-json-patch - camel-json-validator - camel-jsonapi - camel-jsonata - camel-jsonb - camel-jsonpath - camel-jt400 - camel-kamelet - camel-kubernetes - camel-kudu - camel-ldif - camel-leveldb - camel-lra - camel-lucene - camel-lumberjack - camel-lzf - camel-mail - camel-mapstruct - camel-master - camel-metrics - camel-micrometer - camel-microprofile - camel-mina - camel-minio - camel-mllp - camel-mongodb - camel-mongodb-gridfs - camel-mustache - camel-mvel - camel-mybatis - camel-nats - camel-netty - camel-netty-http - camel-nitrite - camel-oaipmh - camel-observation - camel-ognl - camel-olingo2 - camel-olingo4 - camel-openapi-java - camel-opensearch - camel-openstack - camel-opentelemetry - camel-optaplanner - camel-paho - camel-paho-mqtt5 - camel-parquet-avro - camel-pdf - camel-pg-replication-slot - camel-pgevent - camel-platform-http-vertx - camel-plc4x - camel-printer - camel-protobuf - camel-pubnub - camel-pulsar - camel-python - camel-quartz - camel-quickfix - camel-reactive-executor-tomcat - camel-reactive-executor-vertx - camel-reactive-streams - camel-reactor - camel-redis - camel-resilience4j - camel-resourceresolver-github - camel-rest-openapi - camel-robotframework - camel-rocketmq - camel-rss - camel-rxjava - camel-salesforce - camel-sap-netweaver - camel-saxon - camel-schematron - camel-servicenow - camel-servlet - camel-shiro - camel-sjms - camel-sjms2 - camel-slack - camel-smpp - camel-snakeyaml - camel-snmp - camel-soap - camel-splunk - camel-splunk-hec - camel-spring-batch - camel-spring-jdbc - camel-spring-ldap - camel-spring-main - camel-spring-rabbitmq - camel-spring-redis - camel-spring-ws - camel-spring-xml - camel-sql - camel-ssh - camel-stax - camel-stitch - camel-stomp - camel-stream - camel-stringtemplate - camel-swift - camel-syslog - camel-tarfile - camel-telegram - camel-test - camel-threadpoolfactory-vertx - camel-thrift - camel-tika - camel-twilio - camel-twitter - camel-undertow - camel-undertow-spring-security - camel-univocity-parsers - camel-velocity - camel-vertx - camel-weather - camel-web3j - camel-webhook - camel-whatsapp - camel-wordpress - camel-workday - camel-xchange - camel-xj - camel-xmlsecurity - camel-xmpp - camel-xslt-saxon - camel-zeebe - camel-zendesk - camel-zip-deflater
[jira] [Comment Edited] (CAMEL-19619) Throttle when used in camel-kafka route creates thread leak
[
https://issues.apache.org/jira/browse/CAMEL-19619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744639#comment-17744639
]
Kartik edited comment on CAMEL-19619 at 7/19/23 2:37 PM:
-
{code:java}
// code placeholder
from(aEndpoint)
.routeId(aRouteId)
.autoStartup(false)
.setProperty(ICamelConstants.CAMEL_ROUTE_CONFIG_MAP,
constant(aRouteConfigMap))
.throttle(new ExpressionAdapter()
{
/**
* @param exchange
* @return Allowed count
*/
@Override
public Object evaluate(Exchange exchange)
{
return
OnethrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_COUNT, 5000);
}
}, new ExpressionAdapter()
{
/**
* @param exchange Camel exchange
* @return for correlation
*/
@Override
public Object evaluate(Exchange exchange)
{
return aRouteConfigMap.getOrDefault(ICamelConstants.USER,
"default");
}
})
.asyncDelayed((Boolean)
OnethrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_IS_ASYNC_DELAYED,
true))
.timePeriodMillis((Integer)
OnethrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_TIME_PERIOD_MILLIS,
1000 * 60))
.throttle(new ExpressionAdapter()
{
@Override
public Object evaluate(Exchange exchange)
{
return
TwothrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_COUNT, 100);
}
})
.asyncDelayed((Boolean)
TwothrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_IS_ASYNC_DELAYED,
true))
.timePeriodMillis((Integer)
TwothrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_TIME_PERIOD_MILLIS,
1000 * 60))
.process((AsyncProcessor)
aRouteConfigMap.get(ICamelConstants.IDEMPOTENCY_HEADER_GENERATE_PROCESSOR))
.idempotentConsumer(header(ICamelConstants.MESSAGE_ID),
(IdempotentRepository)
aRouteConfigMap.get(ICamelConstants.IDEMPOTENT_REPOSITORY)); {code}
"aEndpoint" is a function argument that is constructed using "Kafka" component
by passing all topic and broker information.
So we have 2 throttles injected in route one is at the user level which uses
"username" to correlate and group it and another at each connection.
!image-2023-07-19-20-05-52-306.png|width=429,height=210!
We can have multiple users who starts multiple routes so to provide fair
resource to all, we have 2 level throttle first one at user level which is
limited to 5000 messages and each route under this is given 100 message.
was (Author: kartikvk1996):
{code:java}
// code placeholder
from(aEndpoint)
.routeId(aRouteId)
.autoStartup(false)
.setProperty(ICamelConstants.CAMEL_ROUTE_CONFIG_MAP,
constant(aRouteConfigMap))
.throttle(new ExpressionAdapter()
{
/**
* @param exchange
* @return Allowed count
*/
@Override
public Object evaluate(Exchange exchange)
{
return
OnethrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_COUNT, 5000);
}
}, new ExpressionAdapter()
{
/**
* @param exchange Camel exchange
* @return for correlation
*/
@Override
public Object evaluate(Exchange exchange)
{
return aRouteConfigMap.getOrDefault(ICamelConstants.USER,
"default");
}
})
.asyncDelayed((Boolean)
OnethrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_IS_ASYNC_DELAYED,
true))
.timePeriodMillis((Integer)
OnethrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_TIME_PERIOD_MILLIS,
1000 * 60))
.throttle(new ExpressionAdapter()
{
@Override
public Object evaluate(Exchange exchange)
{
return
TwothrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_COUNT, 100);
}
})
.asyncDelayed((Boolean)
TwothrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_IS_ASYNC_DELAYED,
true))
.timePeriodMillis((Integer)
TwothrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_TIME_PERIOD_MILLIS,
1000 * 60))
[jira] [Commented] (CAMEL-19619) Throttle when used in camel-kafka route creates thread leak
[
https://issues.apache.org/jira/browse/CAMEL-19619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744639#comment-17744639
]
Kartik commented on CAMEL-19619:
{code:java}
// code placeholder
from(aEndpoint)
.routeId(aRouteId)
.autoStartup(false)
.setProperty(ICamelConstants.CAMEL_ROUTE_CONFIG_MAP,
constant(aRouteConfigMap))
.throttle(new ExpressionAdapter()
{
/**
* @param exchange
* @return Allowed count
*/
@Override
public Object evaluate(Exchange exchange)
{
return
OnethrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_COUNT, 5000);
}
}, new ExpressionAdapter()
{
/**
* @param exchange Camel exchange
* @return for correlation
*/
@Override
public Object evaluate(Exchange exchange)
{
return aRouteConfigMap.getOrDefault(ICamelConstants.USER,
"default");
}
})
.asyncDelayed((Boolean)
OnethrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_IS_ASYNC_DELAYED,
true))
.timePeriodMillis((Integer)
OnethrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_TIME_PERIOD_MILLIS,
1000 * 60))
.throttle(new ExpressionAdapter()
{
@Override
public Object evaluate(Exchange exchange)
{
return
TwothrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_COUNT, 100);
}
})
.asyncDelayed((Boolean)
TwothrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_IS_ASYNC_DELAYED,
true))
.timePeriodMillis((Integer)
TwothrottlerProperties.getOrDefault(ICamelConstants.THROTTLE_TIME_PERIOD_MILLIS,
1000 * 60))
.process((AsyncProcessor)
aRouteConfigMap.get(ICamelConstants.IDEMPOTENCY_HEADER_GENERATE_PROCESSOR))
.idempotentConsumer(header(ICamelConstants.MESSAGE_ID),
(IdempotentRepository)
aRouteConfigMap.get(ICamelConstants.IDEMPOTENT_REPOSITORY)); {code}
So we have 2 throttles injected in route one is at the user level which uses
"username" to correlate and group it and another at each connection.
> Throttle when used in camel-kafka route creates thread leak
> ---
>
> Key: CAMEL-19619
> URL: https://issues.apache.org/jira/browse/CAMEL-19619
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 3.14.9
>Reporter: Kartik
>Priority: Critical
> Attachments: image-2023-07-19-19-33-10-591.png,
> image-2023-07-19-19-33-33-151.png
>
>
> I have used throttle in the camel Kafka route to control the message flow and
> I have 10 routes running initially there will be no throttle thread created
> as soon as the message comes to the Kafka topic and read huge number of
> throttle threads are created.
>
> For 10 routes I see 88 throttle "threads" threads created and are doing no
> work.
>
> !image-2023-07-19-19-33-10-591.png!
>
> !image-2023-07-19-19-33-33-151.png!
>
> Stack trace of each throttle thread.
> "Camel (InfaDefaultCamelContext) thread #51 - Throttle" #135 daemon prio=5
> os_prio=0 tid=0x01dfee834000 nid=0x2dbc waiting on condition
> [0x00d5a2dff000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00073da9aaf0> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
> at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:750)
>
> Locked ownable synchronizers:
> - None
>
> "Camel (InfaDefaultCamelContext) thread #50 - Throttle" #134 daemon prio=5
> os_prio=0 tid=0x01dfee835800 nid=0x71d4 waiting on condition
>
[jira] [Created] (CAMEL-19620) camel-coap - Upgrade to Californium 3.x
Claus Ibsen created CAMEL-19620: --- Summary: camel-coap - Upgrade to Californium 3.x Key: CAMEL-19620 URL: https://issues.apache.org/jira/browse/CAMEL-19620 Project: Camel Issue Type: Dependency upgrade Components: camel-coap Reporter: Claus Ibsen We use 2.x now, and would be good to upgrade to v3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19619) Throttle when used in camel-kafka route creates thread leak
[ https://issues.apache.org/jira/browse/CAMEL-19619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kartik updated CAMEL-19619: --- Priority: Critical (was: Minor) > Throttle when used in camel-kafka route creates thread leak > --- > > Key: CAMEL-19619 > URL: https://issues.apache.org/jira/browse/CAMEL-19619 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.14.9 >Reporter: Kartik >Priority: Critical > Attachments: image-2023-07-19-19-33-10-591.png, > image-2023-07-19-19-33-33-151.png > > > I have used throttle in the camel Kafka route to control the message flow and > I have 10 routes running initially there will be no throttle thread created > as soon as the message comes to the Kafka topic and read huge number of > throttle threads are created. > > For 10 routes I see 88 throttle "threads" threads created and are doing no > work. > > !image-2023-07-19-19-33-10-591.png! > > !image-2023-07-19-19-33-33-151.png! > > Stack trace of each throttle thread. > "Camel (InfaDefaultCamelContext) thread #51 - Throttle" #135 daemon prio=5 > os_prio=0 tid=0x01dfee834000 nid=0x2dbc waiting on condition > [0x00d5a2dff000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073da9aaf0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #50 - Throttle" #134 daemon prio=5 > os_prio=0 tid=0x01dfee835800 nid=0x71d4 waiting on condition > [0x00d5a2cfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073db8c0c0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #49 - Throttle" #133 daemon prio=5 > os_prio=0 tid=0x01dfee82b000 nid=0x5574 waiting on condition > [0x00d5a2bfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073de977d8> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel
[jira] [Commented] (CAMEL-19619) Throttle when used in camel-kafka route creates thread leak
[ https://issues.apache.org/jira/browse/CAMEL-19619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744635#comment-17744635 ] Claus Ibsen commented on CAMEL-19619: - Can you show your camel route what you do > Throttle when used in camel-kafka route creates thread leak > --- > > Key: CAMEL-19619 > URL: https://issues.apache.org/jira/browse/CAMEL-19619 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.14.9 >Reporter: Kartik >Priority: Critical > Attachments: image-2023-07-19-19-33-10-591.png, > image-2023-07-19-19-33-33-151.png > > > I have used throttle in the camel Kafka route to control the message flow and > I have 10 routes running initially there will be no throttle thread created > as soon as the message comes to the Kafka topic and read huge number of > throttle threads are created. > > For 10 routes I see 88 throttle "threads" threads created and are doing no > work. > > !image-2023-07-19-19-33-10-591.png! > > !image-2023-07-19-19-33-33-151.png! > > Stack trace of each throttle thread. > "Camel (InfaDefaultCamelContext) thread #51 - Throttle" #135 daemon prio=5 > os_prio=0 tid=0x01dfee834000 nid=0x2dbc waiting on condition > [0x00d5a2dff000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073da9aaf0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #50 - Throttle" #134 daemon prio=5 > os_prio=0 tid=0x01dfee835800 nid=0x71d4 waiting on condition > [0x00d5a2cfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073db8c0c0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #49 - Throttle" #133 daemon prio=5 > os_prio=0 tid=0x01dfee82b000 nid=0x5574 waiting on condition > [0x00d5a2bfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073de977d8> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked
[jira] [Updated] (CAMEL-19619) Throttle when used in camel-kafka route creates thread leak
[ https://issues.apache.org/jira/browse/CAMEL-19619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19619: Fix Version/s: (was: 3.14.10) > Throttle when used in camel-kafka route creates thread leak > --- > > Key: CAMEL-19619 > URL: https://issues.apache.org/jira/browse/CAMEL-19619 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.14.9 >Reporter: Kartik >Priority: Minor > Attachments: image-2023-07-19-19-33-10-591.png, > image-2023-07-19-19-33-33-151.png > > > I have used throttle in the camel Kafka route to control the message flow and > I have 10 routes running initially there will be no throttle thread created > as soon as the message comes to the Kafka topic and read huge number of > throttle threads are created. > > For 10 routes I see 88 throttle "threads" threads created and are doing no > work. > > !image-2023-07-19-19-33-10-591.png! > > !image-2023-07-19-19-33-33-151.png! > > Stack trace of each throttle thread. > "Camel (InfaDefaultCamelContext) thread #51 - Throttle" #135 daemon prio=5 > os_prio=0 tid=0x01dfee834000 nid=0x2dbc waiting on condition > [0x00d5a2dff000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073da9aaf0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #50 - Throttle" #134 daemon prio=5 > os_prio=0 tid=0x01dfee835800 nid=0x71d4 waiting on condition > [0x00d5a2cfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073db8c0c0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #49 - Throttle" #133 daemon prio=5 > os_prio=0 tid=0x01dfee82b000 nid=0x5574 waiting on condition > [0x00d5a2bfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073de977d8> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel
[jira] [Updated] (CAMEL-19619) Throttle when used in camel-kafka route creates thread leak
[ https://issues.apache.org/jira/browse/CAMEL-19619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19619: Priority: Minor (was: Critical) > Throttle when used in camel-kafka route creates thread leak > --- > > Key: CAMEL-19619 > URL: https://issues.apache.org/jira/browse/CAMEL-19619 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.14.9 >Reporter: Kartik >Priority: Minor > Fix For: 3.14.10 > > Attachments: image-2023-07-19-19-33-10-591.png, > image-2023-07-19-19-33-33-151.png > > > I have used throttle in the camel Kafka route to control the message flow and > I have 10 routes running initially there will be no throttle thread created > as soon as the message comes to the Kafka topic and read huge number of > throttle threads are created. > > For 10 routes I see 88 throttle "threads" threads created and are doing no > work. > > !image-2023-07-19-19-33-10-591.png! > > !image-2023-07-19-19-33-33-151.png! > > Stack trace of each throttle thread. > "Camel (InfaDefaultCamelContext) thread #51 - Throttle" #135 daemon prio=5 > os_prio=0 tid=0x01dfee834000 nid=0x2dbc waiting on condition > [0x00d5a2dff000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073da9aaf0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #50 - Throttle" #134 daemon prio=5 > os_prio=0 tid=0x01dfee835800 nid=0x71d4 waiting on condition > [0x00d5a2cfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073db8c0c0> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable synchronizers: > - None > > "Camel (InfaDefaultCamelContext) thread #49 - Throttle" #133 daemon prio=5 > os_prio=0 tid=0x01dfee82b000 nid=0x5574 waiting on condition > [0x00d5a2bfe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0x00073de977d8> (a > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) > at > java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) > at > java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) > at > java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:750) > > Locked ownable
[jira] [Created] (CAMEL-19619) Throttle when used in camel-kafka route creates thread leak
Kartik created CAMEL-19619: -- Summary: Throttle when used in camel-kafka route creates thread leak Key: CAMEL-19619 URL: https://issues.apache.org/jira/browse/CAMEL-19619 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 3.14.9 Reporter: Kartik Fix For: 3.14.10 Attachments: image-2023-07-19-19-33-10-591.png, image-2023-07-19-19-33-33-151.png I have used throttle in the camel Kafka route to control the message flow and I have 10 routes running initially there will be no throttle thread created as soon as the message comes to the Kafka topic and read huge number of throttle threads are created. For 10 routes I see 88 throttle "threads" threads created and are doing no work. !image-2023-07-19-19-33-10-591.png! !image-2023-07-19-19-33-33-151.png! Stack trace of each throttle thread. "Camel (InfaDefaultCamelContext) thread #51 - Throttle" #135 daemon prio=5 os_prio=0 tid=0x01dfee834000 nid=0x2dbc waiting on condition [0x00d5a2dff000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x00073da9aaf0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:750) Locked ownable synchronizers: - None "Camel (InfaDefaultCamelContext) thread #50 - Throttle" #134 daemon prio=5 os_prio=0 tid=0x01dfee835800 nid=0x71d4 waiting on condition [0x00d5a2cfe000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x00073db8c0c0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:750) Locked ownable synchronizers: - None "Camel (InfaDefaultCamelContext) thread #49 - Throttle" #133 daemon prio=5 os_prio=0 tid=0x01dfee82b000 nid=0x5574 waiting on condition [0x00d5a2bfe000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x00073de977d8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2044) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088) at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:750) Locked ownable synchronizers: - None "Camel (InfaDefaultCamelContext) thread #48 - Throttle" #132 daemon prio=5 os_prio=0 tid=0x01dff3b5e800 nid=0x60cc waiting on condition [0x00d5a2aff000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x00073e02bf60> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at
[jira] [Created] (CAMEL-19618) camel-box - Upgrade to v4
Claus Ibsen created CAMEL-19618: --- Summary: camel-box - Upgrade to v4 Key: CAMEL-19618 URL: https://issues.apache.org/jira/browse/CAMEL-19618 Project: Camel Issue Type: Dependency upgrade Components: camel-box Reporter: Claus Ibsen We use an older v2 java-sdk and should upgrade to v4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19616) camel-restdsl-openapi-plugin - Do not use servlet as component by default
[ https://issues.apache.org/jira/browse/CAMEL-19616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19616. - Resolution: Fixed > camel-restdsl-openapi-plugin - Do not use servlet as component by default > - > > Key: CAMEL-19616 > URL: https://issues.apache.org/jira/browse/CAMEL-19616 > Project: Camel > Issue Type: Improvement > Components: tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.0-RC2, 4.0.0 > > > We should not configure any specific component in the generated code (users > can specify in the plugin configuration). > Camel today has auto-discover and will use platform-http if found etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19615) camel-ftp: chmodDirectory option try for each junk to change the directory permission and fails
[
https://issues.apache.org/jira/browse/CAMEL-19615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19615:
Fix Version/s: 3.14.10
3.20.7
3.21.1
3.22.0
4.0-RC2
4.0.0
> camel-ftp: chmodDirectory option try for each junk to change the directory
> permission and fails
> ---
>
> Key: CAMEL-19615
> URL: https://issues.apache.org/jira/browse/CAMEL-19615
> Project: Camel
> Issue Type: Improvement
> Components: camel-sftp
>Affects Versions: 3.18.2
>Reporter: Michael Rambichler
>Priority: Major
> Fix For: 3.14.10, 3.20.7, 3.21.1, 3.22.0, 4.0-RC2, 4.0.0
>
>
> We have a blocking issue with the current chmodDirectory option.
> [https://camel.apache.org/components/3.20.x/sftp-component.html#_endpoint_query_option_chmodDirectory]
>
> *Steps to reproduce:*
> SFTP Directory: ../home/user/restricted/dir/subdir (where restricted e.g.
> does not have change rights for the current user)
> Component Call:
> "sftp://localhost:21/home/user/restricted/dir/subdir/newDir; +
> "?username=admin=admin=777=770"
>
> *Behaviour:*
> The current implementation steps down the directory and try to create each
> junk. If the chmodDirectory option is set then i{color:#FF}t will try for
> each (already existing junk) to change the directory permission and
> fails.{color}
>
> *Expected Behaviour:*
> It should only try to change the permission if the directory does not yet
> exists
>
> I have already created a fix and added a Testcase for better debugging (but
> the Testcase does not reproduce the error because it would remove the
> permission for the current user and afterwards your need root rights to
> delete the Testdirectory again. Not suitable pipeline builds)
> [https://github.com/michael-salzburg/camel]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-19615) camel-ftp: chmodDirectory option try for each junk to change the directory permission and fails
[
https://issues.apache.org/jira/browse/CAMEL-19615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744565#comment-17744565
]
Michael Rambichler edited comment on CAMEL-19615 at 7/19/23 1:16 PM:
-
PR created: [https://github.com/apache/camel/pull/10730]
was (Author: rambichler):
Pullrequest created: [https://github.com/apache/camel/pull/10727]
> camel-ftp: chmodDirectory option try for each junk to change the directory
> permission and fails
> ---
>
> Key: CAMEL-19615
> URL: https://issues.apache.org/jira/browse/CAMEL-19615
> Project: Camel
> Issue Type: Improvement
> Components: camel-sftp
>Affects Versions: 3.18.2
>Reporter: Michael Rambichler
>Priority: Major
>
> We have a blocking issue with the current chmodDirectory option.
> [https://camel.apache.org/components/3.20.x/sftp-component.html#_endpoint_query_option_chmodDirectory]
>
> *Steps to reproduce:*
> SFTP Directory: ../home/user/restricted/dir/subdir (where restricted e.g.
> does not have change rights for the current user)
> Component Call:
> "sftp://localhost:21/home/user/restricted/dir/subdir/newDir; +
> "?username=admin=admin=777=770"
>
> *Behaviour:*
> The current implementation steps down the directory and try to create each
> junk. If the chmodDirectory option is set then i{color:#FF}t will try for
> each (already existing junk) to change the directory permission and
> fails.{color}
>
> *Expected Behaviour:*
> It should only try to change the permission if the directory does not yet
> exists
>
> I have already created a fix and added a Testcase for better debugging (but
> the Testcase does not reproduce the error because it would remove the
> permission for the current user and afterwards your need root rights to
> delete the Testdirectory again. Not suitable pipeline builds)
> [https://github.com/michael-salzburg/camel]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19613) Convert components to use the camel-test-infra-core
[ https://issues.apache.org/jira/browse/CAMEL-19613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-19613: - Description: As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a CamelContext into the tests. This moves the management of the context lifecycle to JUnit and can simplify debugging the code. Although it is not a drop-in replacement to the CamelTestSupport, a [conversion guide covering the basics of the process is available along with the test infra code|https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-core/README.md]. The following components need to be converted: - -camel-arangodb- - camel-as2 - camel-asn1 - camel-asterisk - camel-atmosphere-websocket - camel-atom - camel-attachments - camel-avro - camel-avro-rpc - camel-aws - camel-azure - camel-barcode - camel-base64 - camel-bean-validator - camel-bindy - camel-bonita - camel-box - camel-braintree - camel-caffeine - In Progress - camel-cassandraql - camel-cbor - camel-chatscript - camel-chunk - camel-coap - camel-cometd - camel-consul - camel-corda - camel-couchbase - camel-couchdb - camel-cron - camel-crypto - camel-csimple-joor - camel-csv - camel-cxf - camel-datasonnet - camel-debezium - camel-dhis2 - camel-digitalocean - camel-disruptor - camel-djl - camel-dns - camel-docker - camel-drill - camel-dropbox - camel-dynamic-router - camel-ehcache - camel-elasticsearch - camel-elytron - camel-etcd3 - camel-exec - camel-facebook - camel-fastjson - camel-fhir - camel-file-watch - camel-flatpack - camel-flink - camel-fop - camel-freemarker - camel-ftp - camel-geocoder - camel-git - camel-github - camel-google - camel-graphql - camel-grok - camel-groovy - camel-grpc - camel-gson - camel-guava-eventbus - camel-hashicorp-vault - camel-hazelcast - camel-hdfs - camel-headersmap - camel-hl7 - camel-http - camel-http-common - camel-huawei - camel-hyperledger-aries - camel-ical - camel-iec60870 - camel-ignite - camel-infinispan - camel-influxdb - camel-influxdb2 - camel-irc - camel-ironmq - camel-jackson - camel-jackson-avro - camel-jackson-protobuf - camel-jacksonxml - camel-jasypt - camel-javascript - camel-jaxb - camel-jcache - camel-jcr - camel-jdbc - camel-jetty - camel-jgroups - camel-jgroups-raft - camel-jira - camel-jms - camel-jmx - camel-jolt - camel-jooq - camel-joor - camel-jpa - camel-jq - camel-jsch - camel-jslt - camel-json-patch - camel-json-validator - camel-jsonapi - camel-jsonata - camel-jsonb - camel-jsonpath - camel-jt400 - camel-kamelet - camel-kubernetes - camel-kudu - camel-ldif - camel-leveldb - camel-lra - camel-lucene - camel-lumberjack - camel-lzf - camel-mail - camel-mapstruct - camel-master - camel-metrics - camel-micrometer - camel-microprofile - camel-mina - camel-minio - camel-mllp - camel-mongodb - camel-mongodb-gridfs - camel-mustache - camel-mvel - camel-mybatis - camel-nats - camel-netty - camel-netty-http - camel-nitrite - camel-oaipmh - camel-observation - camel-ognl - camel-olingo2 - camel-olingo4 - camel-openapi-java - camel-opensearch - camel-openstack - camel-opentelemetry - camel-optaplanner - camel-paho - camel-paho-mqtt5 - camel-parquet-avro - camel-pdf - camel-pg-replication-slot - camel-pgevent - camel-platform-http-vertx - camel-plc4x - camel-printer - camel-protobuf - camel-pubnub - camel-pulsar - camel-python - camel-quartz - camel-quickfix - camel-reactive-executor-tomcat - camel-reactive-executor-vertx - camel-reactive-streams - camel-reactor - camel-redis - camel-resilience4j - camel-resourceresolver-github - camel-rest-openapi - camel-robotframework - camel-rocketmq - camel-rss - camel-rxjava - camel-salesforce - camel-sap-netweaver - camel-saxon - camel-schematron - camel-servicenow - camel-servlet - camel-shiro - camel-sjms - camel-sjms2 - camel-slack - camel-smpp - camel-snakeyaml - camel-snmp - camel-soap - camel-splunk - camel-splunk-hec - camel-spring-batch - camel-spring-jdbc - camel-spring-ldap - camel-spring-main - camel-spring-rabbitmq - camel-spring-redis - camel-spring-ws - camel-spring-xml - camel-sql - camel-ssh - camel-stax - camel-stitch - camel-stomp - camel-stream - camel-stringtemplate - camel-swift - camel-syslog - camel-tarfile - camel-telegram - camel-test - camel-threadpoolfactory-vertx - camel-thrift - camel-tika - camel-twilio - camel-twitter - camel-undertow - camel-undertow-spring-security - camel-univocity-parsers - camel-velocity - camel-vertx - camel-weather - camel-web3j - camel-webhook - camel-whatsapp - camel-wordpress - camel-workday - camel-xchange - camel-xj - camel-xmlsecurity - camel-xmpp - camel-xslt-saxon - camel-zeebe - camel-zendesk - camel-zip-deflater -
[jira] [Updated] (CAMEL-19613) Convert components to use the camel-test-infra-core
[ https://issues.apache.org/jira/browse/CAMEL-19613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano Marcondes Machado updated CAMEL-19613: -- Description: As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a CamelContext into the tests. This moves the management of the context lifecycle to JUnit and can simplify debugging the code. Although it is not a drop-in replacement to the CamelTestSupport, a [conversion guide covering the basics of the process is available along with the test infra code|https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-core/README.md]. The following components need to be converted: - -camel-arangodb- - camel-as2 - camel-asn1 - camel-asterisk - camel-atmosphere-websocket - camel-atom - camel-attachments - camel-avro - camel-avro-rpc - camel-aws - camel-azure - camel-barcode - camel-base64 - camel-bean-validator - camel-bindy - camel-bonita - camel-box - camel-braintree - camel-caffeine - camel-cassandraql - camel-cbor - camel-chatscript - camel-chunk - camel-coap - camel-cometd - camel-consul - camel-corda - camel-couchbase - camel-couchdb - camel-cron - camel-crypto - camel-csimple-joor - camel-csv - camel-cxf - camel-datasonnet - camel-debezium - camel-dhis2 - camel-digitalocean - camel-disruptor - camel-djl - camel-dns - camel-docker - camel-drill - camel-dropbox - camel-dynamic-router - camel-ehcache - camel-elasticsearch - camel-elytron - camel-etcd3 - camel-exec - camel-facebook - camel-fastjson - camel-fhir - camel-file-watch - camel-flatpack - camel-flink - camel-fop - camel-freemarker - camel-ftp - camel-geocoder - camel-git - camel-github - camel-google - camel-graphql - camel-grok - camel-groovy - camel-grpc - camel-gson - camel-guava-eventbus - camel-hashicorp-vault - camel-hazelcast - camel-hdfs - camel-headersmap - camel-hl7 - camel-http - camel-http-common - camel-huawei - camel-hyperledger-aries - camel-ical - camel-iec60870 - camel-ignite - camel-infinispan - camel-influxdb - camel-influxdb2 - camel-irc - camel-ironmq - camel-jackson - camel-jackson-avro - camel-jackson-protobuf - camel-jacksonxml - camel-jasypt - camel-javascript - camel-jaxb - camel-jcache - camel-jcr - camel-jdbc - camel-jetty - camel-jgroups - camel-jgroups-raft - camel-jira - camel-jms - camel-jmx - camel-jolt - camel-jooq - camel-joor - camel-jpa - camel-jq - camel-jsch - camel-jslt - camel-json-patch - camel-json-validator - camel-jsonapi - camel-jsonata - camel-jsonb - camel-jsonpath - camel-jt400 - camel-kamelet - camel-kubernetes - camel-kudu - camel-ldif - camel-leveldb - camel-lra - camel-lucene - camel-lumberjack - camel-lzf - camel-mail - camel-mapstruct - camel-master - camel-metrics - camel-micrometer - camel-microprofile - camel-mina - camel-minio - camel-mllp - camel-mongodb - camel-mongodb-gridfs - camel-mustache - camel-mvel - camel-mybatis - camel-nats - camel-netty - camel-netty-http - camel-nitrite - camel-oaipmh - camel-observation - camel-ognl - camel-olingo2 - camel-olingo4 - camel-openapi-java - camel-opensearch - camel-openstack - camel-opentelemetry - camel-optaplanner - camel-paho - camel-paho-mqtt5 - camel-parquet-avro - camel-pdf - camel-pg-replication-slot - camel-pgevent - camel-platform-http-vertx - camel-plc4x - camel-printer - camel-protobuf - camel-pubnub - camel-pulsar - camel-python - camel-quartz - camel-quickfix - camel-reactive-executor-tomcat - camel-reactive-executor-vertx - camel-reactive-streams - camel-reactor - camel-redis - camel-resilience4j - camel-resourceresolver-github - camel-rest-openapi - camel-robotframework - camel-rocketmq - camel-rss - camel-rxjava - camel-salesforce - camel-sap-netweaver - camel-saxon - camel-schematron - camel-servicenow - camel-servlet - camel-shiro - camel-sjms - camel-sjms2 - camel-slack - camel-smpp - camel-snakeyaml - camel-snmp - camel-soap - camel-splunk - camel-splunk-hec - camel-spring-batch - camel-spring-jdbc - camel-spring-ldap - camel-spring-main - camel-spring-rabbitmq - camel-spring-redis - camel-spring-ws - camel-spring-xml - camel-sql - camel-ssh - camel-stax - camel-stitch - camel-stomp - camel-stream - camel-stringtemplate - camel-swift - camel-syslog - camel-tarfile - camel-telegram - camel-test - camel-threadpoolfactory-vertx - camel-thrift - camel-tika - camel-twilio - camel-twitter - camel-undertow - camel-undertow-spring-security - camel-univocity-parsers - camel-velocity - camel-vertx - camel-weather - camel-web3j - camel-webhook - camel-whatsapp - camel-wordpress - camel-workday - camel-xchange - camel-xj - camel-xmlsecurity - camel-xmpp - camel-xslt-saxon - camel-zeebe - camel-zendesk - camel-zip-deflater - camel-zipfile
[jira] [Resolved] (CAMEL-19447) camel-kafka: investigate potential test cleanups
[ https://issues.apache.org/jira/browse/CAMEL-19447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-19447. -- Resolution: Fixed Resolved with the linked PRs. > camel-kafka: investigate potential test cleanups > > > Key: CAMEL-19447 > URL: https://issues.apache.org/jira/browse/CAMEL-19447 > Project: Camel > Issue Type: Task > Components: camel-kafka >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Labels: easy > > It seems that there are a few minor cleanups that we can do on the tests for > the camel-kafka component. For instance, there seems to exist a few grammar > problems, lack of usage of final variables, threading issues and other > minor-problems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19616) camel-restdsl-openapi-plugin - Do not use servlet as component by default
[ https://issues.apache.org/jira/browse/CAMEL-19616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744576#comment-17744576 ] Claus Ibsen commented on CAMEL-19616: - There is also some code generator for spring-boot with servlet that is no longer needed (as we use platform-http) now > camel-restdsl-openapi-plugin - Do not use servlet as component by default > - > > Key: CAMEL-19616 > URL: https://issues.apache.org/jira/browse/CAMEL-19616 > Project: Camel > Issue Type: Improvement > Components: tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.0-RC2, 4.0.0 > > > We should not configure any specific component in the generated code (users > can specify in the plugin configuration). > Camel today has auto-discover and will use platform-http if found etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19616) camel-restdsl-openapi-plugin - Do not use servlet as component by default
[ https://issues.apache.org/jira/browse/CAMEL-19616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-19616: --- Assignee: Claus Ibsen > camel-restdsl-openapi-plugin - Do not use servlet as component by default > - > > Key: CAMEL-19616 > URL: https://issues.apache.org/jira/browse/CAMEL-19616 > Project: Camel > Issue Type: Improvement > Components: tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.0-RC2, 4.0.0 > > > We should not configure any specific component in the generated code (users > can specify in the plugin configuration). > Camel today has auto-discover and will use platform-http if found etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19615) camel-ftp: chmodDirectory option try for each junk to change the directory permission and fails
[
https://issues.apache.org/jira/browse/CAMEL-19615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744565#comment-17744565
]
Michael Rambichler commented on CAMEL-19615:
Pullrequest created: [https://github.com/apache/camel/pull/10727]
> camel-ftp: chmodDirectory option try for each junk to change the directory
> permission and fails
> ---
>
> Key: CAMEL-19615
> URL: https://issues.apache.org/jira/browse/CAMEL-19615
> Project: Camel
> Issue Type: Improvement
> Components: camel-sftp
>Affects Versions: 3.18.2
>Reporter: Michael Rambichler
>Priority: Major
>
> We have a blocking issue with the current chmodDirectory option.
> [https://camel.apache.org/components/3.20.x/sftp-component.html#_endpoint_query_option_chmodDirectory]
>
> *Steps to reproduce:*
> SFTP Directory: ../home/user/restricted/dir/subdir (where restricted e.g.
> does not have change rights for the current user)
> Component Call:
> "sftp://localhost:21/home/user/restricted/dir/subdir/newDir; +
> "?username=admin=admin=777=770"
>
> *Behaviour:*
> The current implementation steps down the directory and try to create each
> junk. If the chmodDirectory option is set then i{color:#FF}t will try for
> each (already existing junk) to change the directory permission and
> fails.{color}
>
> *Expected Behaviour:*
> It should only try to change the permission if the directory does not yet
> exists
>
> I have already created a fix and added a Testcase for better debugging (but
> the Testcase does not reproduce the error because it would remove the
> permission for the current user and afterwards your need root rights to
> delete the Testdirectory again. Not suitable pipeline builds)
> [https://github.com/michael-salzburg/camel]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19617) camel-xmlsecurity - Upgrade santuario to 3.x
Claus Ibsen created CAMEL-19617: --- Summary: camel-xmlsecurity - Upgrade santuario to 3.x Key: CAMEL-19617 URL: https://issues.apache.org/jira/browse/CAMEL-19617 Project: Camel Issue Type: Dependency upgrade Components: camel-xmlsecurity Reporter: Claus Ibsen There is 1 unit test that fails with the upgrade [ERROR] Failures: [ERROR] XmlSignatureTest.testSetTransformMethodXsltXpathInRouteDefinitionSecValDisabled:566 mock://result Received message count. Expected: <1> but was: <0> [INFO] [ERROR] Tests run: 186, Failures: 1, Errors: 0, Skipped: 8 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19613) Convert components to use the camel-test-infra-core
[ https://issues.apache.org/jira/browse/CAMEL-19613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744508#comment-17744508 ] Otavio Rodolfo Piske commented on CAMEL-19613: -- Updated the list: there were a few components that had been incorrectly added. It should be fine now. > Convert components to use the camel-test-infra-core > --- > > Key: CAMEL-19613 > URL: https://issues.apache.org/jira/browse/CAMEL-19613 > Project: Camel > Issue Type: Test > Components: camel-test-infra-core >Affects Versions: 4.0.0 >Reporter: Otavio Rodolfo Piske >Priority: Major > Labels: easy, help-wanted > > As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a > CamelContext into the tests. This moves the management of the context > lifecycle to JUnit and can simplify debugging the code. Although it is not a > drop-in replacement to the CamelTestSupport, a [conversion guide covering the > basics of the process is available along with the test infra > code|https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-core/README.md]. > > The following components need to be converted: > - camel-arangodb - DONE > - camel-as2 > - camel-asn1 > - camel-asterisk > - camel-atmosphere-websocket > - camel-atom > - camel-attachments > - camel-avro > - camel-avro-rpc > - camel-aws > - camel-azure > - camel-barcode > - camel-base64 > - camel-bean-validator > - camel-bindy > - camel-bonita > - camel-box > - camel-braintree > - camel-caffeine > - camel-cbor > - camel-chatscript > - camel-chunk > - camel-coap > - camel-cometd > - camel-consul > - camel-corda > - camel-couchbase > - camel-couchdb > - camel-cron > - camel-crypto > - camel-csimple-joor > - camel-csv > - camel-cxf > - camel-datasonnet > - camel-debezium > - camel-dhis2 > - camel-digitalocean > - camel-disruptor > - camel-djl > - camel-dns > - camel-docker > - camel-drill > - camel-dropbox > - camel-dynamic-router > - camel-ehcache > - camel-elasticsearch > - camel-elytron > - camel-etcd3 > - camel-exec > - camel-facebook > - camel-fastjson > - camel-fhir > - camel-file-watch > - camel-flatpack > - camel-flink > - camel-fop > - camel-freemarker > - camel-ftp > - camel-geocoder > - camel-git > - camel-github > - camel-google > - camel-graphql > - camel-grok > - camel-groovy > - camel-grpc > - camel-gson > - camel-guava-eventbus > - camel-hashicorp-vault > - camel-hazelcast > - camel-hdfs > - camel-headersmap > - camel-hl7 > - camel-http > - camel-http-common > - camel-huawei > - camel-hyperledger-aries > - camel-ical > - camel-iec60870 > - camel-ignite > - camel-infinispan > - camel-influxdb > - camel-influxdb2 > - camel-irc > - camel-ironmq > - camel-jackson > - camel-jackson-avro > - camel-jackson-protobuf > - camel-jacksonxml > - camel-jasypt > - camel-javascript > - camel-jaxb > - camel-jcache > - camel-jcr > - camel-jdbc > - camel-jetty > - camel-jgroups > - camel-jgroups-raft > - camel-jira > - camel-jms > - camel-jmx > - camel-jolt > - camel-jooq > - camel-joor > - camel-jpa > - camel-jq > - camel-jsch > - camel-jslt > - camel-json-patch > - camel-json-validator > - camel-jsonapi > - camel-jsonata > - camel-jsonb > - camel-jsonpath > - camel-jt400 > - camel-kamelet > - camel-kubernetes > - camel-kudu > - camel-ldif > - camel-leveldb > - camel-lra > - camel-lucene > - camel-lumberjack > - camel-lzf > - camel-mail > - camel-mapstruct > - camel-master > - camel-metrics > - camel-micrometer > - camel-microprofile > - camel-mina > - camel-minio > - camel-mllp > - camel-mongodb > - camel-mongodb-gridfs > - camel-mustache > - camel-mvel > - camel-mybatis > - camel-nats > - camel-netty > - camel-netty-http > - camel-nitrite > - camel-oaipmh > - camel-observation > - camel-ognl > - camel-olingo2 > - camel-olingo4 > - camel-openapi-java > - camel-opensearch > - camel-openstack > - camel-opentelemetry > - camel-optaplanner > - camel-paho-mqtt5 > - camel-parquet-avro > - camel-pdf > - camel-pg-replication-slot > - camel-pgevent > - camel-platform-http-vertx > - camel-plc4x > - camel-printer > - camel-protobuf > - camel-pubnub > - camel-pulsar > - camel-python > - camel-quartz > - camel-quickfix > - camel-reactive-executor-tomcat > - camel-reactive-executor-vertx > - camel-reactive-streams > - camel-reactor > - camel-redis > - camel-resilience4j > - camel-resourceresolver-github > - camel-rest-openapi > - camel-robotframework > - camel-rocketmq > - camel-rss > - camel-rxjava > - camel-salesforce > - camel-sap-netweaver > - camel-saxon > - camel-schematron > - camel-servicenow > - camel-servlet > - camel-shiro > - camel-sjms > - camel-sjms2 > - camel-slack > - camel-smpp > - camel-snakeyaml > - camel-snmp > - camel-soap > - camel-splunk > - camel-splunk-hec > - camel-spring-batch > - camel-spring-jdbc > -
[jira] [Updated] (CAMEL-19613) Convert components to use the camel-test-infra-core
[ https://issues.apache.org/jira/browse/CAMEL-19613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-19613: - Description: As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a CamelContext into the tests. This moves the management of the context lifecycle to JUnit and can simplify debugging the code. Although it is not a drop-in replacement to the CamelTestSupport, a [conversion guide covering the basics of the process is available along with the test infra code|https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-core/README.md]. The following components need to be converted: - camel-arangodb - DONE - camel-as2 - camel-asn1 - camel-asterisk - camel-atmosphere-websocket - camel-atom - camel-attachments - camel-avro - camel-avro-rpc - camel-aws - camel-azure - camel-barcode - camel-base64 - camel-bean-validator - camel-bindy - camel-bonita - camel-box - camel-braintree - camel-caffeine - camel-cbor - camel-chatscript - camel-chunk - camel-coap - camel-cometd - camel-consul - camel-corda - camel-couchbase - camel-couchdb - camel-cron - camel-crypto - camel-csimple-joor - camel-csv - camel-cxf - camel-datasonnet - camel-debezium - camel-dhis2 - camel-digitalocean - camel-disruptor - camel-djl - camel-dns - camel-docker - camel-drill - camel-dropbox - camel-dynamic-router - camel-ehcache - camel-elasticsearch - camel-elytron - camel-etcd3 - camel-exec - camel-facebook - camel-fastjson - camel-fhir - camel-file-watch - camel-flatpack - camel-flink - camel-fop - camel-freemarker - camel-ftp - camel-geocoder - camel-git - camel-github - camel-google - camel-graphql - camel-grok - camel-groovy - camel-grpc - camel-gson - camel-guava-eventbus - camel-hashicorp-vault - camel-hazelcast - camel-hdfs - camel-headersmap - camel-hl7 - camel-http - camel-http-common - camel-huawei - camel-hyperledger-aries - camel-ical - camel-iec60870 - camel-ignite - camel-infinispan - camel-influxdb - camel-influxdb2 - camel-irc - camel-ironmq - camel-jackson - camel-jackson-avro - camel-jackson-protobuf - camel-jacksonxml - camel-jasypt - camel-javascript - camel-jaxb - camel-jcache - camel-jcr - camel-jdbc - camel-jetty - camel-jgroups - camel-jgroups-raft - camel-jira - camel-jms - camel-jmx - camel-jolt - camel-jooq - camel-joor - camel-jpa - camel-jq - camel-jsch - camel-jslt - camel-json-patch - camel-json-validator - camel-jsonapi - camel-jsonata - camel-jsonb - camel-jsonpath - camel-jt400 - camel-kamelet - camel-kubernetes - camel-kudu - camel-ldif - camel-leveldb - camel-lra - camel-lucene - camel-lumberjack - camel-lzf - camel-mail - camel-mapstruct - camel-master - camel-metrics - camel-micrometer - camel-microprofile - camel-mina - camel-minio - camel-mllp - camel-mongodb - camel-mongodb-gridfs - camel-mustache - camel-mvel - camel-mybatis - camel-nats - camel-netty - camel-netty-http - camel-nitrite - camel-oaipmh - camel-observation - camel-ognl - camel-olingo2 - camel-olingo4 - camel-openapi-java - camel-opensearch - camel-openstack - camel-opentelemetry - camel-optaplanner - camel-paho-mqtt5 - camel-parquet-avro - camel-pdf - camel-pg-replication-slot - camel-pgevent - camel-platform-http-vertx - camel-plc4x - camel-printer - camel-protobuf - camel-pubnub - camel-pulsar - camel-python - camel-quartz - camel-quickfix - camel-reactive-executor-tomcat - camel-reactive-executor-vertx - camel-reactive-streams - camel-reactor - camel-redis - camel-resilience4j - camel-resourceresolver-github - camel-rest-openapi - camel-robotframework - camel-rocketmq - camel-rss - camel-rxjava - camel-salesforce - camel-sap-netweaver - camel-saxon - camel-schematron - camel-servicenow - camel-servlet - camel-shiro - camel-sjms - camel-sjms2 - camel-slack - camel-smpp - camel-snakeyaml - camel-snmp - camel-soap - camel-splunk - camel-splunk-hec - camel-spring-batch - camel-spring-jdbc - camel-spring-ldap - camel-spring-main - camel-spring-rabbitmq - camel-spring-redis - camel-spring-ws - camel-spring-xml - camel-sql - camel-ssh - camel-stax - camel-stitch - camel-stomp - camel-stream - camel-stringtemplate - camel-swift - camel-syslog - camel-tarfile - camel-telegram - camel-test - camel-threadpoolfactory-vertx - camel-thrift - camel-tika - camel-twilio - camel-twitter - camel-undertow - camel-undertow-spring-security - camel-univocity-parsers - camel-velocity - camel-vertx - camel-weather - camel-web3j - camel-webhook - camel-whatsapp - camel-wordpress - camel-workday - camel-xchange - camel-xj - camel-xmlsecurity - camel-xmpp - camel-xslt-saxon - camel-zeebe - camel-zendesk - camel-zip-deflater - camel-zipfile - camel-zookeeper was: As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a CamelContext into the tests. This moves the management of the context lifecycle to JUnit and can simplify debugging the code. Although it is not a drop-in replacement to
[jira] [Resolved] (CAMEL-19583) Lack of multiple shards consumption of Camel aws2 Kinesis
[ https://issues.apache.org/jira/browse/CAMEL-19583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-19583. -- Resolution: Fixed > Lack of multiple shards consumption of Camel aws2 Kinesis > - > > Key: CAMEL-19583 > URL: https://issues.apache.org/jira/browse/CAMEL-19583 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Reporter: Hamed Hatami >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0-RC2, 4.0.0 > > > Only one single shard can be consumed with one route on Kinesis and if you > have multiple shards then need to repeat the same route of kinesis with only > shard-id difference. there has to be a capability within this component even > in DSL to be able to consume from all available shards -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19583) Lack of multiple shards consumption of Camel aws2 Kinesis
[ https://issues.apache.org/jira/browse/CAMEL-19583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-19583: Assignee: Andrea Cosentino > Lack of multiple shards consumption of Camel aws2 Kinesis > - > > Key: CAMEL-19583 > URL: https://issues.apache.org/jira/browse/CAMEL-19583 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Reporter: Hamed Hatami >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0-RC2, 4.0.0 > > > Only one single shard can be consumed with one route on Kinesis and if you > have multiple shards then need to repeat the same route of kinesis with only > shard-id difference. there has to be a capability within this component even > in DSL to be able to consume from all available shards -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19583) Lack of multiple shards consumption of Camel aws2 Kinesis
[ https://issues.apache.org/jira/browse/CAMEL-19583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-19583: - Fix Version/s: 4.0-RC2 4.0.0 > Lack of multiple shards consumption of Camel aws2 Kinesis > - > > Key: CAMEL-19583 > URL: https://issues.apache.org/jira/browse/CAMEL-19583 > Project: Camel > Issue Type: Improvement > Components: camel-aws2 >Reporter: Hamed Hatami >Priority: Major > Fix For: 4.0-RC2, 4.0.0 > > > Only one single shard can be consumed with one route on Kinesis and if you > have multiple shards then need to repeat the same route of kinesis with only > shard-id difference. there has to be a capability within this component even > in DSL to be able to consume from all available shards -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19584) Camel aws2 Kinesis Asynchronous Client
[ https://issues.apache.org/jira/browse/CAMEL-19584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-19584: Assignee: Andrea Cosentino > Camel aws2 Kinesis Asynchronous Client > -- > > Key: CAMEL-19584 > URL: https://issues.apache.org/jira/browse/CAMEL-19584 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Affects Versions: 4.0-M3 >Reporter: Hamed Hatami >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.0-RC2, 4.0.0 > > > In the current aws-kinesis component , there's only synchronous client > implementation which is not nifty for nowadays framework's capabilities such > as Reactive Development so it'd be great if we improved this component to > support async client as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19584) Camel aws2 Kinesis Asynchronous Client
[ https://issues.apache.org/jira/browse/CAMEL-19584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-19584: - Fix Version/s: 4.0-RC2 4.0.0 > Camel aws2 Kinesis Asynchronous Client > -- > > Key: CAMEL-19584 > URL: https://issues.apache.org/jira/browse/CAMEL-19584 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Affects Versions: 4.0-M3 >Reporter: Hamed Hatami >Priority: Minor > Fix For: 4.0-RC2, 4.0.0 > > > In the current aws-kinesis component , there's only synchronous client > implementation which is not nifty for nowadays framework's capabilities such > as Reactive Development so it'd be great if we improved this component to > support async client as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19584) Camel aws2 Kinesis Asynchronous Client
[ https://issues.apache.org/jira/browse/CAMEL-19584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-19584. -- Resolution: Fixed > Camel aws2 Kinesis Asynchronous Client > -- > > Key: CAMEL-19584 > URL: https://issues.apache.org/jira/browse/CAMEL-19584 > Project: Camel > Issue Type: New Feature > Components: camel-aws2 >Affects Versions: 4.0-M3 >Reporter: Hamed Hatami >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.0-RC2, 4.0.0 > > > In the current aws-kinesis component , there's only synchronous client > implementation which is not nifty for nowadays framework's capabilities such > as Reactive Development so it'd be great if we improved this component to > support async client as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19614) camel-openapi-rest-dsl-generator - Upgrade apicurio-data-models
[ https://issues.apache.org/jira/browse/CAMEL-19614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19614. - Resolution: Fixed > camel-openapi-rest-dsl-generator - Upgrade apicurio-data-models > --- > > Key: CAMEL-19614 > URL: https://issues.apache.org/jira/browse/CAMEL-19614 > Project: Camel > Issue Type: Dependency upgrade > Components: tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0-RC2, 4.0.0 > > > Unfortunately the model is not compatible in v1 to v2, and its a lot of pain > to upgrade. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19613) Convert components to use the camel-test-infra-core
[ https://issues.apache.org/jira/browse/CAMEL-19613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-19613: - Description: As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a CamelContext into the tests. This moves the management of the context lifecycle to JUnit and can simplify debugging the code. Although it is not a drop-in replacement to the CamelTestSupport, a [conversion guide covering the basics of the process is available along with the test infra code|https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-core/README.md]. The following components need to be converted: - camel-arangodb - DONE - camel-as2 - camel-asn1 - camel-asterisk - camel-atmosphere-websocket - camel-atom - camel-attachments - camel-avro - camel-avro-rpc - camel-aws - camel-azure - camel-barcode - camel-base64 - camel-bean-validator - camel-bindy - camel-bonita - camel-box - camel-braintree - camel-caffeine - camel-cassandraql - camel-cbor - camel-chatscript - camel-chunk - camel-coap - camel-cometd - camel-consul - camel-corda - camel-couchbase - camel-couchdb - camel-cron - camel-crypto - camel-csimple-joor - camel-csv - camel-cxf - camel-datasonnet - camel-debezium - camel-dhis2 - camel-digitalocean - camel-disruptor - camel-djl - camel-dns - camel-docker - camel-drill - camel-dropbox - camel-dynamic-router - camel-ehcache - camel-elasticsearch - camel-elytron - camel-etcd3 - camel-exec - camel-facebook - camel-fastjson - camel-fhir - camel-file-watch - camel-flatpack - camel-flink - camel-fop - camel-freemarker - camel-ftp - camel-geocoder - camel-git - camel-github - camel-google - camel-graphql - camel-grok - camel-groovy - camel-grpc - camel-gson - camel-guava-eventbus - camel-hashicorp-vault - camel-hazelcast - camel-hdfs - camel-headersmap - camel-hl7 - camel-http - camel-http-common - camel-huawei - camel-hyperledger-aries - camel-ical - camel-iec60870 - camel-ignite - camel-infinispan - camel-influxdb - camel-influxdb2 - camel-irc - camel-ironmq - camel-jackson - camel-jackson-avro - camel-jackson-protobuf - camel-jacksonxml - camel-jasypt - camel-javascript - camel-jaxb - camel-jcache - camel-jcr - camel-jdbc - camel-jetty - camel-jgroups - camel-jgroups-raft - camel-jira - camel-jms - camel-jmx - camel-jolt - camel-jooq - camel-joor - camel-jpa - camel-jq - camel-jsch - camel-jslt - camel-json-patch - camel-json-validator - camel-jsonapi - camel-jsonata - camel-jsonb - camel-jsonpath - camel-jt400 - camel-kamelet - camel-kubernetes - camel-kudu - camel-ldif - camel-leveldb - camel-lra - camel-lucene - camel-lumberjack - camel-lzf - camel-mail - camel-mapstruct - camel-master - camel-metrics - camel-micrometer - camel-microprofile - camel-mina - camel-minio - camel-mllp - camel-mongodb - camel-mongodb-gridfs - camel-mustache - camel-mvel - camel-mybatis - camel-nats - camel-netty - camel-netty-http - camel-nitrite - camel-oaipmh - camel-observation - camel-ognl - camel-olingo2 - camel-olingo4 - camel-openapi-java - camel-opensearch - camel-openstack - camel-opentelemetry - camel-optaplanner - camel-paho - camel-paho-mqtt5 - camel-parquet-avro - camel-pdf - camel-pg-replication-slot - camel-pgevent - camel-platform-http-vertx - camel-plc4x - camel-printer - camel-protobuf - camel-pubnub - camel-pulsar - camel-python - camel-quartz - camel-quickfix - camel-reactive-executor-tomcat - camel-reactive-executor-vertx - camel-reactive-streams - camel-reactor - camel-redis - camel-resilience4j - camel-resourceresolver-github - camel-rest-openapi - camel-robotframework - camel-rocketmq - camel-rss - camel-rxjava - camel-salesforce - camel-sap-netweaver - camel-saxon - camel-schematron - camel-servicenow - camel-servlet - camel-shiro - camel-sjms - camel-sjms2 - camel-slack - camel-smpp - camel-snakeyaml - camel-snmp - camel-soap - camel-splunk - camel-splunk-hec - camel-spring-batch - camel-spring-jdbc - camel-spring-ldap - camel-spring-main - camel-spring-rabbitmq - camel-spring-redis - camel-spring-ws - camel-spring-xml - camel-sql - camel-ssh - camel-stax - camel-stitch - camel-stomp - camel-stream - camel-stringtemplate - camel-swift - camel-syslog - camel-tarfile - camel-telegram - camel-test - camel-threadpoolfactory-vertx - camel-thrift - camel-tika - camel-twilio - camel-twitter - camel-undertow - camel-undertow-spring-security - camel-univocity-parsers - camel-velocity - camel-vertx - camel-weather - camel-web3j - camel-webhook - camel-whatsapp - camel-wordpress - camel-workday - camel-xchange - camel-xj - camel-xmlsecurity - camel-xmpp - camel-xslt-saxon - camel-zeebe - camel-zendesk - camel-zip-deflater - camel-zipfile - camel-zookeeper was: As part of CAMEL-18957 we introduced a JUnit 5 extension that can inject a CamelContext into the tests. This moves the management of the context lifecycle to JUnit and can simplify debugging the code. Although it is not a
[jira] [Commented] (CAMEL-19447) camel-kafka: investigate potential test cleanups
[ https://issues.apache.org/jira/browse/CAMEL-19447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744483#comment-17744483 ] Otavio Rodolfo Piske commented on CAMEL-19447: -- All yours. Thanks! > camel-kafka: investigate potential test cleanups > > > Key: CAMEL-19447 > URL: https://issues.apache.org/jira/browse/CAMEL-19447 > Project: Camel > Issue Type: Task > Components: camel-kafka >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Labels: easy > > It seems that there are a few minor cleanups that we can do on the tests for > the camel-kafka component. For instance, there seems to exist a few grammar > problems, lack of usage of final variables, threading issues and other > minor-problems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19616) camel-restdsl-openapi-plugin - Do not use servlet as component by default
Claus Ibsen created CAMEL-19616: --- Summary: camel-restdsl-openapi-plugin - Do not use servlet as component by default Key: CAMEL-19616 URL: https://issues.apache.org/jira/browse/CAMEL-19616 Project: Camel Issue Type: Improvement Components: tooling Reporter: Claus Ibsen Fix For: 4.0-RC2, 4.0.0 We should not configure any specific component in the generated code (users can specify in the plugin configuration). Camel today has auto-discover and will use platform-http if found etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19615) camel-ftp: chmodDirectory option try for each junk to change the directory permission and fails
[
https://issues.apache.org/jira/browse/CAMEL-19615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-19615:
-
Summary: camel-ftp: chmodDirectory option try for each junk to change the
directory permission and fails (was: camel-ftp: chmodDirectory )
> camel-ftp: chmodDirectory option try for each junk to change the directory
> permission and fails
> ---
>
> Key: CAMEL-19615
> URL: https://issues.apache.org/jira/browse/CAMEL-19615
> Project: Camel
> Issue Type: Improvement
> Components: camel-sftp
>Affects Versions: 3.18.2
>Reporter: Michael Rambichler
>Priority: Major
>
> We have a blocking issue with the current chmodDirectory option.
> [https://camel.apache.org/components/3.20.x/sftp-component.html#_endpoint_query_option_chmodDirectory]
>
> *Steps to reproduce:*
> SFTP Directory: ../home/user/restricted/dir/subdir (where restricted e.g.
> does not have change rights for the current user)
> Component Call:
> "sftp://localhost:21/home/user/restricted/dir/subdir/newDir; +
> "?username=admin=admin=777=770"
>
> *Behaviour:*
> The current implementation steps down the directory and try to create each
> junk. If the chmodDirectory option is set then i{color:#FF}t will try for
> each (already existing junk) to change the directory permission and
> fails.{color}
>
> *Expected Behaviour:*
> It should only try to change the permission if the directory does not yet
> exists
>
> I have already created a fix and added a Testcase for better debugging (but
> the Testcase does not reproduce the error because it would remove the
> permission for the current user and afterwards your need root rights to
> delete the Testdirectory again. Not suitable pipeline builds)
> [https://github.com/michael-salzburg/camel]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19615) camel-ftp: chmodDirectory option try for each junk to change the directory permission and fails
[
https://issues.apache.org/jira/browse/CAMEL-19615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744476#comment-17744476
]
Claus Ibsen commented on CAMEL-19615:
-
You can send a PR with your code changes, thanks
> camel-ftp: chmodDirectory option try for each junk to change the directory
> permission and fails
> ---
>
> Key: CAMEL-19615
> URL: https://issues.apache.org/jira/browse/CAMEL-19615
> Project: Camel
> Issue Type: Improvement
> Components: camel-sftp
>Affects Versions: 3.18.2
>Reporter: Michael Rambichler
>Priority: Major
>
> We have a blocking issue with the current chmodDirectory option.
> [https://camel.apache.org/components/3.20.x/sftp-component.html#_endpoint_query_option_chmodDirectory]
>
> *Steps to reproduce:*
> SFTP Directory: ../home/user/restricted/dir/subdir (where restricted e.g.
> does not have change rights for the current user)
> Component Call:
> "sftp://localhost:21/home/user/restricted/dir/subdir/newDir; +
> "?username=admin=admin=777=770"
>
> *Behaviour:*
> The current implementation steps down the directory and try to create each
> junk. If the chmodDirectory option is set then i{color:#FF}t will try for
> each (already existing junk) to change the directory permission and
> fails.{color}
>
> *Expected Behaviour:*
> It should only try to change the permission if the directory does not yet
> exists
>
> I have already created a fix and added a Testcase for better debugging (but
> the Testcase does not reproduce the error because it would remove the
> permission for the current user and afterwards your need root rights to
> delete the Testdirectory again. Not suitable pipeline builds)
> [https://github.com/michael-salzburg/camel]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19615) camel-ftp: chmodDirectory
[
https://issues.apache.org/jira/browse/CAMEL-19615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-19615:
-
Summary: camel-ftp: chmodDirectory (was: camel-ftp)
> camel-ftp: chmodDirectory
> --
>
> Key: CAMEL-19615
> URL: https://issues.apache.org/jira/browse/CAMEL-19615
> Project: Camel
> Issue Type: Improvement
> Components: camel-sftp
>Affects Versions: 3.18.2
>Reporter: Michael Rambichler
>Priority: Major
>
> We have a blocking issue with the current chmodDirectory option.
> [https://camel.apache.org/components/3.20.x/sftp-component.html#_endpoint_query_option_chmodDirectory]
>
> *Steps to reproduce:*
> SFTP Directory: ../home/user/restricted/dir/subdir (where restricted e.g.
> does not have change rights for the current user)
> Component Call:
> "sftp://localhost:21/home/user/restricted/dir/subdir/newDir; +
> "?username=admin=admin=777=770"
>
> *Behaviour:*
> The current implementation steps down the directory and try to create each
> junk. If the chmodDirectory option is set then i{color:#FF}t will try for
> each (already existing junk) to change the directory permission and
> fails.{color}
>
> *Expected Behaviour:*
> It should only try to change the permission if the directory does not yet
> exists
>
> I have already created a fix and added a Testcase for better debugging (but
> the Testcase does not reproduce the error because it would remove the
> permission for the current user and afterwards your need root rights to
> delete the Testdirectory again. Not suitable pipeline builds)
> [https://github.com/michael-salzburg/camel]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19615) camel-ftp
[
https://issues.apache.org/jira/browse/CAMEL-19615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744471#comment-17744471
]
Michael Rambichler commented on CAMEL-19615:
If OK i can push my current fork into the branch.
> camel-ftp
> -
>
> Key: CAMEL-19615
> URL: https://issues.apache.org/jira/browse/CAMEL-19615
> Project: Camel
> Issue Type: Improvement
> Components: camel-sftp
>Affects Versions: 3.18.2
>Reporter: Michael Rambichler
>Priority: Major
>
> We have a blocking issue with the current chmodDirectory option.
> [https://camel.apache.org/components/3.20.x/sftp-component.html#_endpoint_query_option_chmodDirectory]
>
> *Steps to reproduce:*
> SFTP Directory: ../home/user/restricted/dir/subdir (where restricted e.g.
> does not have change rights for the current user)
> Component Call:
> "sftp://localhost:21/home/user/restricted/dir/subdir/newDir; +
> "?username=admin=admin=777=770"
>
> *Behaviour:*
> The current implementation steps down the directory and try to create each
> junk. If the chmodDirectory option is set then i{color:#FF}t will try for
> each (already existing junk) to change the directory permission and
> fails.{color}
>
> *Expected Behaviour:*
> It should only try to change the permission if the directory does not yet
> exists
>
> I have already created a fix and added a Testcase for better debugging (but
> the Testcase does not reproduce the error because it would remove the
> permission for the current user and afterwards your need root rights to
> delete the Testdirectory again. Not suitable pipeline builds)
> [https://github.com/michael-salzburg/camel]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19615) camel-ftp
Michael Rambichler created CAMEL-19615:
--
Summary: camel-ftp
Key: CAMEL-19615
URL: https://issues.apache.org/jira/browse/CAMEL-19615
Project: Camel
Issue Type: Improvement
Components: camel-sftp
Affects Versions: 3.18.2
Reporter: Michael Rambichler
We have a blocking issue with the current chmodDirectory option.
[https://camel.apache.org/components/3.20.x/sftp-component.html#_endpoint_query_option_chmodDirectory]
*Steps to reproduce:*
SFTP Directory: ../home/user/restricted/dir/subdir (where restricted e.g. does
not have change rights for the current user)
Component Call:
"sftp://localhost:21/home/user/restricted/dir/subdir/newDir; +
"?username=admin=admin=777=770"
*Behaviour:*
The current implementation steps down the directory and try to create each
junk. If the chmodDirectory option is set then i{color:#FF}t will try for
each (already existing junk) to change the directory permission and
fails.{color}
*Expected Behaviour:*
It should only try to change the permission if the directory does not yet exists
I have already created a fix and added a Testcase for better debugging (but the
Testcase does not reproduce the error because it would remove the permission
for the current user and afterwards your need root rights to delete the
Testdirectory again. Not suitable pipeline builds)
[https://github.com/michael-salzburg/camel]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19614) camel-openapi-rest-dsl-generator - Upgrade apicurio-data-models
[ https://issues.apache.org/jira/browse/CAMEL-19614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19614: Fix Version/s: 4.0-RC2 4.0.0 > camel-openapi-rest-dsl-generator - Upgrade apicurio-data-models > --- > > Key: CAMEL-19614 > URL: https://issues.apache.org/jira/browse/CAMEL-19614 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0-RC2, 4.0.0 > > > Unfortunately the model is not compatible in v1 to v2, and its a lot of pain > to upgrade. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19614) camel-openapi-rest-dsl-generator - Upgrade apicurio-data-models
[ https://issues.apache.org/jira/browse/CAMEL-19614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-19614: --- Assignee: Claus Ibsen > camel-openapi-rest-dsl-generator - Upgrade apicurio-data-models > --- > > Key: CAMEL-19614 > URL: https://issues.apache.org/jira/browse/CAMEL-19614 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > > Unfortunately the model is not compatible in v1 to v2, and its a lot of pain > to upgrade. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19614) camel-openapi-rest-dsl-generator - Upgrade apicurio-data-models
[ https://issues.apache.org/jira/browse/CAMEL-19614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19614: Component/s: tooling > camel-openapi-rest-dsl-generator - Upgrade apicurio-data-models > --- > > Key: CAMEL-19614 > URL: https://issues.apache.org/jira/browse/CAMEL-19614 > Project: Camel > Issue Type: Dependency upgrade > Components: tooling >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0-RC2, 4.0.0 > > > Unfortunately the model is not compatible in v1 to v2, and its a lot of pain > to upgrade. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19447) camel-kafka: investigate potential test cleanups
[ https://issues.apache.org/jira/browse/CAMEL-19447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744469#comment-17744469 ] Nikita commented on CAMEL-19447: Take this one > camel-kafka: investigate potential test cleanups > > > Key: CAMEL-19447 > URL: https://issues.apache.org/jira/browse/CAMEL-19447 > Project: Camel > Issue Type: Task > Components: camel-kafka >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Labels: easy > > It seems that there are a few minor cleanups that we can do on the tests for > the camel-kafka component. For instance, there seems to exist a few grammar > problems, lack of usage of final variables, threading issues and other > minor-problems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
