[jira] [Created] (CAMEL-12330) camel-rabbitmq - Allow to configure connection settings on component level
Claus Ibsen created CAMEL-12330: --- Summary: camel-rabbitmq - Allow to configure connection settings on component level Key: CAMEL-12330 URL: https://issues.apache.org/jira/browse/CAMEL-12330 Project: Camel Issue Type: Improvement Components: camel-rabbitmq Reporter: Claus Ibsen The component has no options. But we should allow to configure connection settings etc so you can configure this once. And also maybe let it auto-detect rabbitmq connection factory, so spring-boot users can just configure it the spring-boot way. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12329) camel-rabbitmq - Use another header for exchange override header in producer
Claus Ibsen created CAMEL-12329: --- Summary: camel-rabbitmq - Use another header for exchange override header in producer Key: CAMEL-12329 URL: https://issues.apache.org/jira/browse/CAMEL-12329 Project: Camel Issue Type: Improvement Components: camel-rabbitmq Reporter: Claus Ibsen See CAMEL-12324 We should not let rabbitmq.EXCHANGE_NAME be used as the override destination for the producer. As this can lead to the problem with from foo to bar Will route foo -> foo instead. So if the end user want to use a header to route to another destination that configured in the endpoint uri, you would need to use some other header for that, so rabbitmq.EXCHANGE_NAME becomes "read-only" and dont affect anything. This is also how JMS component works etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12324) Issue:Camel rabbitmq publishes message to consumer exchange instead of publisher exchange
[ https://issues.apache.org/jira/browse/CAMEL-12324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389192#comment-16389192 ] Claus Ibsen commented on CAMEL-12324: - Its a bit unfortunately but that is how the camel-rabbitmq component was originally created to do this. In the JMS component we have a special header for overriding what destination to send to so it wont do something like the rabbitmq component does. We should likely look at doing something similar. > Issue:Camel rabbitmq publishes message to consumer exchange instead of > publisher exchange > - > > Key: CAMEL-12324 > URL: https://issues.apache.org/jira/browse/CAMEL-12324 > Project: Camel > Issue Type: Bug > Components: camel-rabbitmq >Affects Versions: 2.20.0, 2.20.1, 2.20.2 >Reporter: zoheb >Priority: Major > Fix For: 2.21.0 > > Attachments: camel-rmq-test.zip > > > Hello Team, > I am facing issue when i tried to use camel rabbitmq components for version > 2.20.x. > The issue is happening when i have camel context containing route that > consumes from rabbitmq queue and publishes to rabbitmq exchange .What happens > is camel rabbitmq is publishing to consumer exchange instead of given > producer exchange and in this way it goes in infinite cycle. Here is sample > route for reference which can easily reproduce the issue. > > http://www.springframework.org/schema/beans; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xmlns:context="http://www.springframework.org/schema/context; > xmlns:camel="http://camel.apache.org/schema/spring; > xsi:schemaLocation=" > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans.xsd > http://www.springframework.org/schema/context > http://www.springframework.org/schema/context/spring-context.xsd > http://camel.apache.org/schema/spring > http://camel.apache.org/schema/spring/camel-spring.xsd;> > > > > > > > > > uri="rabbitmq://localhost:8311/test_exchange_in?username=adminpassword=adminvhost=/queue=test_queue_inautomaticRecoveryEnabled=trueconcurrentConsumers=2durable=falsearg.queue.x-message-ttl=5000networkRecoveryInterval=1" > /> > loggingLevel="INFO"/> > Message modified. > > uri="rabbitmq://localhost:8311/test_exchange_out?username=adminpassword=adminvhost=/skipQueueDeclare=trueexchangeType=headersautomaticRecoveryEnabled=trueautoDelete=falsenetworkRecoveryInterval=1" > /> > > > > > > > > > > > > I have also attached sample project to reproduce the issue. > Request you to please look into the issue and let us know the solution or fix > if any. > Thanks & regards, > Zoheb > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12324) Issue:Camel rabbitmq publishes message to consumer exchange instead of publisher exchange
[ https://issues.apache.org/jira/browse/CAMEL-12324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12324. - Resolution: Not A Bug Assignee: Claus Ibsen Fix Version/s: 2.21.0 > Issue:Camel rabbitmq publishes message to consumer exchange instead of > publisher exchange > - > > Key: CAMEL-12324 > URL: https://issues.apache.org/jira/browse/CAMEL-12324 > Project: Camel > Issue Type: Bug > Components: camel-rabbitmq >Affects Versions: 2.20.0, 2.20.1, 2.20.2 >Reporter: zoheb >Assignee: Claus Ibsen >Priority: Major > Fix For: 2.21.0 > > Attachments: camel-rmq-test.zip > > > Hello Team, > I am facing issue when i tried to use camel rabbitmq components for version > 2.20.x. > The issue is happening when i have camel context containing route that > consumes from rabbitmq queue and publishes to rabbitmq exchange .What happens > is camel rabbitmq is publishing to consumer exchange instead of given > producer exchange and in this way it goes in infinite cycle. Here is sample > route for reference which can easily reproduce the issue. > > http://www.springframework.org/schema/beans; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xmlns:context="http://www.springframework.org/schema/context; > xmlns:camel="http://camel.apache.org/schema/spring; > xsi:schemaLocation=" > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans.xsd > http://www.springframework.org/schema/context > http://www.springframework.org/schema/context/spring-context.xsd > http://camel.apache.org/schema/spring > http://camel.apache.org/schema/spring/camel-spring.xsd;> > > > > > > > > > uri="rabbitmq://localhost:8311/test_exchange_in?username=adminpassword=adminvhost=/queue=test_queue_inautomaticRecoveryEnabled=trueconcurrentConsumers=2durable=falsearg.queue.x-message-ttl=5000networkRecoveryInterval=1" > /> > loggingLevel="INFO"/> > Message modified. > > uri="rabbitmq://localhost:8311/test_exchange_out?username=adminpassword=adminvhost=/skipQueueDeclare=trueexchangeType=headersautomaticRecoveryEnabled=trueautoDelete=falsenetworkRecoveryInterval=1" > /> > > > > > > > > > > > > I have also attached sample project to reproduce the issue. > Request you to please look into the issue and let us know the solution or fix > if any. > Thanks & regards, > Zoheb > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12324) Issue:Camel rabbitmq publishes message to consumer exchange instead of publisher exchange
[ https://issues.apache.org/jira/browse/CAMEL-12324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389191#comment-16389191 ] Claus Ibsen commented on CAMEL-12324: - I have improved the docs to explain about this https://github.com/apache/camel/blob/master/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc#routing-between-exchanges > Issue:Camel rabbitmq publishes message to consumer exchange instead of > publisher exchange > - > > Key: CAMEL-12324 > URL: https://issues.apache.org/jira/browse/CAMEL-12324 > Project: Camel > Issue Type: Bug > Components: camel-rabbitmq >Affects Versions: 2.20.0, 2.20.1, 2.20.2 >Reporter: zoheb >Priority: Major > Attachments: camel-rmq-test.zip > > > Hello Team, > I am facing issue when i tried to use camel rabbitmq components for version > 2.20.x. > The issue is happening when i have camel context containing route that > consumes from rabbitmq queue and publishes to rabbitmq exchange .What happens > is camel rabbitmq is publishing to consumer exchange instead of given > producer exchange and in this way it goes in infinite cycle. Here is sample > route for reference which can easily reproduce the issue. > > http://www.springframework.org/schema/beans; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xmlns:context="http://www.springframework.org/schema/context; > xmlns:camel="http://camel.apache.org/schema/spring; > xsi:schemaLocation=" > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans.xsd > http://www.springframework.org/schema/context > http://www.springframework.org/schema/context/spring-context.xsd > http://camel.apache.org/schema/spring > http://camel.apache.org/schema/spring/camel-spring.xsd;> > > > > > > > > > uri="rabbitmq://localhost:8311/test_exchange_in?username=adminpassword=adminvhost=/queue=test_queue_inautomaticRecoveryEnabled=trueconcurrentConsumers=2durable=falsearg.queue.x-message-ttl=5000networkRecoveryInterval=1" > /> > loggingLevel="INFO"/> > Message modified. > > uri="rabbitmq://localhost:8311/test_exchange_out?username=adminpassword=adminvhost=/skipQueueDeclare=trueexchangeType=headersautomaticRecoveryEnabled=trueautoDelete=falsenetworkRecoveryInterval=1" > /> > > > > > > > > > > > > I have also attached sample project to reproduce the issue. > Request you to please look into the issue and let us know the solution or fix > if any. > Thanks & regards, > Zoheb > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12328) Headers getting lost after calling kubernetes-services API
[ https://issues.apache.org/jira/browse/CAMEL-12328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389188#comment-16389188 ] Andrea Cosentino commented on CAMEL-12328: -- Yes, the copy headers like other resources already use is missing in services Producers. [https://github.com/apache/camel/blob/camel-2.20.x/components/camel-kubernetes/src/main/java/org/apache/camel/component/kubernetes/deployments/KubernetesDeploymentsProducer.java#L119] I'll fix this. > Headers getting lost after calling kubernetes-services API > -- > > Key: CAMEL-12328 > URL: https://issues.apache.org/jira/browse/CAMEL-12328 > Project: Camel > Issue Type: Bug > Components: camel-kubernetes >Affects Versions: 2.20.2 >Reporter: Pradeesh >Assignee: Andrea Cosentino >Priority: Major > > Header set by user is getting removed after calling Kubernetes-services API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12324) Issue:Camel rabbitmq publishes message to consumer exchange instead of publisher exchange
[ https://issues.apache.org/jira/browse/CAMEL-12324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389183#comment-16389183 ] Claus Ibsen commented on CAMEL-12324: - You need to either * remove the `rabbitmq.EXCHANGE_NAME` header before sending, or * turn on bridge endpoint which would ignore this header and send it to the exchange set on the endpoint uri eg in your camel:to add the option: bridgeEndpoint=true > Issue:Camel rabbitmq publishes message to consumer exchange instead of > publisher exchange > - > > Key: CAMEL-12324 > URL: https://issues.apache.org/jira/browse/CAMEL-12324 > Project: Camel > Issue Type: Bug > Components: camel-rabbitmq >Affects Versions: 2.20.0, 2.20.1, 2.20.2 >Reporter: zoheb >Priority: Major > Attachments: camel-rmq-test.zip > > > Hello Team, > I am facing issue when i tried to use camel rabbitmq components for version > 2.20.x. > The issue is happening when i have camel context containing route that > consumes from rabbitmq queue and publishes to rabbitmq exchange .What happens > is camel rabbitmq is publishing to consumer exchange instead of given > producer exchange and in this way it goes in infinite cycle. Here is sample > route for reference which can easily reproduce the issue. > > http://www.springframework.org/schema/beans; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xmlns:context="http://www.springframework.org/schema/context; > xmlns:camel="http://camel.apache.org/schema/spring; > xsi:schemaLocation=" > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans.xsd > http://www.springframework.org/schema/context > http://www.springframework.org/schema/context/spring-context.xsd > http://camel.apache.org/schema/spring > http://camel.apache.org/schema/spring/camel-spring.xsd;> > > > > > > > > > uri="rabbitmq://localhost:8311/test_exchange_in?username=adminpassword=adminvhost=/queue=test_queue_inautomaticRecoveryEnabled=trueconcurrentConsumers=2durable=falsearg.queue.x-message-ttl=5000networkRecoveryInterval=1" > /> > loggingLevel="INFO"/> > Message modified. > > uri="rabbitmq://localhost:8311/test_exchange_out?username=adminpassword=adminvhost=/skipQueueDeclare=trueexchangeType=headersautomaticRecoveryEnabled=trueautoDelete=falsenetworkRecoveryInterval=1" > /> > > > > > > > > > > > > I have also attached sample project to reproduce the issue. > Request you to please look into the issue and let us know the solution or fix > if any. > Thanks & regards, > Zoheb > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12328) Headers getting lost after calling kubernetes-services API
[ https://issues.apache.org/jira/browse/CAMEL-12328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-12328: Assignee: Andrea Cosentino > Headers getting lost after calling kubernetes-services API > -- > > Key: CAMEL-12328 > URL: https://issues.apache.org/jira/browse/CAMEL-12328 > Project: Camel > Issue Type: Bug > Components: camel-kubernetes >Affects Versions: 2.20.2 >Reporter: Pradeesh >Assignee: Andrea Cosentino >Priority: Major > > Header set by user is getting removed after calling Kubernetes-services API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12328) Headers getting lost after calling kubernetes-services API
Pradeesh created CAMEL-12328: Summary: Headers getting lost after calling kubernetes-services API Key: CAMEL-12328 URL: https://issues.apache.org/jira/browse/CAMEL-12328 Project: Camel Issue Type: Bug Components: camel-kubernetes Affects Versions: 2.20.2 Reporter: Pradeesh Header set by user is getting removed after calling Kubernetes-services API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12327) camel-infinispan - Add GET check before PUT on add operation in idempontent repository
Claus Ibsen created CAMEL-12327: --- Summary: camel-infinispan - Add GET check before PUT on add operation in idempontent repository Key: CAMEL-12327 URL: https://issues.apache.org/jira/browse/CAMEL-12327 Project: Camel Issue Type: Improvement Components: camel-infinispan Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 2.21.0 See the comment on this SO [https://stackoverflow.com/questions/49123757/camel-idempotentconsumer-always-use-put-instead-of-get/49125815#49125815] The PUT causes the item to be refreshed and cannot expire its cache lifespan. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12326) Improve CamelCxfClientImpl a bit ensure it can handle camel side usecase
[ https://issues.apache.org/jira/browse/CAMEL-12326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CAMEL-12326. -- Resolution: Fixed Fix Version/s: 2.21.0 > Improve CamelCxfClientImpl a bit ensure it can handle camel side usecase > > > Key: CAMEL-12326 > URL: https://issues.apache.org/jira/browse/CAMEL-12326 > Project: Camel > Issue Type: Improvement > Components: camel-cxf >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > Fix For: 2.21.0 > > > when use camel-cxf as bridge which isn't in POJO mode, the camel-cxf > producer(CamelCxfClientImpl) needn't check if there is any content in the > return list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12326) Improve CamelCxfClientImpl a bit ensure it can handle camel side usecase
[ https://issues.apache.org/jira/browse/CAMEL-12326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CAMEL-12326: Assignee: Freeman Fang > Improve CamelCxfClientImpl a bit ensure it can handle camel side usecase > > > Key: CAMEL-12326 > URL: https://issues.apache.org/jira/browse/CAMEL-12326 > Project: Camel > Issue Type: Improvement > Components: camel-cxf >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > when use camel-cxf as bridge which isn't in POJO mode, the camel-cxf > producer(CamelCxfClientImpl) needn't check if there is any content in the > return list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12326) Improve CamelCxfClientImpl a bit ensure it can handle camel side usecase
Freeman Fang created CAMEL-12326: Summary: Improve CamelCxfClientImpl a bit ensure it can handle camel side usecase Key: CAMEL-12326 URL: https://issues.apache.org/jira/browse/CAMEL-12326 Project: Camel Issue Type: Improvement Components: camel-cxf Reporter: Freeman Fang when use camel-cxf as bridge which isn't in POJO mode, the camel-cxf producer(CamelCxfClientImpl) needn't check if there is any content in the return list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-12324) Issue:Camel rabbitmq publishes message to consumer exchange instead of publisher exchange
[ https://issues.apache.org/jira/browse/CAMEL-12324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1636#comment-1636 ] zoheb edited comment on CAMEL-12324 at 3/7/18 4:17 AM: --- Hi Andrea, I think this is a bug in camel 2.20.x rabbitmq component I tried many things but it didn't worked. As per your recommendation I have also published issue to camel user mailing list. Request team to please look into this as it is a major blocker in case camel context contains route that consume from rabbitmq and publishes to rabbitmq. was (Author: zohebp): Hi Andrea, I think this is a bug in camel 2.20.x rabbitmq component I tried many things but it didn't worked. Request team to please look into this as it is a major blocker in case camel context contains route that consume from rabbitmq and publishes to rabbitmq. > Issue:Camel rabbitmq publishes message to consumer exchange instead of > publisher exchange > - > > Key: CAMEL-12324 > URL: https://issues.apache.org/jira/browse/CAMEL-12324 > Project: Camel > Issue Type: Bug > Components: camel-rabbitmq >Affects Versions: 2.20.0, 2.20.1, 2.20.2 >Reporter: zoheb >Priority: Major > Attachments: camel-rmq-test.zip > > > Hello Team, > I am facing issue when i tried to use camel rabbitmq components for version > 2.20.x. > The issue is happening when i have camel context containing route that > consumes from rabbitmq queue and publishes to rabbitmq exchange .What happens > is camel rabbitmq is publishing to consumer exchange instead of given > producer exchange and in this way it goes in infinite cycle. Here is sample > route for reference which can easily reproduce the issue. > > http://www.springframework.org/schema/beans; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xmlns:context="http://www.springframework.org/schema/context; > xmlns:camel="http://camel.apache.org/schema/spring; > xsi:schemaLocation=" > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans.xsd > http://www.springframework.org/schema/context > http://www.springframework.org/schema/context/spring-context.xsd > http://camel.apache.org/schema/spring > http://camel.apache.org/schema/spring/camel-spring.xsd;> > > > > > > > > > uri="rabbitmq://localhost:8311/test_exchange_in?username=adminpassword=adminvhost=/queue=test_queue_inautomaticRecoveryEnabled=trueconcurrentConsumers=2durable=falsearg.queue.x-message-ttl=5000networkRecoveryInterval=1" > /> > loggingLevel="INFO"/> > Message modified. > > uri="rabbitmq://localhost:8311/test_exchange_out?username=adminpassword=adminvhost=/skipQueueDeclare=trueexchangeType=headersautomaticRecoveryEnabled=trueautoDelete=falsenetworkRecoveryInterval=1" > /> > > > > > > > > > > > > I have also attached sample project to reproduce the issue. > Request you to please look into the issue and let us know the solution or fix > if any. > Thanks & regards, > Zoheb > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (CAMEL-12324) Issue:Camel rabbitmq publishes message to consumer exchange instead of publisher exchange
[ https://issues.apache.org/jira/browse/CAMEL-12324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zoheb reopened CAMEL-12324: --- > Issue:Camel rabbitmq publishes message to consumer exchange instead of > publisher exchange > - > > Key: CAMEL-12324 > URL: https://issues.apache.org/jira/browse/CAMEL-12324 > Project: Camel > Issue Type: Bug > Components: camel-rabbitmq >Affects Versions: 2.20.0, 2.20.1, 2.20.2 >Reporter: zoheb >Priority: Major > Attachments: camel-rmq-test.zip > > > Hello Team, > I am facing issue when i tried to use camel rabbitmq components for version > 2.20.x. > The issue is happening when i have camel context containing route that > consumes from rabbitmq queue and publishes to rabbitmq exchange .What happens > is camel rabbitmq is publishing to consumer exchange instead of given > producer exchange and in this way it goes in infinite cycle. Here is sample > route for reference which can easily reproduce the issue. > > http://www.springframework.org/schema/beans; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xmlns:context="http://www.springframework.org/schema/context; > xmlns:camel="http://camel.apache.org/schema/spring; > xsi:schemaLocation=" > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans.xsd > http://www.springframework.org/schema/context > http://www.springframework.org/schema/context/spring-context.xsd > http://camel.apache.org/schema/spring > http://camel.apache.org/schema/spring/camel-spring.xsd;> > > > > > > > > > uri="rabbitmq://localhost:8311/test_exchange_in?username=adminpassword=adminvhost=/queue=test_queue_inautomaticRecoveryEnabled=trueconcurrentConsumers=2durable=falsearg.queue.x-message-ttl=5000networkRecoveryInterval=1" > /> > loggingLevel="INFO"/> > Message modified. > > uri="rabbitmq://localhost:8311/test_exchange_out?username=adminpassword=adminvhost=/skipQueueDeclare=trueexchangeType=headersautomaticRecoveryEnabled=trueautoDelete=falsenetworkRecoveryInterval=1" > /> > > > > > > > > > > > > I have also attached sample project to reproduce the issue. > Request you to please look into the issue and let us know the solution or fix > if any. > Thanks & regards, > Zoheb > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-12324) Issue:Camel rabbitmq publishes message to consumer exchange instead of publisher exchange
[ https://issues.apache.org/jira/browse/CAMEL-12324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1636#comment-1636 ] zoheb edited comment on CAMEL-12324 at 3/7/18 4:06 AM: --- Hi Andrea, I think this is a bug in camel 2.20.x rabbitmq component I tried many things but it didn't worked. Request team to please look into this as it is a major blocker in case camel context contains route that consume from rabbitmq and publishes to rabbitmq. was (Author: zohebp): Hi Andrea, I think this is a bug in camel 2.20.x rabbitmq component I tried many things but it didn't worked. Request team to please look into this as it is a major blocker in case camel context contains route that consumer from rabbitmq and publishes to rabbitmq. > Issue:Camel rabbitmq publishes message to consumer exchange instead of > publisher exchange > - > > Key: CAMEL-12324 > URL: https://issues.apache.org/jira/browse/CAMEL-12324 > Project: Camel > Issue Type: Bug > Components: camel-rabbitmq >Affects Versions: 2.20.0, 2.20.1, 2.20.2 >Reporter: zoheb >Priority: Major > Attachments: camel-rmq-test.zip > > > Hello Team, > I am facing issue when i tried to use camel rabbitmq components for version > 2.20.x. > The issue is happening when i have camel context containing route that > consumes from rabbitmq queue and publishes to rabbitmq exchange .What happens > is camel rabbitmq is publishing to consumer exchange instead of given > producer exchange and in this way it goes in infinite cycle. Here is sample > route for reference which can easily reproduce the issue. > > http://www.springframework.org/schema/beans; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xmlns:context="http://www.springframework.org/schema/context; > xmlns:camel="http://camel.apache.org/schema/spring; > xsi:schemaLocation=" > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans.xsd > http://www.springframework.org/schema/context > http://www.springframework.org/schema/context/spring-context.xsd > http://camel.apache.org/schema/spring > http://camel.apache.org/schema/spring/camel-spring.xsd;> > > > > > > > > > uri="rabbitmq://localhost:8311/test_exchange_in?username=adminpassword=adminvhost=/queue=test_queue_inautomaticRecoveryEnabled=trueconcurrentConsumers=2durable=falsearg.queue.x-message-ttl=5000networkRecoveryInterval=1" > /> > loggingLevel="INFO"/> > Message modified. > > uri="rabbitmq://localhost:8311/test_exchange_out?username=adminpassword=adminvhost=/skipQueueDeclare=trueexchangeType=headersautomaticRecoveryEnabled=trueautoDelete=falsenetworkRecoveryInterval=1" > /> > > > > > > > > > > > > I have also attached sample project to reproduce the issue. > Request you to please look into the issue and let us know the solution or fix > if any. > Thanks & regards, > Zoheb > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12324) Issue:Camel rabbitmq publishes message to consumer exchange instead of publisher exchange
[ https://issues.apache.org/jira/browse/CAMEL-12324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1636#comment-1636 ] zoheb commented on CAMEL-12324: --- Hi Andrea, I think this is a bug in camel 2.20.x rabbitmq component I tried many things but it didn't worked. Request team to please look into this as it is a major blocker in case camel context contains route that consumer from rabbitmq and publishes to rabbitmq. > Issue:Camel rabbitmq publishes message to consumer exchange instead of > publisher exchange > - > > Key: CAMEL-12324 > URL: https://issues.apache.org/jira/browse/CAMEL-12324 > Project: Camel > Issue Type: Bug > Components: camel-rabbitmq >Affects Versions: 2.20.0, 2.20.1, 2.20.2 >Reporter: zoheb >Priority: Major > Attachments: camel-rmq-test.zip > > > Hello Team, > I am facing issue when i tried to use camel rabbitmq components for version > 2.20.x. > The issue is happening when i have camel context containing route that > consumes from rabbitmq queue and publishes to rabbitmq exchange .What happens > is camel rabbitmq is publishing to consumer exchange instead of given > producer exchange and in this way it goes in infinite cycle. Here is sample > route for reference which can easily reproduce the issue. > > http://www.springframework.org/schema/beans; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xmlns:context="http://www.springframework.org/schema/context; > xmlns:camel="http://camel.apache.org/schema/spring; > xsi:schemaLocation=" > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans.xsd > http://www.springframework.org/schema/context > http://www.springframework.org/schema/context/spring-context.xsd > http://camel.apache.org/schema/spring > http://camel.apache.org/schema/spring/camel-spring.xsd;> > > > > > > > > > uri="rabbitmq://localhost:8311/test_exchange_in?username=adminpassword=adminvhost=/queue=test_queue_inautomaticRecoveryEnabled=trueconcurrentConsumers=2durable=falsearg.queue.x-message-ttl=5000networkRecoveryInterval=1" > /> > loggingLevel="INFO"/> > Message modified. > > uri="rabbitmq://localhost:8311/test_exchange_out?username=adminpassword=adminvhost=/skipQueueDeclare=trueexchangeType=headersautomaticRecoveryEnabled=trueautoDelete=falsenetworkRecoveryInterval=1" > /> > > > > > > > > > > > > I have also attached sample project to reproduce the issue. > Request you to please look into the issue and let us know the solution or fix > if any. > Thanks & regards, > Zoheb > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12325) lastConnectionActivityTicks is not getting updated by MllpTcpClientProducer
[ https://issues.apache.org/jira/browse/CAMEL-12325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quinn Stevenson resolved CAMEL-12325. - Resolution: Fixed Fix Version/s: 2.21.0 Fixed with commit e2b10183ba735986102799e8d1be28111f11cfc6 > lastConnectionActivityTicks is not getting updated by MllpTcpClientProducer > --- > > Key: CAMEL-12325 > URL: https://issues.apache.org/jira/browse/CAMEL-12325 > Project: Camel > Issue Type: Bug > Components: camel-mllp >Reporter: Quinn Stevenson >Assignee: Quinn Stevenson >Priority: Major > Fix For: 2.21.0 > > > The producer is not updating the last activity timestamp, which is causing > idleTimeout to not work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12325) lastConnectionActivityTicks is not getting updated by MllpTcpClientProducer
Quinn Stevenson created CAMEL-12325: --- Summary: lastConnectionActivityTicks is not getting updated by MllpTcpClientProducer Key: CAMEL-12325 URL: https://issues.apache.org/jira/browse/CAMEL-12325 Project: Camel Issue Type: Bug Components: camel-mllp Reporter: Quinn Stevenson Assignee: Quinn Stevenson The producer is not updating the last activity timestamp, which is causing idleTimeout to not work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12324) Issue:Camel rabbitmq publishes message to consumer exchange instead of publisher exchange
[ https://issues.apache.org/jira/browse/CAMEL-12324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-12324. -- Resolution: Invalid Ask on mailing list first > Issue:Camel rabbitmq publishes message to consumer exchange instead of > publisher exchange > - > > Key: CAMEL-12324 > URL: https://issues.apache.org/jira/browse/CAMEL-12324 > Project: Camel > Issue Type: Bug > Components: camel-rabbitmq >Affects Versions: 2.20.0, 2.20.1, 2.20.2 >Reporter: zoheb >Priority: Major > Attachments: camel-rmq-test.zip > > > Hello Team, > I am facing issue when i tried to use camel rabbitmq components for version > 2.20.x. > The issue is happening when i have camel context containing route that > consumes from rabbitmq queue and publishes to rabbitmq exchange .What happens > is camel rabbitmq is publishing to consumer exchange instead of given > producer exchange and in this way it goes in infinite cycle. Here is sample > route for reference which can easily reproduce the issue. > > http://www.springframework.org/schema/beans; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xmlns:context="http://www.springframework.org/schema/context; > xmlns:camel="http://camel.apache.org/schema/spring; > xsi:schemaLocation=" > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans.xsd > http://www.springframework.org/schema/context > http://www.springframework.org/schema/context/spring-context.xsd > http://camel.apache.org/schema/spring > http://camel.apache.org/schema/spring/camel-spring.xsd;> > > > > > > > > > uri="rabbitmq://localhost:8311/test_exchange_in?username=adminpassword=adminvhost=/queue=test_queue_inautomaticRecoveryEnabled=trueconcurrentConsumers=2durable=falsearg.queue.x-message-ttl=5000networkRecoveryInterval=1" > /> > loggingLevel="INFO"/> > Message modified. > > uri="rabbitmq://localhost:8311/test_exchange_out?username=adminpassword=adminvhost=/skipQueueDeclare=trueexchangeType=headersautomaticRecoveryEnabled=trueautoDelete=falsenetworkRecoveryInterval=1" > /> > > > > > > > > > > > > I have also attached sample project to reproduce the issue. > Request you to please look into the issue and let us know the solution or fix > if any. > Thanks & regards, > Zoheb > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12324) Issue:Camel rabbitmq publishes message to consumer exchange instead of publisher exchange
zoheb created CAMEL-12324: - Summary: Issue:Camel rabbitmq publishes message to consumer exchange instead of publisher exchange Key: CAMEL-12324 URL: https://issues.apache.org/jira/browse/CAMEL-12324 Project: Camel Issue Type: Bug Components: camel-rabbitmq Affects Versions: 2.20.2, 2.20.1, 2.20.0 Reporter: zoheb Attachments: camel-rmq-test.zip Hello Team, I am facing issue when i tried to use camel rabbitmq components for version 2.20.x. The issue is happening when i have camel context containing route that consumes from rabbitmq queue and publishes to rabbitmq exchange .What happens is camel rabbitmq is publishing to consumer exchange instead of given producer exchange and in this way it goes in infinite cycle. Here is sample route for reference which can easily reproduce the issue. http://www.springframework.org/schema/beans; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns:context="http://www.springframework.org/schema/context; xmlns:camel="http://camel.apache.org/schema/spring; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context.xsd http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd;> Message modified. I have also attached sample project to reproduce the issue. Request you to please look into the issue and let us know the solution or fix if any. Thanks & regards, Zoheb -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-12034) camel-elasticsearch5 - Search Operation: If Map or String is used in Message Body, "size" and "from" parameters are always ignored
[
https://issues.apache.org/jira/browse/CAMEL-12034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-12034.
-
Resolution: Fixed
> camel-elasticsearch5 - Search Operation: If Map or String is used in Message
> Body, "size" and "from" parameters are always ignored
> --
>
> Key: CAMEL-12034
> URL: https://issues.apache.org/jira/browse/CAMEL-12034
> Project: Camel
> Issue Type: Improvement
> Components: camel-elasticsearch5
>Affects Versions: 2.20.1
>Reporter: Radoslav Cincala
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.3, 2.21.0
>
>
> Hi,
> I am using camel-elasticsearch5 component of Camel 2.20.1.
> I have found and issue. The description follows.
> *If you use Map or String in message body for SEARCH operation, "size" and
> "from" parameters are always ignored hence you always get just default 10
> results.*
> For example - if your map contains query like this:
> (in terms of simplicity - following is String representation of the map):
> {code}
> {size=50, query={query_string={query=status:ACTIVE}}, from=0}
> {code}
> Issue I suspect is present in class:
> _org.apache.camel.component.elasticsearch5.converter.ElasticsearchActionRequestConverter_
> and its method
> _public static SearchRequest toSearchRequest(Object queryObject, Exchange
> exchange)_
> {code}
> // line 191...
> if (queryObject instanceof Map) {
> Map mapQuery = (Map)queryObject;
> // Remove 'query' prefix from the query object for backward
> compatibility
> if
> (mapQuery.containsKey(ElasticsearchConstants.ES_QUERY_DSL_PREFIX)) {
> mapQuery = (Map Object>)mapQuery.get(ElasticsearchConstants.ES_QUERY_DSL_PREFIX);
> }
> try {
> XContentBuilder contentBuilder =
> XContentFactory.contentBuilder(XContentType.JSON);
> queryText = contentBuilder.map(mapQuery).string();
> } catch (IOException e) {
> LOG.error(e.getMessage());
> }
> }
> // queryText then used on line 220...
> searchSourceBuilder.query(QueryBuilders.wrapperQuery(queryText));
> searchRequest.source(searchSourceBuilder);
> return searchRequest;
> {code}
> Inner if condition basically extracts only query part from the map
> {code}
> query={query_string={query=status:ACTIVE}
> {code}
> and *"size" and "from" get lost from the query*
> {code}
> // line 194...
> if (mapQuery.containsKey(ElasticsearchConstants.ES_QUERY_DSL_PREFIX)) {
> mapQuery = (Map Object>)mapQuery.get(ElasticsearchConstants.ES_QUERY_DSL_PREFIX);
> // ...where ElasticsearchConstants.ES_QUERY_DSL_PREFIX = "query"
> }
> {code}
> Same issue is with usage of the String in the message body:
> {code}
> // line 203
> } else if (queryObject instanceof String) {
> queryText = (String)queryObject;
> ObjectMapper mapper = new ObjectMapper();
> try {
> JsonNode jsonTextObject = mapper.readValue(queryText,
> JsonNode.class);
> JsonNode parentJsonNode =
> jsonTextObject.get(ElasticsearchConstants.ES_QUERY_DSL_PREFIX);
> if (parentJsonNode != null) {
> queryText = parentJsonNode.toString();
> }
> } catch (IOException e) {
> LOG.error(e.getMessage());
> }
> }
> {code}
> Only workaround for this is to use *SearchRequest* object in a message body
> where you can explicitly set "size" and "from" on SearchSourceBuilder object.
> For example:
> {code}
> SearchRequest searchRequest = new SearchRequest("my_index")
> .types("my_type")
> .source(new
> SearchSourceBuilder().query(QueryBuilders.wrapperQuery("my:query"))
> .size(50).from(0));
> {code}
> I don't know what was the developer's intention for having such a condition
> which removes these parameters from the query.
> Thank you very much in advance if anybody can have a look and verify if this
> is a valid concern.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-12034) camel-elasticsearch5 - Search Operation: If Map or String is used in Message Body, "size" and "from" parameters are always ignored
[
https://issues.apache.org/jira/browse/CAMEL-12034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-12034:
Issue Type: Improvement (was: Bug)
> camel-elasticsearch5 - Search Operation: If Map or String is used in Message
> Body, "size" and "from" parameters are always ignored
> --
>
> Key: CAMEL-12034
> URL: https://issues.apache.org/jira/browse/CAMEL-12034
> Project: Camel
> Issue Type: Improvement
> Components: camel-elasticsearch5
>Affects Versions: 2.20.1
>Reporter: Radoslav Cincala
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.3, 2.21.0
>
>
> Hi,
> I am using camel-elasticsearch5 component of Camel 2.20.1.
> I have found and issue. The description follows.
> *If you use Map or String in message body for SEARCH operation, "size" and
> "from" parameters are always ignored hence you always get just default 10
> results.*
> For example - if your map contains query like this:
> (in terms of simplicity - following is String representation of the map):
> {code}
> {size=50, query={query_string={query=status:ACTIVE}}, from=0}
> {code}
> Issue I suspect is present in class:
> _org.apache.camel.component.elasticsearch5.converter.ElasticsearchActionRequestConverter_
> and its method
> _public static SearchRequest toSearchRequest(Object queryObject, Exchange
> exchange)_
> {code}
> // line 191...
> if (queryObject instanceof Map) {
> Map mapQuery = (Map)queryObject;
> // Remove 'query' prefix from the query object for backward
> compatibility
> if
> (mapQuery.containsKey(ElasticsearchConstants.ES_QUERY_DSL_PREFIX)) {
> mapQuery = (Map Object>)mapQuery.get(ElasticsearchConstants.ES_QUERY_DSL_PREFIX);
> }
> try {
> XContentBuilder contentBuilder =
> XContentFactory.contentBuilder(XContentType.JSON);
> queryText = contentBuilder.map(mapQuery).string();
> } catch (IOException e) {
> LOG.error(e.getMessage());
> }
> }
> // queryText then used on line 220...
> searchSourceBuilder.query(QueryBuilders.wrapperQuery(queryText));
> searchRequest.source(searchSourceBuilder);
> return searchRequest;
> {code}
> Inner if condition basically extracts only query part from the map
> {code}
> query={query_string={query=status:ACTIVE}
> {code}
> and *"size" and "from" get lost from the query*
> {code}
> // line 194...
> if (mapQuery.containsKey(ElasticsearchConstants.ES_QUERY_DSL_PREFIX)) {
> mapQuery = (Map Object>)mapQuery.get(ElasticsearchConstants.ES_QUERY_DSL_PREFIX);
> // ...where ElasticsearchConstants.ES_QUERY_DSL_PREFIX = "query"
> }
> {code}
> Same issue is with usage of the String in the message body:
> {code}
> // line 203
> } else if (queryObject instanceof String) {
> queryText = (String)queryObject;
> ObjectMapper mapper = new ObjectMapper();
> try {
> JsonNode jsonTextObject = mapper.readValue(queryText,
> JsonNode.class);
> JsonNode parentJsonNode =
> jsonTextObject.get(ElasticsearchConstants.ES_QUERY_DSL_PREFIX);
> if (parentJsonNode != null) {
> queryText = parentJsonNode.toString();
> }
> } catch (IOException e) {
> LOG.error(e.getMessage());
> }
> }
> {code}
> Only workaround for this is to use *SearchRequest* object in a message body
> where you can explicitly set "size" and "from" on SearchSourceBuilder object.
> For example:
> {code}
> SearchRequest searchRequest = new SearchRequest("my_index")
> .types("my_type")
> .source(new
> SearchSourceBuilder().query(QueryBuilders.wrapperQuery("my:query"))
> .size(50).from(0));
> {code}
> I don't know what was the developer's intention for having such a condition
> which removes these parameters from the query.
> Thank you very much in advance if anybody can have a look and verify if this
> is a valid concern.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12034) camel-elasticsearch5 - Search Operation: If Map or String is used in Message Body, "size" and "from" parameters are always ignored
[
https://issues.apache.org/jira/browse/CAMEL-12034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387731#comment-16387731
]
Claus Ibsen commented on CAMEL-12034:
-
This was not really intended, but I am adding support for providing from and
size in the map / json string
> camel-elasticsearch5 - Search Operation: If Map or String is used in Message
> Body, "size" and "from" parameters are always ignored
> --
>
> Key: CAMEL-12034
> URL: https://issues.apache.org/jira/browse/CAMEL-12034
> Project: Camel
> Issue Type: Improvement
> Components: camel-elasticsearch5
>Affects Versions: 2.20.1
>Reporter: Radoslav Cincala
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.3, 2.21.0
>
>
> Hi,
> I am using camel-elasticsearch5 component of Camel 2.20.1.
> I have found and issue. The description follows.
> *If you use Map or String in message body for SEARCH operation, "size" and
> "from" parameters are always ignored hence you always get just default 10
> results.*
> For example - if your map contains query like this:
> (in terms of simplicity - following is String representation of the map):
> {code}
> {size=50, query={query_string={query=status:ACTIVE}}, from=0}
> {code}
> Issue I suspect is present in class:
> _org.apache.camel.component.elasticsearch5.converter.ElasticsearchActionRequestConverter_
> and its method
> _public static SearchRequest toSearchRequest(Object queryObject, Exchange
> exchange)_
> {code}
> // line 191...
> if (queryObject instanceof Map) {
> Map mapQuery = (Map)queryObject;
> // Remove 'query' prefix from the query object for backward
> compatibility
> if
> (mapQuery.containsKey(ElasticsearchConstants.ES_QUERY_DSL_PREFIX)) {
> mapQuery = (Map Object>)mapQuery.get(ElasticsearchConstants.ES_QUERY_DSL_PREFIX);
> }
> try {
> XContentBuilder contentBuilder =
> XContentFactory.contentBuilder(XContentType.JSON);
> queryText = contentBuilder.map(mapQuery).string();
> } catch (IOException e) {
> LOG.error(e.getMessage());
> }
> }
> // queryText then used on line 220...
> searchSourceBuilder.query(QueryBuilders.wrapperQuery(queryText));
> searchRequest.source(searchSourceBuilder);
> return searchRequest;
> {code}
> Inner if condition basically extracts only query part from the map
> {code}
> query={query_string={query=status:ACTIVE}
> {code}
> and *"size" and "from" get lost from the query*
> {code}
> // line 194...
> if (mapQuery.containsKey(ElasticsearchConstants.ES_QUERY_DSL_PREFIX)) {
> mapQuery = (Map Object>)mapQuery.get(ElasticsearchConstants.ES_QUERY_DSL_PREFIX);
> // ...where ElasticsearchConstants.ES_QUERY_DSL_PREFIX = "query"
> }
> {code}
> Same issue is with usage of the String in the message body:
> {code}
> // line 203
> } else if (queryObject instanceof String) {
> queryText = (String)queryObject;
> ObjectMapper mapper = new ObjectMapper();
> try {
> JsonNode jsonTextObject = mapper.readValue(queryText,
> JsonNode.class);
> JsonNode parentJsonNode =
> jsonTextObject.get(ElasticsearchConstants.ES_QUERY_DSL_PREFIX);
> if (parentJsonNode != null) {
> queryText = parentJsonNode.toString();
> }
> } catch (IOException e) {
> LOG.error(e.getMessage());
> }
> }
> {code}
> Only workaround for this is to use *SearchRequest* object in a message body
> where you can explicitly set "size" and "from" on SearchSourceBuilder object.
> For example:
> {code}
> SearchRequest searchRequest = new SearchRequest("my_index")
> .types("my_type")
> .source(new
> SearchSourceBuilder().query(QueryBuilders.wrapperQuery("my:query"))
> .size(50).from(0));
> {code}
> I don't know what was the developer's intention for having such a condition
> which removes these parameters from the query.
> Thank you very much in advance if anybody can have a look and verify if this
> is a valid concern.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (CAMEL-12034) camel-elasticsearch5 - Search Operation: If Map or String is used in Message Body, "size" and "from" parameters are always ignored
[
https://issues.apache.org/jira/browse/CAMEL-12034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-12034:
---
Assignee: Claus Ibsen (was: Andrea Cosentino)
> camel-elasticsearch5 - Search Operation: If Map or String is used in Message
> Body, "size" and "from" parameters are always ignored
> --
>
> Key: CAMEL-12034
> URL: https://issues.apache.org/jira/browse/CAMEL-12034
> Project: Camel
> Issue Type: Bug
> Components: camel-elasticsearch5
>Affects Versions: 2.20.1
>Reporter: Radoslav Cincala
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.20.3, 2.21.0
>
>
> Hi,
> I am using camel-elasticsearch5 component of Camel 2.20.1.
> I have found and issue. The description follows.
> *If you use Map or String in message body for SEARCH operation, "size" and
> "from" parameters are always ignored hence you always get just default 10
> results.*
> For example - if your map contains query like this:
> (in terms of simplicity - following is String representation of the map):
> {code}
> {size=50, query={query_string={query=status:ACTIVE}}, from=0}
> {code}
> Issue I suspect is present in class:
> _org.apache.camel.component.elasticsearch5.converter.ElasticsearchActionRequestConverter_
> and its method
> _public static SearchRequest toSearchRequest(Object queryObject, Exchange
> exchange)_
> {code}
> // line 191...
> if (queryObject instanceof Map) {
> Map mapQuery = (Map)queryObject;
> // Remove 'query' prefix from the query object for backward
> compatibility
> if
> (mapQuery.containsKey(ElasticsearchConstants.ES_QUERY_DSL_PREFIX)) {
> mapQuery = (Map Object>)mapQuery.get(ElasticsearchConstants.ES_QUERY_DSL_PREFIX);
> }
> try {
> XContentBuilder contentBuilder =
> XContentFactory.contentBuilder(XContentType.JSON);
> queryText = contentBuilder.map(mapQuery).string();
> } catch (IOException e) {
> LOG.error(e.getMessage());
> }
> }
> // queryText then used on line 220...
> searchSourceBuilder.query(QueryBuilders.wrapperQuery(queryText));
> searchRequest.source(searchSourceBuilder);
> return searchRequest;
> {code}
> Inner if condition basically extracts only query part from the map
> {code}
> query={query_string={query=status:ACTIVE}
> {code}
> and *"size" and "from" get lost from the query*
> {code}
> // line 194...
> if (mapQuery.containsKey(ElasticsearchConstants.ES_QUERY_DSL_PREFIX)) {
> mapQuery = (Map Object>)mapQuery.get(ElasticsearchConstants.ES_QUERY_DSL_PREFIX);
> // ...where ElasticsearchConstants.ES_QUERY_DSL_PREFIX = "query"
> }
> {code}
> Same issue is with usage of the String in the message body:
> {code}
> // line 203
> } else if (queryObject instanceof String) {
> queryText = (String)queryObject;
> ObjectMapper mapper = new ObjectMapper();
> try {
> JsonNode jsonTextObject = mapper.readValue(queryText,
> JsonNode.class);
> JsonNode parentJsonNode =
> jsonTextObject.get(ElasticsearchConstants.ES_QUERY_DSL_PREFIX);
> if (parentJsonNode != null) {
> queryText = parentJsonNode.toString();
> }
> } catch (IOException e) {
> LOG.error(e.getMessage());
> }
> }
> {code}
> Only workaround for this is to use *SearchRequest* object in a message body
> where you can explicitly set "size" and "from" on SearchSourceBuilder object.
> For example:
> {code}
> SearchRequest searchRequest = new SearchRequest("my_index")
> .types("my_type")
> .source(new
> SearchSourceBuilder().query(QueryBuilders.wrapperQuery("my:query"))
> .size(50).from(0));
> {code}
> I don't know what was the developer's intention for having such a condition
> which removes these parameters from the query.
> Thank you very much in advance if anybody can have a look and verify if this
> is a valid concern.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (CAMEL-12221) Let's create a camel-fhir component
[ https://issues.apache.org/jira/browse/CAMEL-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-12221. - Resolution: Fixed Assignee: John Poth There is now a camel-fhir karaf feature (needed to turn on dynamic-import on some fhire wrapped jars) - its classloading is not osgi friendly by using Class.forName and such > Let's create a camel-fhir component > --- > > Key: CAMEL-12221 > URL: https://issues.apache.org/jira/browse/CAMEL-12221 > Project: Camel > Issue Type: New Feature >Reporter: John Poth >Assignee: John Poth >Priority: Major > Fix For: 2.21.0 > > > Let's create a camel-fhir component based on [HAPI-FHIR|http://hapifhir.io] > I can take care of the PR. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-11162) camel-rest - Should we add content-type check for server side
[ https://issues.apache.org/jira/browse/CAMEL-11162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11162: Fix Version/s: (was: 2.21.0) 2.22.0 > camel-rest - Should we add content-type check for server side > - > > Key: CAMEL-11162 > URL: https://issues.apache.org/jira/browse/CAMEL-11162 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 2.22.0 > > > For example setting up a rest-dsl which consumes application/json and then a > client calls it with text/plain or application/xml, should we then automatic > let rest consumer detect this and return a HTTP status 415 (unsuported media > type) > Not all the HTTP server components does this today, eg jetty etc. But when > using restlet which is more natual REST it would do so. > We could then add an option to turn this on|off. > The check is only if the media-type is within the list that may have been > specified on consumes in the rest-dsl. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12221) Let's create a camel-fhir component
[ https://issues.apache.org/jira/browse/CAMEL-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387583#comment-16387583 ] Andrea Cosentino commented on CAMEL-12221: -- I believe for 2.21.0 we have no solution, we need to use Wrap. Lets see if they'll accept the PR and eventually we may think to create a SMX bundle for this, but I guess they will accept it > Let's create a camel-fhir component > --- > > Key: CAMEL-12221 > URL: https://issues.apache.org/jira/browse/CAMEL-12221 > Project: Camel > Issue Type: New Feature >Reporter: John Poth >Priority: Major > Fix For: 2.21.0 > > > Let's create a camel-fhir component based on [HAPI-FHIR|http://hapifhir.io] > I can take care of the PR. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-12221) Let's create a camel-fhir component
[ https://issues.apache.org/jira/browse/CAMEL-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387564#comment-16387564 ] John Poth edited comment on CAMEL-12221 at 3/6/18 10:15 AM: I sent a [PR|https://github.com/jamesagnew/hapi-fhir/pull/871] to HAPI-FHIR to have OSGI support natively. We could probably achieve the same thing using the wrap protocol if need be. Or SMX as you mentioned. was (Author: jpoth): I sent a [PR|https://github.com/jamesagnew/hapi-fhir/pull/871] to HAPI-FHIR to have OSGI support natively. We could probably achieve the same thing using the wrap protocol if need be. > Let's create a camel-fhir component > --- > > Key: CAMEL-12221 > URL: https://issues.apache.org/jira/browse/CAMEL-12221 > Project: Camel > Issue Type: New Feature >Reporter: John Poth >Priority: Major > Fix For: 2.21.0 > > > Let's create a camel-fhir component based on [HAPI-FHIR|http://hapifhir.io] > I can take care of the PR. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12221) Let's create a camel-fhir component
[ https://issues.apache.org/jira/browse/CAMEL-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387564#comment-16387564 ] John Poth commented on CAMEL-12221: --- I sent a [PR|https://github.com/jamesagnew/hapi-fhir/pull/871] to HAPI-FHIR to have OSGI support natively. We could probably achieve the same thing using the wrap protocol if need be. > Let's create a camel-fhir component > --- > > Key: CAMEL-12221 > URL: https://issues.apache.org/jira/browse/CAMEL-12221 > Project: Camel > Issue Type: New Feature >Reporter: John Poth >Priority: Major > Fix For: 2.21.0 > > > Let's create a camel-fhir component based on [HAPI-FHIR|http://hapifhir.io] > I can take care of the PR. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (CAMEL-11780) camel-amqp - SSL Transport configuration
[ https://issues.apache.org/jira/browse/CAMEL-11780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387552#comment-16387552 ] Claus Ibsen edited comment on CAMEL-11780 at 3/6/18 10:02 AM: -- Can you try again with newest release as we have upgraded qpid-jms-client to be 0.30 in Camel 2.21. Then it may support amqps scheme and configuring it via its url syntax is possible. was (Author: davsclaus): Can you try again with newest release as we have upgraded qpid-jms-client to be 0.30 in Camel 2.21 > camel-amqp - SSL Transport configuration > > > Key: CAMEL-11780 > URL: https://issues.apache.org/jira/browse/CAMEL-11780 > Project: Camel > Issue Type: Improvement > Components: camel-amqp >Affects Versions: 2.19.2 >Reporter: Cyril EDME >Assignee: Viral Gohel >Priority: Major > Fix For: 2.22.0 > > > Hi, > i'm using camel and specially the amqp component to consume a topic. > Everything is working well but I'm confused regarding the SSL configuration. > It's not clear in the documentation, I don't want to use the default JVM > certificate storage so I tried to configure the connection factory with the > [qpid > documentation|https://qpid.apache.org/releases/qpid-jms-0.24.0/docs/index.html#ssl-transport-configuration-options] > but the qpid-jms-client version used by amqp component (0.11.1) doesn't > handle the amqps schema URI. > There is another way to configure the SSL transport like the key store > location and password without a qpid upgrade ? > Thanks ! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-11780) camel-amqp - SSL Transport configuration
[ https://issues.apache.org/jira/browse/CAMEL-11780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11780: Fix Version/s: (was: 2.21.0) 2.22.0 > camel-amqp - SSL Transport configuration > > > Key: CAMEL-11780 > URL: https://issues.apache.org/jira/browse/CAMEL-11780 > Project: Camel > Issue Type: Improvement > Components: camel-amqp >Affects Versions: 2.19.2 >Reporter: Cyril EDME >Assignee: Viral Gohel >Priority: Major > Fix For: 2.22.0 > > > Hi, > i'm using camel and specially the amqp component to consume a topic. > Everything is working well but I'm confused regarding the SSL configuration. > It's not clear in the documentation, I don't want to use the default JVM > certificate storage so I tried to configure the connection factory with the > [qpid > documentation|https://qpid.apache.org/releases/qpid-jms-0.24.0/docs/index.html#ssl-transport-configuration-options] > but the qpid-jms-client version used by amqp component (0.11.1) doesn't > handle the amqps schema URI. > There is another way to configure the SSL transport like the key store > location and password without a qpid upgrade ? > Thanks ! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-11780) camel-amqp - SSL Transport configuration
[ https://issues.apache.org/jira/browse/CAMEL-11780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387552#comment-16387552 ] Claus Ibsen commented on CAMEL-11780: - Can you try again with newest release as we have upgraded qpid-jms-client to be 0.30 in Camel 2.21 > camel-amqp - SSL Transport configuration > > > Key: CAMEL-11780 > URL: https://issues.apache.org/jira/browse/CAMEL-11780 > Project: Camel > Issue Type: Improvement > Components: camel-amqp >Affects Versions: 2.19.2 >Reporter: Cyril EDME >Assignee: Viral Gohel >Priority: Major > Fix For: 2.21.0 > > > Hi, > i'm using camel and specially the amqp component to consume a topic. > Everything is working well but I'm confused regarding the SSL configuration. > It's not clear in the documentation, I don't want to use the default JVM > certificate storage so I tried to configure the connection factory with the > [qpid > documentation|https://qpid.apache.org/releases/qpid-jms-0.24.0/docs/index.html#ssl-transport-configuration-options] > but the qpid-jms-client version used by amqp component (0.11.1) doesn't > handle the amqps schema URI. > There is another way to configure the SSL transport like the key store > location and password without a qpid upgrade ? > Thanks ! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12115) Camel-Consul: Upgrade to 1.0.0 consul client
[ https://issues.apache.org/jira/browse/CAMEL-12115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12115: Fix Version/s: (was: 2.21.0) 2.22.0 > Camel-Consul: Upgrade to 1.0.0 consul client > > > Key: CAMEL-12115 > URL: https://issues.apache.org/jira/browse/CAMEL-12115 > Project: Camel > Issue Type: Task > Components: camel-consul >Reporter: Andrea Cosentino >Priority: Major > Fix For: 2.22.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-11823) [example] cdi-cassandrasql - nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 'Connection refused'
[
https://issues.apache.org/jira/browse/CAMEL-11823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-11823:
Priority: Minor (was: Major)
> [example] cdi-cassandrasql - nodetool: Failed to connect to '127.0.0.1:7199'
> - ConnectException: 'Connection refused'
> -
>
> Key: CAMEL-11823
> URL: https://issues.apache.org/jira/browse/CAMEL-11823
> Project: Camel
> Issue Type: Sub-task
> Components: examples
>Affects Versions: 2.20.0
>Reporter: Tomohisa Igarashi
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.21.0
>
>
> something wrong with docker image
> {code}
> $ docker exec -ti master_node /opt/cassandra/bin/nodetool status
> nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException:
> 'Connection refused'.
> {code}
> {code}
> $ docker logs master_node
> *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
> *** Running /etc/rc.local...
> *** Booting runit daemon...
> *** Runit started as PID 8
> I'm starting cassandra
> tail: unrecognized file system type 0x794c7630 for ‘/var/log/syslog’. please
> report this to bug-coreut...@gnu.org. reverting to polling
> Filling in the blanks inside cassandra.yaml
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:28 Killed bin/cassandra -Rf
> I'm starting cassandra
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:93 Killed bin/cassandra -Rf
> I'm starting cassandra
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31: 159 Killed bin/cassandra -Rf
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CAMEL-11994) Add call options to the camel-grpc component
[ https://issues.apache.org/jira/browse/CAMEL-11994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11994: Fix Version/s: (was: 2.21.0) 2.22.0 > Add call options to the camel-grpc component > > > Key: CAMEL-11994 > URL: https://issues.apache.org/jira/browse/CAMEL-11994 > Project: Camel > Issue Type: New Feature > Components: camel-grpc >Affects Versions: 2.20.0 >Reporter: Dmitry Volodin >Assignee: Dmitry Volodin >Priority: Major > Fix For: 2.22.0 > > > Add advanced call options related to the one operation and not overriding > channel option: > - deadline > - compression > - etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12221) Let's create a camel-fhir component
[ https://issues.apache.org/jira/browse/CAMEL-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387546#comment-16387546 ] Claus Ibsen commented on CAMEL-12221: - John, Andrea. Are we in need for SMX bundles for this or something for getting camel-fhir into Karaf feature file? Currently its not there. > Let's create a camel-fhir component > --- > > Key: CAMEL-12221 > URL: https://issues.apache.org/jira/browse/CAMEL-12221 > Project: Camel > Issue Type: New Feature >Reporter: John Poth >Priority: Major > Fix For: 2.21.0 > > > Let's create a camel-fhir component based on [HAPI-FHIR|http://hapifhir.io] > I can take care of the PR. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12323) camel-spark-rest - Avoid singleton spark instance
Claus Ibsen created CAMEL-12323: --- Summary: camel-spark-rest - Avoid singleton spark instance Key: CAMEL-12323 URL: https://issues.apache.org/jira/browse/CAMEL-12323 Project: Camel Issue Type: Improvement Reporter: Claus Ibsen Instead of using singleton Spark we can use Service.ignite() that can create an instance. We can then better control that lifecycle. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
