Re: Kafka - Issue with additionalProperties
Hi Omar
Highly appreciate your response on this matter. You are on point, i was
using 3.7.0 anddiscovered this later and posted the same on stack trace.
https://stackoverflow.com/questions/67307832/camel-kafka-additionalproperties-issue/67307854#67307854
Much appreciate it.
Thanks & Regards
Anand
On Wed, Apr 28, 2021 at 11:39 AM Omar Al-Safi wrote:
> Hi,
>
> I guess you are using the Endpoint DSL? Which Camel version do you use
> here?
>
> In case you are running Camel 3.7.0, I recall the additionalProperties was
> broken in the kafka component and it was fixed in 3.7.1 and 3.8.0.
>
> Regards,
> Omar
>
> On Wed, Apr 28, 2021 at 3:19 PM anandakrishnan ramakrishnan <
> anand140...@gmail.com> wrote:
>
> > I am having issue with setting additionalProperties. I am setting the
> > property as below
> >
> > Map additionalProperties = new HashMap<>();
> > additionalProperties.put("sasl.login.callback.handler.class",
> >
> >
> >
> "io.confluent.kafka.clients.plugins.auth.token.TokenUserLoginCallbackHandler");
> >
> > Followed by the Kafka route builder is setup as below
> >
> > .additionalProperties(additionalProperties)
> >
> > However the property i see populated in the kafka config show up as
> >
> >
> "sasl"->"io.confluent.kafka.clients.plugins.auth.token.TokenUserLoginCallbackHandler"
> >
> > The reason being the PropertyBindingSupport.java is splitting by dot
> >
> > // we should only walk and create OGNL path for the middle graph
> >
> > String[] parts;
> > if (isDotKey(name)) {
> > parts = splitKey(name);
> > } else {
> > parts = new String[] { name };
> > }
> >
> > // which only picks up "sasl" instead of
> > "sasl.login.callback-handler.class"
> >
> > newName = parts[i + 1];
> >
> > Any help is appreciated.
> >
>
Unable to set CXF CachedOutputStream.Threshold
Hi, I am using camel-cxf and have exposed soap service over HTTP using
cxfEndpoint. There are few requests that are getting logged into the /tmp
folder as the size is great than 64K-128K.
I want to increase the memory size greater than 128K so that the request
does not gets saved in the /tmp folder.
Below is my spring-config.xml where I am creating the camel-cxf bus object.
This is the default bus object when I verified after looking into the
source code of io.apache.cxf.io.CachedOutputStream.java class.
<*bean **class*
="org.apache.camel.component.cxf.transport.CamelTransportFactory">
<*property **name*="bus" *ref*="cxf" />
<*property **name*="transportIds">
<*list*>
<*value*>http://cxf.apache.org/transports/camel
<*property **name*="checkException" *value*="true">
I am including the cxfEndpoints in my spring-config.xml file.
<*import **resource*="endpoints/TestEndpoint.xml" />
<*cxf**:cxfEndpoint **id*="cXFTestHttp"
*address*="/TestService/TestServiceName"
*loggingFeatureEnabled*="true" *endpointName*="a:***SOAPPort"
*wsdlURL*="META-INF/wsdl/TestService/.wsdl"
*serviceName*="a:TestService"
*serviceClass*="com.example.***"
*xmlns:**a*="http://test***;>
<*cxf**:properties*>
<*entry **key*="schema-validation-enabled"
*value*="${schema.validation.enabled}" />
<*entry **key*="org.apache.cxf.io.CachedOutputStream.Threshold"
*value*="256000"/>
<*entry **key*="org.apache.cxf.io.CachedOutputStream.MaxSize"
*value*="1000"/>
<*entry **key*="bus.io.CachedOutputStream.OutputDirectory" *value*="/tmp"/>
<*cxf**:inInterceptors*>
<*ref **bean*="ecsLoggingInInterceptor" />
<*cxf**:outInterceptors*>
<*ref **bean*="ecsLoggingOutInterceptor" />
These properties are not getting picked up.
I also tried adding and its properties, but the xml throw
exception
<*cxf**:bus **id*="cxf">
<*cxf**:properties*>
<*entry **key*="org.apache.cxf.io.CachedOutputStream.Threshold"
*value*="256000" />
<*entry **key*="org.apache.cxf.io.CachedOutputStream.OutputDirectory"
*value*="/tmp" />
Caused by:
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line
70 in XML document from file [*] is invalid;
nested exception is org.xml.sax.SAXParseException; lineNumber: 70;
columnNumber: 21; cvc-complex-type.2.4.c: The matching wildcard is strict,
but no declaration can be found for element 'cxf:bus'.
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:402)
~[spring-beans-5.2.7.RELEASE.jar:5.2.7.RELEASE]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:338)
~[spring-beans-5.2.7.RELEASE.jar:5.2.7.RELEASE]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310)
~[spring-beans-5.2.7.RELEASE.jar:5.2.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188)
~[spring-beans-5.2.7.RELEASE.jar:5.2.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:224)
~[spring-beans-5.2.7.RELEASE.jar:5.2.7.RELEASE]
at
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.importBeanDefinitionResource(DefaultBeanDefinitionDocumentReader.java:255)
~[spring-beans-5.2.7.RELEASE.jar:5.2.7.RELEASE]
... 30 more
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The
matching wildcard is strict, but no declaration can be found for element
'cxf:bus'.
What am I missing here. Where should I add these properties effectively ?
Any help appreciated. I am using camel version 3.4.5 and cxf version is
3.3.6.
-Regards
Srikant Mantha
Re: Kafka - Issue with additionalProperties
Hi,
I guess you are using the Endpoint DSL? Which Camel version do you use
here?
In case you are running Camel 3.7.0, I recall the additionalProperties was
broken in the kafka component and it was fixed in 3.7.1 and 3.8.0.
Regards,
Omar
On Wed, Apr 28, 2021 at 3:19 PM anandakrishnan ramakrishnan <
anand140...@gmail.com> wrote:
> I am having issue with setting additionalProperties. I am setting the
> property as below
>
> Map additionalProperties = new HashMap<>();
> additionalProperties.put("sasl.login.callback.handler.class",
>
>
>
> "io.confluent.kafka.clients.plugins.auth.token.TokenUserLoginCallbackHandler");
>
> Followed by the Kafka route builder is setup as below
>
> .additionalProperties(additionalProperties)
>
> However the property i see populated in the kafka config show up as
>
> "sasl"->"io.confluent.kafka.clients.plugins.auth.token.TokenUserLoginCallbackHandler"
>
> The reason being the PropertyBindingSupport.java is splitting by dot
>
> // we should only walk and create OGNL path for the middle graph
>
> String[] parts;
> if (isDotKey(name)) {
> parts = splitKey(name);
> } else {
> parts = new String[] { name };
> }
>
> // which only picks up "sasl" instead of
> "sasl.login.callback-handler.class"
>
> newName = parts[i + 1];
>
> Any help is appreciated.
>
Kafka - Issue with additionalProperties
I am having issue with setting additionalProperties. I am setting the
property as below
Map additionalProperties = new HashMap<>();
additionalProperties.put("sasl.login.callback.handler.class",
"io.confluent.kafka.clients.plugins.auth.token.TokenUserLoginCallbackHandler");
Followed by the Kafka route builder is setup as below
.additionalProperties(additionalProperties)
However the property i see populated in the kafka config show up as
"sasl"->"io.confluent.kafka.clients.plugins.auth.token.TokenUserLoginCallbackHandler"
The reason being the PropertyBindingSupport.java is splitting by dot
// we should only walk and create OGNL path for the middle graph
String[] parts;
if (isDotKey(name)) {
parts = splitKey(name);
} else {
parts = new String[] { name };
}
// which only picks up "sasl" instead of "sasl.login.callback-handler.class"
newName = parts[i + 1];
Any help is appreciated.
Re: Camel Kubernetes Deployment Component issue
Thanks, it worked. On Wed, Apr 28, 2021 at 4:42 PM Andrea Cosentino wrote: > Hello, > > You need to specify the following header with the number of > replicas: CamelKubernetesDeploymentReplicas > > Cheers. > > Il giorno mer 28 apr 2021 alle ore 13:00 Bikash Kaushik < > kaushikbikas...@gmail.com> ha scritto: > > > Hi Team, > > > > I'm facing an issue while setting a replica number using the camel > > Kubernetes deployment component. > > > > *Please help me in fixing this issue.* > > > > *Route :* > > > > > > > > > > name="CamelKubernetesNamespaceName">bikash-test > > > > name="CamelKubernetesDeploymentName">frontend > > > > > > > > > > *Error :* > > java.lang.IllegalArgumentException: *Scale a specific deployment require > > specify a replicas number* > > at > > > > > org.apache.camel.component.kubernetes.deployments.KubernetesDeploymentsProducer.doScaleDeployment(KubernetesDeploymentsProducer.java:186) > > at > > > > > org.apache.camel.component.kubernetes.deployments.KubernetesDeploymentsProducer.process(KubernetesDeploymentsProducer.java:83) > > at > > > > > org.apache.camel.support.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:66) > > at > > > > > org.apache.camel.processor.SendProcessor.lambda$process$2(SendProcessor.java:191) > > -- > > > > > > *Regards,* > > *Bikash Kaushik* > > > -- *Regards,* *Bikash Kaushik*
Re: Camel Kubernetes Deployment Component issue
Hello, You need to specify the following header with the number of replicas: CamelKubernetesDeploymentReplicas Cheers. Il giorno mer 28 apr 2021 alle ore 13:00 Bikash Kaushik < kaushikbikas...@gmail.com> ha scritto: > Hi Team, > > I'm facing an issue while setting a replica number using the camel > Kubernetes deployment component. > > *Please help me in fixing this issue.* > > *Route :* > > > > name="CamelKubernetesNamespaceName">bikash-test > name="CamelKubernetesDeploymentName">frontend > > > > > *Error :* > java.lang.IllegalArgumentException: *Scale a specific deployment require > specify a replicas number* > at > > org.apache.camel.component.kubernetes.deployments.KubernetesDeploymentsProducer.doScaleDeployment(KubernetesDeploymentsProducer.java:186) > at > > org.apache.camel.component.kubernetes.deployments.KubernetesDeploymentsProducer.process(KubernetesDeploymentsProducer.java:83) > at > > org.apache.camel.support.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:66) > at > > org.apache.camel.processor.SendProcessor.lambda$process$2(SendProcessor.java:191) > -- > > > *Regards,* > *Bikash Kaushik* >
Camel Kubernetes Deployment Component issue
Hi Team, I'm facing an issue while setting a replica number using the camel Kubernetes deployment component. *Please help me in fixing this issue.* *Route :* bikash-test frontend *Error :* java.lang.IllegalArgumentException: *Scale a specific deployment require specify a replicas number* at org.apache.camel.component.kubernetes.deployments.KubernetesDeploymentsProducer.doScaleDeployment(KubernetesDeploymentsProducer.java:186) at org.apache.camel.component.kubernetes.deployments.KubernetesDeploymentsProducer.process(KubernetesDeploymentsProducer.java:83) at org.apache.camel.support.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:66) at org.apache.camel.processor.SendProcessor.lambda$process$2(SendProcessor.java:191) -- *Regards,* *Bikash Kaushik*
Re: Camel-K on Google Cloud Run
Hi, since Google Cloud Run is not Kubernetes-based, the Camel K operator cannot run in it. Camel K works fine on GKE instead. Recently we've introduced the "kamel local run" / "kamel local build" commands that should enable you creating container images for your Camel K integrations. Technically, you should be able to encapsulate your integration into a container image using those commands, then pass the container image to cloud run, but this is something that I've never tried. Nicola On Wed, Apr 28, 2021 at 11:18 AM Gerald Kallas wrote: > Hi all, > > does Camel-K run on Google Cloud Run? > > Best > Gerald
Camel-K on Google Cloud Run
Hi all, does Camel-K run on Google Cloud Run? Best Gerald
