Hi,
Can we access the context of one camel-k integration from another camel-k
integration?
e.g a.groovy has bean 'a'
Can we access bean 'a' from b.groovy ?
Thank you,
Narsi
ssages ?
>
> On Wed, Feb 2, 2022, 17:35 Narsi Reddy Nallamilli <
> narsi.nallami...@gmail.com> wrote:
>
> > Hi Arnaud,
> >
> > Yup, It used to work before because I use it in my project and was not
> > aware of the bug till you reported.
> >
> > Can
rticle
> > <
> https://blog.christianposta.com/camel/very-fast-camels-and-cloud-messaging/>
> it
> > has worked in the past. Shouldn't we open an issue ?
> >
> > Thanks again!
> > Arnaud
> >
> > On Wed, Feb 2, 2022 at 5:52 PM Narsi Reddy Nallamilli <
; So in this example, each consumer will pull no more than 10 messages per
> > poll to the SQS Queue. So if there are less than 10 messages on your
> > queue, the other consumers aren't going to really get an messages.
> >
> > On Mon, Jan 31, 2022 at 7:15 AM Arnaud Lev
Hi Arnaud,
Is your AWS queue type fifo or standard?
On Mon, 31 Jan, 2022, 17:31 Arnaud Level, wrote:
> Hi,
>
> (Camel version: camel-aws2-sqs-starter: 3.12.0)
>
> I am trying to use and understand concurentConsumers with a SQS queue:
>
>
Correct. Maven is not yet updated.
On Fri, Dec 17, 2021 at 3:06 PM Claus Ibsen wrote:
> Hi Gregor
>
> It does not seem that the 3.14.0 release are in maven central.
> I assume you promoted yesterday so they should really be there by now.
>
>
>
> On Wed, Mar 10, 2021 at 2:06 PM Narsi Reddy Nallamilli
> wrote:
> >
> > Hi,
> >
> > I have a executorservice build from threadpoolbuilder.
> >
> > public ExecutorService jobThreadPool() throws Exception {
> > return new
> ThreadPoolBui
Hi,
I have a executorservice build from threadpoolbuilder.
public ExecutorService jobThreadPool() throws Exception {
return new
ThreadPoolBuilder(getContext()).poolSize(50).maxPoolSize(500).keepAliveTime(180).build("jobThread");
}
I would like to set thread before executing the task, just
Hi,
I moved from 2.x to 3.x and see getOut() on exchange is now depreciated.
But the intention to replace it with getMessage is not inline with the
behaviour of getOut().
https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_getout_on_message
As stated in above link the
Hi,
Any help on this?
On Tue, Jan 21, 2020 at 5:56 PM Narsi Reddy Nallamilli <
narsi.nallami...@gmail.com> wrote:
> Hi,
>
> I moved from 2.x to 3.x and see getOut() on exchange is now depreciated.
> But the intention to replace it with getMessage is not inline with the
>
Hi,
I moved from 2.x to 3.x and see getOut() on exchange is now depreciated.
But the intention to replace it with getMessage is not inline with the
behaviour of getOut().
https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_getout_on_message
As stated in above link the
cluster-labels[app]=
> ${project.artifactId}
>
>
> On Thu, Oct 10, 2019 at 12:55 PM Narsi Reddy Nallamilli <
> narsi.nallami...@gmail.com> wrote:
>
> > Hi,
> >
> > I am trying to run below camel app in minikube, however receiving below
> > error. any help?
&
Hi,
I am trying to run below camel app in minikube, however receiving below
error. any help?
JDK version: 8
camel-version 2.24.2
example : https://github.com/nicolaferraro/camel-leader-election
minikube version: v1.4.0
2019-10-07 11:48:29.229 WARN 1 --- [rshipController]
Hi,
Timeout valued in http-conf:conduit set in my soapContext.xml are not
getting applied to my WebClient. When I try to inspect the webclient
which is getting created
in JAXRSClientFactoryBean it shown the connectiontimout value 3
whereas I have set to 70 in the httpconduit.
Please
14 matches
Mail list logo
