You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/10/20 21:18:28 UTC
[GitHub] [camel-quarkus] weimeilin79 opened a new issue #1935: Properties Bean configure not working with AMQP and Infinispan
weimeilin79 opened a new issue #1935:
URL: https://github.com/apache/camel-quarkus/issues/1935
I had a couple of components in Camel K that uses properties to set the value for the components.
After the runtime switched to Quarkus, some of them stopped working.
AMQP
```
camel.component.amqp.configuration.connection-factory.remoteURI=amqp://messaging-yez4fz7xkj.workshop-operators.svc:5672?amqp.saslMechanisms=PLAIN
camel.component.amqp.username=user
camel.component.amqp.password=enmasse
```
but now, it only takes in quarkus setting
```
quarkus.qpid-jms.url=amqp://<CHANGE_ME>:5672
quarkus.qpid-jms.username=user
quarkus.qpid-jms.password=enmasse
```
Infinispan
```
kafka.properties: |2+
consumer.group=premium
camel.component.kafka.brokers=<CHANGE_ME>:9092
camel.component.infinispan.configuration.hosts=example-infinispan.user1.svc:11222
camel.component.infinispan.configuration.configurationUri=client.properties
client.properties: |2+
infinispan.client.hotrod.use_auth=true
infinispan.client.hotrod.auth_username=developer
infinispan.client.hotrod.auth_password=password
infinispan.client.hotrod.auth_realm=default
infinispan.client.hotrod.sasl_mechanism=SCRAM-SHA-512
infinispan.client.hotrod.marshaller=org.infinispan.commons.marshall.JavaSerializationMarshaller
infinispan.client.hotrod.java_serial_whitelist=java.util.ArrayList,java.util.LinkedHashMap,java.util.HashMap
infinispan.client.hotrod.async_executor_factory = org.infinispan.client.hotrod.impl.async.DefaultAsyncExecutorFactory
infinispan.client.hotrod.default_executor_factory.pool_size = 1
infinispan.client.hotrod.hash_function_impl.2 = org.infinispan.client.hotrod.impl.consistenthash.ConsistentHashV2
infinispan.client.hotrod.tcp_no_delay = true
infinispan.client.hotrod.tcp_keep_alive = false
infinispan.client.hotrod.request_balancing_strategy = org.infinispan.client.hotrod.impl.transport.tcp.RoundRobinBalancingStrategy
infinispan.client.hotrod.key_size_estimate = 64
infinispan.client.hotrod.value_size_estimate = 512
infinispan.client.hotrod.force_return_values = false
```
But now it only takes in
```
quarkus.infinispan-client.server-list=example-infinispan.user1.svc:11222
quarkus.infinispan-client.use-auth=true
quarkus.infinispan-client.auth-username=developer
quarkus.infinispan-client.auth-password=password
quarkus.infinispan-client.auth-realm=default
quarkus.infinispan-client.sasl-mechanism=SCRAM-SHA-512
``
and was not able to take in the hotrod-client properties anymore with many missing configs.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] lburgazzoli edited a comment on issue #1935: Properties Bean configure not working with AMQP and Infinispan
Posted by GitBox <gi...@apache.org>.
lburgazzoli edited a comment on issue #1935:
URL: https://github.com/apache/camel-quarkus/issues/1935#issuecomment-713379722
No camel-quarkus-main is there by default in camel-k.
Additional note: only the components for which we have an extension that use beans from build items seems to be affected. As example here, the kafka set-up works using camel's conventions whereas the amqp/infinispan do not seem to work.
@weimeilin79 am I right ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] lburgazzoli commented on issue #1935: Properties Bean configure not working with AMQP and Infinispan
Posted by GitBox <gi...@apache.org>.
lburgazzoli commented on issue #1935:
URL: https://github.com/apache/camel-quarkus/issues/1935#issuecomment-713379722
No camel-quarkus-main is there by default in camel-k.
Additional note: only the components for which we have an extension that uses beans from build items seems to be affected, as example here, the kafka setup works using camel's conventions whereas the jms one does not.
@weimeilin79 am I right ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] weimeilin79 commented on issue #1935: Properties Bean configure not working with AMQP and Infinispan
Posted by GitBox <gi...@apache.org>.
weimeilin79 commented on issue #1935:
URL: https://github.com/apache/camel-quarkus/issues/1935#issuecomment-713180459
I was using Camel K, which by default using the Quarkus runtime. Should we include this dependency by default?
Currently it only has this:
- 'camel-quarkus:infinispan'
- 'camel-quarkus:kafka'
- 'camel-quarkus:timer'
- 'camel:bean'
- 'camel:infinispan'
- 'camel:jackson'
- 'mvn:io.netty:netty-codec:4.1.49.Final'
- 'mvn:org.apache.camel.k/camel-k-quarkus-loader-java'
- 'mvn:org.apache.camel.k/camel-k-runtime-quarkus'
And it was not very clear on the individual documents that some configuration are only supported when camel-quarkus-main is added and some don't like *Kafka*.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] ppalaga commented on issue #1935: Properties Bean configure not working with AMQP and Infinispan
Posted by GitBox <gi...@apache.org>.
ppalaga commented on issue #1935:
URL: https://github.com/apache/camel-quarkus/issues/1935#issuecomment-713172366
I guess you need to add the `camel-quarkus-main` dependency as documented in https://camel.apache.org/camel-quarkus/latest/user-guide/bootstrap.html#_camel_main
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] weimeilin79 commented on issue #1935: Properties Bean configure not working with AMQP and Infinispan
Posted by GitBox <gi...@apache.org>.
weimeilin79 commented on issue #1935:
URL: https://github.com/apache/camel-quarkus/issues/1935#issuecomment-721206576
Yes @lburgazzoli
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] lburgazzoli edited a comment on issue #1935: Properties Bean configure not working with AMQP and Infinispan
Posted by GitBox <gi...@apache.org>.
lburgazzoli edited a comment on issue #1935:
URL: https://github.com/apache/camel-quarkus/issues/1935#issuecomment-713379722
No camel-quarkus-main is there by default in camel-k.
Additional note: only the components for which we have an extension that uses beans from build items seems to be affected, as example here, the kafka setup works using camel's conventions whereas the amqp/infinispa do not seem to work.
@weimeilin79 am I right ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] lburgazzoli edited a comment on issue #1935: Properties Bean configure not working with AMQP and Infinispan
Posted by GitBox <gi...@apache.org>.
lburgazzoli edited a comment on issue #1935:
URL: https://github.com/apache/camel-quarkus/issues/1935#issuecomment-713379722
No camel-quarkus-main is there by default in camel-k.
Additional note: only the components for which we have an extension that use beans from build items or registry seems to be affected. As example here, the kafka set-up works using camel's conventions whereas the amqp/infinispan do not seem to work.
@weimeilin79 am I right ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] lburgazzoli edited a comment on issue #1935: Properties Bean configure not working with AMQP and Infinispan
Posted by GitBox <gi...@apache.org>.
lburgazzoli edited a comment on issue #1935:
URL: https://github.com/apache/camel-quarkus/issues/1935#issuecomment-713379722
No camel-quarkus-main is there by default in camel-k.
Additional note: only the components for which we have an extension that uses beans from build items seems to be affected, as example here, the kafka setup works using camel's conventions whereas the amqp/infinispan do not seem to work.
@weimeilin79 am I right ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org