Re: websphere mq ciphersuite

2017-08-20 Thread stanleyab
yihtserns is correct. The java standard is that property name first character only has its case changed to construct the 'set' call. The MQ property setter is setSSLCipherSuite. https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_7.5.0/com.ibm.mq.javadoc.doc/WMQJMSClasses/com/ibm/mq/jms/MQCo

Re: Camel Kafka SASL plain with broker list rather than zookeeper

2017-08-20 Thread Chris Snow
I've raised a JIRA to track this: https://issues.apache.org/jira/browse/CAMEL-11682 -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Kafka-SASL-plain-with-broker-list-rather-than-zookeeper-tp5811191p5811365.html Sent from the Camel - Users mailing list archive at Nabble.

Re: JBoss/HornetQ JMS JNDI Spring config - getting connectionFactory must be specified error

2017-08-20 Thread Francis Carlo Gavino
Thanks for the reply Zoran. I think what's happening is that my Spring context is not loading in JBoss. I tried to test it by changing my JMS component id and uri to something else and Camel wasn't able to recognize it. Also, when I pass the connectionFactory as a parameter in the URI the error

Re: Camel Kafka SASL plain with broker list rather than zookeeper

2017-08-20 Thread Chris Snow
I was wondering whether camel should also support consumer.properties and producer.properties files as a configuration mechanism? This would allow developers to easily reuse their existing assets for connecting to kafka. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-K

Re: Camel Kafka SASL plain with broker list rather than zookeeper

2017-08-20 Thread Zoran Regvart
Hi Chris, yeah, they are comma separated (see the source[1]), for the `sasl.mechanism` and `sasl.jaas.config` I don't see support for them in the source code, you're welcome to file an issue or better yet contribute via pull request support for those, perhaps we could also have a generic way of add

Re: Camel Kafka SASL plain with broker list rather than zookeeper

2017-08-20 Thread Chris Snow
Thanks Zoran, from the documentation it appears that I need to pass the parameters: brokers=kafka01-prod01.messagehub.services.eu-de.bluemix.net:9093kafka02-prod01.messagehub.services.eu-de.bluemix.net:9093 ... saslMechanism=PLAIN securityProtocol=SASL_SSL sslProtocol=TLSv1.2 sslEnabledProtocols=T

Re: Error Building Camel

2017-08-20 Thread Zoran Regvart
Hi Christian, seems to be OK on the build machines (sans occasional memory issues), just did a build on my machine without issues. Perhaps a cached dependency in your local Maven repository is the culprit, you could try running with -U to update snapshot versions, zoran On Wed, Aug 16, 2017 at 3