Hello again,
update I saw on the documentation the *lazyStartProducer* flag, but the
question remains for the MO's (consumers) as well.
BR,
Memas
Στις Τρί, 12 Ιαν 2021 στις 10:12 π.μ., ο/η Memas kal
έγραψε:
> Hello,
>
> In my scenario, I have a consumer that produces to a set of SMSC
> connect
Hi
You can use supervised route controller that can use a retry mechanism
to restart consumer routes that fail to startup
On Tue, Jan 12, 2021 at 9:19 AM Memas kal wrote:
>
> Hello,
>
> In my scenario, I have a consumer that produces to a set of SMSC
> connections using
> the SMPP Apache Camel c
Hello,
In my scenario, I have a consumer that produces to a set of SMSC
connections using
the SMPP Apache Camel component and the load balance pattern.
The multiple SMSC connections are used for load balancing and failover when
an SMSC
cluster is down. The problem is that when a connection is dow
Camel 2.20 has a new route controller that can start routes in
parallel and asynchronous and have retries etc. As its new we marked
it experimental as we may refine the api and implementation over the
next couple of releases.
Its intended to be the default way for Camel 3.0.
On Mon, Oct 23, 201
Hello,
During application startup we create a lot of routes of which some endpoints
(ftp, sftp and ftps, etc) can be offline. This can be quite blocking because of
connection timeouts and reconnect attempts. Currently this is 3x 45000ms. What
I am looking for is a way to start multiple routes s
Did you try to use JConsole to look up the status of camel routes[1]?
From your description I double if the camel-jms can access the JMS broker
rightly.
[1]http://camel.apache.org/camel-jmx.html
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (
Hi
Please do not cross post the same message to many mailing lists.
The correct mailinglists for getting help with Camel is the user mailinglist.
Also please do not mail the Camel team directly. Apache Camel is an open project
and all discussions should happen in the open so everyone can see / pa
Hi,
We are using Camel 2.9 in our application. The role of which is to read the
message from one end point and pass it to another endpoint which is a POJO
which takes care of processing the message.
We use Spring xml based configuration to define the JNDITemplate and endpoints
and things worke
-
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 8.028s
> [INFO] Finished at: Tue Feb 01 16:21:21 CET 2011
> [INFO] Final Memory: 14M/166M
> [INFO]
> --
--
So, my question is : what did I do wrong ?
Regards.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-startup-tp3367829p3367829.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Perfect!
2010/5/5 Guillaume Nodet :
> I've created https://issues.apache.org/activemq/browse/CAMEL-2693 for that.
>
> On Thu, Apr 29, 2010 at 14:06, Bengt Rodehav wrote:
>
>> Hello Willem,
>>
>> Yeah, I guess it could potentially be a lot of service dependencies.
>> Remember though that these dep
I've created https://issues.apache.org/activemq/browse/CAMEL-2693 for that.
On Thu, Apr 29, 2010 at 14:06, Bengt Rodehav wrote:
> Hello Willem,
>
> Yeah, I guess it could potentially be a lot of service dependencies.
> Remember though that these dependencies are present regardless if we
> handle
Hello Willem,
Yeah, I guess it could potentially be a lot of service dependencies.
Remember though that these dependencies are present regardless if we
handle them or not. If I have routes referring to 10 components, then
these components MUST be registered before I create my routes. Right?
Today
Bengt Rodehav wrote:
This is exactly the way I was thinking:
- Define a new interface representing a Camel component ( e g
CamelComponentService)
- Use a service property to identify the specific componente (e g
"camel.component")
This enables me to wait for a service with that specific service
Guillaume Nodet wrote:
We don't have to add anything to the component jars I think. It should be
possible to extend camel-osgi bundle in the following way:
* when a bundle containing a component is started, register a service in
the osgi registry for the component. I think it should be a new
This is exactly the way I was thinking:
- Define a new interface representing a Camel component ( e g
CamelComponentService)
- Use a service property to identify the specific componente (e g
"camel.component")
This enables me to wait for a service with that specific service
property to be availab
We don't have to add anything to the component jars I think. It should be
possible to extend camel-osgi bundle in the following way:
* when a bundle containing a component is started, register a service in
the osgi registry for the component. I think it should be a new interface
which will
Bengt Rodehav wrote:
Thanks for your reply Willem,
I will try to the bundle dependency of camel-core to my route bundle
as you suggested - sounds like good advice.
I wasn't sure what you mean by your last paragraph:
If you need to dependent on some specify component interface will introduce
t
Guillaume Nodet wrote:
On Wed, Apr 28, 2010 at 17:30, Bengt Rodehav wrote:
Thanks for your reply Willem,
I will try to the bundle dependency of camel-core to my route bundle
as you suggested - sounds like good advice.
This won't work I think. The reason is that a camel component will only
On Wed, Apr 28, 2010 at 17:30, Bengt Rodehav wrote:
> Thanks for your reply Willem,
>
> I will try to the bundle dependency of camel-core to my route bundle
> as you suggested - sounds like good advice.
>
This won't work I think. The reason is that a camel component will only be
used
if the bun
Thanks for your reply Willem,
I will try to the bundle dependency of camel-core to my route bundle
as you suggested - sounds like good advice.
I wasn't sure what you mean by your last paragraph:
> If you need to dependent on some specify component interface will introduce
> the OSGi related depe
Hi
Please see my comments in the mail.
Bengt Rodehav wrote:
I'm using Karaf to deploy my Camel routes. However, I run into
problems during startup due to dependency ordering. Some of these
ordering problems are OSGI/Karaf specific and have nothing to do with
Camel. I've discussed them on the Fe
I'm using Karaf to deploy my Camel routes. However, I run into
problems during startup due to dependency ordering. Some of these
ordering problems are OSGI/Karaf specific and have nothing to do with
Camel. I've discussed them on the Felix user mailing list and I have
workarounds for that. The Camel
23 matches
Mail list logo
