[jira] [Commented] (CAMEL-12960) Allow consumer partition assignment
[ https://issues.apache.org/jira/browse/CAMEL-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700035#comment-16700035 ] Andrea Cosentino commented on CAMEL-12960: -- No problem. Removed > Allow consumer partition assignment > --- > > Key: CAMEL-12960 > URL: https://issues.apache.org/jira/browse/CAMEL-12960 > Project: Camel > Issue Type: New Feature > Components: camel-kafka >Reporter: J Jenkins >Priority: Minor > Fix For: Future > > > The current implementation of camel-kafka is coded to use consumer.subscribe. > This tends to be the default for most Kafka consumer use-cases, however, > there are times when you may not want some of the features that come with > subscription (such as automatic re-balancing). > Kafka allows for more control in this situations by using the consumer.assign > api. > Would be great if we can extend camel-kafka to pass in some additional flags > and required fields for using assign instead of subscribe. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (CAMEL-12960) Allow consumer partition assignment
[ https://issues.apache.org/jira/browse/CAMEL-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-12960: Assignee: (was: Andrea Cosentino) > Allow consumer partition assignment > --- > > Key: CAMEL-12960 > URL: https://issues.apache.org/jira/browse/CAMEL-12960 > Project: Camel > Issue Type: New Feature > Components: camel-kafka >Reporter: J Jenkins >Priority: Minor > Fix For: Future > > > The current implementation of camel-kafka is coded to use consumer.subscribe. > This tends to be the default for most Kafka consumer use-cases, however, > there are times when you may not want some of the features that come with > subscription (such as automatic re-balancing). > Kafka allows for more control in this situations by using the consumer.assign > api. > Would be great if we can extend camel-kafka to pass in some additional flags > and required fields for using assign instead of subscribe. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12960) Allow consumer partition assignment
[ https://issues.apache.org/jira/browse/CAMEL-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16700030#comment-16700030 ] J Jenkins commented on CAMEL-12960: --- [~ancosen] apologies, I clone this issue and it won't let me remove you from the assignee... > Allow consumer partition assignment > --- > > Key: CAMEL-12960 > URL: https://issues.apache.org/jira/browse/CAMEL-12960 > Project: Camel > Issue Type: New Feature > Components: camel-kafka >Reporter: J Jenkins >Assignee: Andrea Cosentino >Priority: Minor > Fix For: Future > > > The current implementation of camel-kafka is coded to use consumer.subscribe. > This tends to be the default for most Kafka consumer use-cases, however, > there are times when you may not want some of the features that come with > subscription (such as automatic re-balancing). > Kafka allows for more control in this situations by using the consumer.assign > api. > Would be great if we can extend camel-kafka to pass in some additional flags > and required fields for using assign instead of subscribe. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12960) Allow consumer partition assignment
[ https://issues.apache.org/jira/browse/CAMEL-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J Jenkins updated CAMEL-12960: -- Description: The current implementation of camel-kafka is coded to use consumer.subscribe. This tends to be the default for most Kafka consumer use-cases, however, there are times when you may not want some of the features that come with subscription (such as automatic re-balancing). Kafka allows for more control in this situations by using the consumer.assign api. Would be great if we can extend camel-kafka to pass in some additional flags and required fields for using assign instead of subscribe. > Allow consumer partition assignment > --- > > Key: CAMEL-12960 > URL: https://issues.apache.org/jira/browse/CAMEL-12960 > Project: Camel > Issue Type: New Feature > Components: camel-kafka >Reporter: J Jenkins >Assignee: Andrea Cosentino >Priority: Minor > Fix For: Future > > > The current implementation of camel-kafka is coded to use consumer.subscribe. > This tends to be the default for most Kafka consumer use-cases, however, > there are times when you may not want some of the features that come with > subscription (such as automatic re-balancing). > Kafka allows for more control in this situations by using the consumer.assign > api. > Would be great if we can extend camel-kafka to pass in some additional flags > and required fields for using assign instead of subscribe. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12960) Allow consumer partition assignment
J Jenkins created CAMEL-12960: - Summary: Allow consumer partition assignment Key: CAMEL-12960 URL: https://issues.apache.org/jira/browse/CAMEL-12960 Project: Camel Issue Type: New Feature Components: camel-kafka Reporter: J Jenkins Assignee: Andrea Cosentino Fix For: Future -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12812) Salesforce component tries to reconnect when unsubscribing from topic in case of "403::Handshake denied" error
[
https://issues.apache.org/jira/browse/CAMEL-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Tyurin updated CAMEL-12812:
--
Affects Version/s: 2.21.2
> Salesforce component tries to reconnect when unsubscribing from topic in case
> of "403::Handshake denied" error
> --
>
> Key: CAMEL-12812
> URL: https://issues.apache.org/jira/browse/CAMEL-12812
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 2.21.2, 2.22.1
>Reporter: Andrey Tyurin
>Priority: Major
>
> Hi.
> We've faced some strange behavior when salesforce component is shutting down.
> When SF component is unsubscribing from channel and it gets some error, e.g.
> "403::Handshake denied" it tries then reconnect to SF. But why? if it is
> shutting down.
> This causes long process of logout from SF: about 4 minutes.
> We do not have specific scenario, but only exceptions for this case.
>
> 2018-08-31 05:40:51.454 [SalesforceHttpClient@b9f06a7-293] INFO
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper -
> Restarting on unexpected disconnect from Salesforce... 2018-08-31
> 05:40:51.454 [SalesforceHttpClient@b9f06a7-293] DEBUG
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper -
> Waiting to disconnect... 2018-08-31 05:40:51.455
> [SalesforceHttpClient@b9f06a7-288] DEBUG
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper -
> [CHANNEL:META_CONNECT]: \{clientId=kteskpq4fgf192z1zpdm0ml1ebe,
> advice={reconnect=none, interval=0}, channel=/meta/connect, id=29,
> error=401::Authentication invalid, successful=false} 2018-08-31 05:40:51.455
> [SalesforceHttpClient@b9f06a7-288] WARN
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper -
> Connect failure: \{clientId=kteskpq4fgf192z1zpdm0ml1ebe,
> advice={reconnect=none, interval=0}, channel=/meta/connect, id=29,
> error=401::Authentication invalid, successful=false} 2018-08-31 05:40:56.516
> [SalesforceHttpClient@b9f06a7-292] INFO
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper -
> Cleaning session (logout) from SalesforceSession before restarting client
> 2018-08-31 05:41:39.156 [Camel (camel-1) thread #105 - ShutdownTask] INFO
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper -
> Unsubscribing from channel /topic/myCompanyExtRoutPsr... ... 2018-08-31
> 05:42:19.156 [Camel (camel-1) thread #105 - ShutdownTask] WARN
> org.apache.camel.impl.DefaultShutdownStrategy - Error occurred while shutting
> down route:
> Consumer[salesforce-102-STREAMING://myCompanyExtRoutPsr?sObjectClass=com.myCompany.sfgateway.api.dto.PendingServiceRouting=SELECT+Id%2C+QueueId%2C+WorkItemId%2C+IsPushed%2C+ServiceChannelId%2C+LastDeclinedAgentSession%2C+CreatedDate%2C+IsDeleted%2C+IsPushAttempted%2C+IsTransfer+from+PendingServiceRouting+WHERE+RoutingModel+%3D+%27ExternalRouting%27=true].
> This exception will be ignored. org.apache.camel.CamelException: Timeout
> error unsubscribing from topic myCompanyExtRoutPsr after 40 seconds at
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper.unsubscribe(SubscriptionHelper.java:519)
> ~[camel-salesforce-2.21.2.jar!/:2.21.2] at
> org.apache.camel.component.salesforce.SalesforceConsumer.doStop(SalesforceConsumer.java:139)
> ~[camel-salesforce-2.21.2.jar!/:2.21.2] at
> org.apache.camel.support.ServiceSupport.stop(ServiceSupport.java:102)
> ~[camel-core-2.21.2.jar!/:2.21.2] at
> org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:142)
> ~[camel-core-2.21.2.jar!/:2.21.2] at
> org.apache.camel.impl.DefaultShutdownStrategy.shutdownNow(DefaultShutdownStrategy.java:381)
> [camel-core-2.21.2.jar!/:2.21.2] at
> org.apache.camel.impl.DefaultShutdownStrategy$ShutdownTask.run(DefaultShutdownStrategy.java:577)
> [camel-core-2.21.2.jar!/:2.21.2] at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [?:1.8.0_102] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [?:1.8.0_102] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [?:1.8.0_102] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [?:1.8.0_102] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102]
> 2018-08-31 05:42:19.170 [Camel (camel-1) thread #105 - ShutdownTask] INFO
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper -
> Unsubscribing from channel /topic/myCompanyExtRoute... 2018-08-31
> 05:42:46.458 [SalesforceHttpClient@b9f06a7-293] ERROR
> org.apache.camel.component.salesforce.internal.streaming.SubscriptionHelper -
> Error restarting: Error during
[jira] [Commented] (CAMEL-12605) Enhance the AS2 Component to send and receive encrypted AS2 messages
[ https://issues.apache.org/jira/browse/CAMEL-12605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16699582#comment-16699582 ] ASF GitHub Bot commented on CAMEL-12605: punkhorn opened a new pull request #2639: [CAMEL-12605] Added support for compression URL: https://github.com/apache/camel/pull/2639 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Enhance the AS2 Component to send and receive encrypted AS2 messages > > > Key: CAMEL-12605 > URL: https://issues.apache.org/jira/browse/CAMEL-12605 > Project: Camel > Issue Type: Improvement >Affects Versions: 2.23.0 >Reporter: William Collins >Assignee: William Collins >Priority: Major > > Enhance the AS2 Component to support encrypted AS2 messages per RFC4130 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12958) Wrong camel context bound in service registry of jbpm/Kie Server
[ https://issues.apache.org/jira/browse/CAMEL-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698871#comment-16698871 ] ASF GitHub Bot commented on CAMEL-12958: mswiderski opened a new pull request #2637: CAMEL-12958 - Wrong camel context bound in service registry of jbpm/K… URL: https://github.com/apache/camel/pull/2637 …ie Server This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Wrong camel context bound in service registry of jbpm/Kie Server > > > Key: CAMEL-12958 > URL: https://issues.apache.org/jira/browse/CAMEL-12958 > Project: Camel > Issue Type: Bug > Components: camel-jbpm >Affects Versions: 2.23.0 >Reporter: Maciej Swiderski >Assignee: Maciej Swiderski >Priority: Major > > Wrong camel context is set in the ServiceRegistry of jBPM when creating kie > container specific camel context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (CAMEL-12959) Container specific context is not registered in jBPM Camel KIE-Server Extension
[ https://issues.apache.org/jira/browse/CAMEL-12959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maciej Swiderski closed CAMEL-12959. Resolution: Duplicate > Container specific context is not registered in jBPM Camel KIE-Server > Extension > --- > > Key: CAMEL-12959 > URL: https://issues.apache.org/jira/browse/CAMEL-12959 > Project: Camel > Issue Type: Bug > Components: camel-jbpm >Affects Versions: 2.23.0 >Reporter: Duncan Doyle >Assignee: Maciej Swiderski >Priority: Major > > See this line > [https://github.com/apache/camel/blob/master/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java#L120] > Instead of registering the container specific "context" DefaultCamelContext, > the "this.camel" DefaultCamelContext (the global CamelContext of the > KIE-Server extension) is registered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12959) Container specific context is not registered in jBPM Camel KIE-Server Extension
Duncan Doyle created CAMEL-12959: Summary: Container specific context is not registered in jBPM Camel KIE-Server Extension Key: CAMEL-12959 URL: https://issues.apache.org/jira/browse/CAMEL-12959 Project: Camel Issue Type: Bug Components: camel-jbpm Affects Versions: 2.23.0 Reporter: Duncan Doyle Assignee: Maciej Swiderski See this line [https://github.com/apache/camel/blob/master/components/camel-jbpm/src/main/java/org/apache/camel/component/jbpm/server/CamelKieServerExtension.java#L120] Instead of registering the container specific "context" DefaultCamelContext, the "this.camel" DefaultCamelContext (the global CamelContext of the KIE-Server extension) is registered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12958) Wrong camel context bound in service registry of jbpm/Kie Server
Maciej Swiderski created CAMEL-12958: Summary: Wrong camel context bound in service registry of jbpm/Kie Server Key: CAMEL-12958 URL: https://issues.apache.org/jira/browse/CAMEL-12958 Project: Camel Issue Type: Bug Components: camel-jbpm Affects Versions: 2.23.0 Reporter: Maciej Swiderski Assignee: Maciej Swiderski Wrong camel context is set in the ServiceRegistry of jBPM when creating kie container specific camel context. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12957) Swagger/OpenAPI feature should not involve the Camel route
Jens Kleine-Herzbruch created CAMEL-12957: - Summary: Swagger/OpenAPI feature should not involve the Camel route Key: CAMEL-12957 URL: https://issues.apache.org/jira/browse/CAMEL-12957 Project: Camel Issue Type: Improvement Components: camel-cxfrs Affects Versions: 2.22.2 Reporter: Jens Kleine-Herzbruch Currently, when adding Swagger2Feature or OpenApiFeature to a CXFRS endpoint, the calls to the API descriptions go through the Camel route, ie. one has to implement an additional Camel route in order to make those features work. Using runAsFilter=false a call to http://localhost:8080/services/myCamelService/openapi.json results in a call of the Camel route with an operation "getOpenApi" http://localhost:8080/services/myCamelServive/api-docs?url=openapi.json results in call of the Camel route with an operation "getResource" Using runAsFilter=true the situation improves marginally: http://localhost:8080/services/myCamelService/openapi.json still results in a call of the Camel route with an operation "getOpenApi" http://localhost:8080/services/myCamelServive/api-docs?url=openapi.json at least now shows the Swagger UI page frame but still fails to load the actual service description since it again calls the Camel route with the "getOpenApi" operation. Supposedly that means the filter correctly intercepts the getResource call but not the getOpenApi call. It would be great if this worked out of the box. A custom implementation would still be possible by not running as a filter. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12956) Spring Boot Auto-Configuration via application.properties does not work
[
https://issues.apache.org/jira/browse/CAMEL-12956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Epping updated CAMEL-12956:
---
Description:
I am trying to configure camel with spring boot to use active MQ. But the jms
connection factory (activemq) gets not picked up automatically during auto
configuration. Thus, I tried to configure it via application.properties
{code:java}
camel.component.jms.connection-factory=org.apache.activemq.ActiveMQConnectionFactory{code}
But then I get an error on startup stating, that the expected datatype is
{code:java}
javax.jms.ConnectionFactory{code}
and not
{code:java}
String{code}
The only solutions I have found is not using autoconfiguration and configuring
*JmsComponent* by hand or using a *ComponentCustomizer* programatically. This
seems to be a Bug, as other component auto configurations expect a String as
connectionFactory property.
was:I am trying to configure camel with spring boot to use active MQ. But the
jms connection factory (activemq) gets not picked up automatically during auto
configuration. Thus, I tried to configure it via application.properties
(`camel.component.jms.connection-factory=org.apache.activemq.ActiveMQConnectionFactory`).
But then I get an error on startup stating, that the expected datatype is
`javax.jms.ConnectionFactory` and not `String`. The only solutions I have found
is not using autoconfiguration and configuring JmsComponent by hand or using a
ComponentCustomizer programatically. This seems to be a Bug, as other component
auto configurations expect a String as connectionFactory property.
> Spring Boot Auto-Configuration via application.properties does not work
> ---
>
> Key: CAMEL-12956
> URL: https://issues.apache.org/jira/browse/CAMEL-12956
> Project: Camel
> Issue Type: Bug
> Components: camel-activemq, camel-jms, camel-spring-boot,
> camel-spring-boot-starters
>Affects Versions: 2.22.2
>Reporter: Stephan Epping
>Priority: Major
>
> I am trying to configure camel with spring boot to use active MQ. But the jms
> connection factory (activemq) gets not picked up automatically during auto
> configuration. Thus, I tried to configure it via application.properties
> {code:java}
> camel.component.jms.connection-factory=org.apache.activemq.ActiveMQConnectionFactory{code}
> But then I get an error on startup stating, that the expected datatype is
> {code:java}
> javax.jms.ConnectionFactory{code}
> and not
> {code:java}
> String{code}
> The only solutions I have found is not using autoconfiguration and
> configuring *JmsComponent* by hand or using a *ComponentCustomizer*
> programatically. This seems to be a Bug, as other component auto
> configurations expect a String as connectionFactory property.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12955) Create a Camel-ChatScript component
[ https://issues.apache.org/jira/browse/CAMEL-12955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698625#comment-16698625 ] Varun Krish commented on CAMEL-12955: - Will be requesting a PR for this change. > Create a Camel-ChatScript component > --- > > Key: CAMEL-12955 > URL: https://issues.apache.org/jira/browse/CAMEL-12955 > Project: Camel > Issue Type: New Feature >Reporter: Varun Krish >Assignee: Andrea Cosentino >Priority: Major > Fix For: Future > > > Create new component to interact with ChatScript BOTs. > Chat Script: [https://github.com/bwilcox-1234/ChatScript] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12956) Spring Boot Auto-Configuration via application.properties does not work
Stephan Epping created CAMEL-12956: -- Summary: Spring Boot Auto-Configuration via application.properties does not work Key: CAMEL-12956 URL: https://issues.apache.org/jira/browse/CAMEL-12956 Project: Camel Issue Type: Bug Components: camel-activemq, camel-jms, camel-spring-boot, camel-spring-boot-starters Affects Versions: 2.22.2 Reporter: Stephan Epping I am trying to configure camel with spring boot to use active MQ. But the jms connection factory (activemq) gets not picked up automatically during auto configuration. Thus, I tried to configure it via application.properties (`camel.component.jms.connection-factory=org.apache.activemq.ActiveMQConnectionFactory`). But then I get an error on startup stating, that the expected datatype is `javax.jms.ConnectionFactory` and not `String`. The only solutions I have found is not using autoconfiguration and configuring JmsComponent by hand or using a ComponentCustomizer programatically. This seems to be a Bug, as other component auto configurations expect a String as connectionFactory property. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-12955) Create a Camel-ChatScript component
[ https://issues.apache.org/jira/browse/CAMEL-12955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Krish updated CAMEL-12955: Description: Create new component to interact with ChatScript BOTs. Chat Script: [https://github.com/bwilcox-1234/ChatScript] was: [https://pulsar.incubator.apache.org/docs/latest/clients/Java/] https://pulsar.incubator.apache.org/ > Create a Camel-ChatScript component > --- > > Key: CAMEL-12955 > URL: https://issues.apache.org/jira/browse/CAMEL-12955 > Project: Camel > Issue Type: New Feature >Reporter: Varun Krish >Assignee: Andrea Cosentino >Priority: Major > Fix For: Future > > > Create new component to interact with ChatScript BOTs. > Chat Script: [https://github.com/bwilcox-1234/ChatScript] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-12955) Create a Camel-ChatScript component
Varun Krish created CAMEL-12955: --- Summary: Create a Camel-ChatScript component Key: CAMEL-12955 URL: https://issues.apache.org/jira/browse/CAMEL-12955 Project: Camel Issue Type: New Feature Reporter: Varun Krish Assignee: Andrea Cosentino Fix For: Future [https://pulsar.incubator.apache.org/docs/latest/clients/Java/] https://pulsar.incubator.apache.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
