Claus:
Once again, thank you for your reply.
Even my real-world application processes the messages much, much faster than 20
seconds. However, I can also replicate the problem using the sample class
below (which reads the in message, appends a String to it, and returns the
result). So, as I
I was able to build an app with OsgiDefaultCamelContext, but I had to
add a ServiceTracker to wait for
org.apache.camel.spi.TypeConverterLoader to be registered. Before I
did that, my bundles were trying to create SEDA queues before
camel-core had finished loading.
If camel-core-osgi is going to
Cool, thanks :-) I'll check this out and give you some feedback.
Best regards,
Harald
Am 31.03.2011 11:57, schrieb davsclaus:
This has been implemented in Camel 2.8. You can now use Future in your client
interfaces, and the invocation will now be asynchronous.
And there is a little example her
Thanks for your fast response.
I know that i can get notifications from camel but i like that nagios
call camel and check if the route is running. So i need a attribute
which can i easy check without
saving timestamps.
Regards,
Michael
Thank you, I will check it using the example provided.
--
View this message in context:
http://camel.465427.n5.nabble.com/Exchange-MAXIMUM-CACHE-POOL-SIZE-is-not-affecting-producers-created-by-recipientList-tp4257273p4275924.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Works fine. I added an unit test
http://svn.apache.org/viewvc?rev=1087773&view=rev
On Fri, Mar 25, 2011 at 2:05 PM, Marco Crivellaro
wrote:
> this affects 2.7.0 release too
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Exchange-MAXIMUM-CACHE-POOL-SIZE-is-not-affecti
On Fri, Apr 1, 2011 at 4:34 PM, Claus Ibsen wrote:
> Just use a direct endpoint in the DLC.
>
> Then you can use a camel route where you can grab the caused exception
> message and do whatever you want with it.
>
You can also just use a bean endpoint in the DLC.
And then in the bean (pojo) have
On Fri, Apr 1, 2011 at 4:42 PM, Charles Moulliard wrote:
> I think that Michael is looking for a component that they can use to
> connect to Camel from Nagios active ...
>
And that's what camel-nagios can do.
It can send ALERTS to nagios from Camel, when something goes wrong,
such as an Exchange
I think that Michael is looking for a component that they can use to
connect to Camel from Nagios active ...
On Fri, Apr 1, 2011 at 4:36 PM, Claus Ibsen wrote:
> Hi
>
> There is a camel-nagios component
> http://camel.apache.org/nagios
>
> On Fri, Apr 1, 2011 at 11:16 AM, Michael Prieß
> wrote:
Hi
There is a camel-nagios component
http://camel.apache.org/nagios
On Fri, Apr 1, 2011 at 11:16 AM, Michael Prieß
wrote:
> Hi,
>
> i have the problem that i like to monitor my camel routes with Nagios.
> Know anyone a Nagios plugin or something else to monitor camel with
> Nagios active easily?
Just use a direct endpoint in the DLC.
Then you can use a camel route where you can grab the caused exception
message and do whatever you want with it.
On Fri, Apr 1, 2011 at 2:58 PM, John McDonald wrote:
> I feel this is an embarrassingly simple question - but I've read around and
> cant get
I feel this is an embarrassingly simple question - but I've read around and
cant get things to happen the way I want.
I am using the following dead-letter channel as a strategy for handling errors
errorHandler(deadLetterChannel("log:RoutingError?level=ERROR"));
but my problem is that I
reason why I am asking is because I've tried to set it to a low value (say
50) and then send several messages to a list of 100 unique recipents (3
recipient for each exchange).
I than took a snapshot with jmap and found all 100 producers
--
View this message in context:
http://camel.465427.n5.na
Hi,
The Recipient List uses the default size for the ProducerCache which is set
to Exchange.MAXIMUM_CACHE_POOL_SIZE in the camel context. If no value is set
by the user in the camel context for this property, the default cache size
is set to 1000.
There is no operation on the recepient list to ge
Thanks Willem :)
On Fri, 2011-04-01 at 04:07 -0700, Willem Jiang wrote:
> Hi Paul,
>
> Cool. It's good to see you find a way to resolve this issue.
>
> Just one more note for the InputStreamCache, if you want to read the
> body again, you just need to call the method reset() of
> InputStreamCache.
Hi Paul,
Cool. It's good to see you find a way to resolve this issue.
Just one more note for the InputStreamCache, if you want to read the
body again, you just need to call the method reset() of InputStreamCache.
Willem
On 4/1/11 5:49 PM, Paul Lowry wrote:
Hi Willem,
My route looks like th
Thanks,Claus:
The real problem is spring doesn't understand the camel's xml schema. For
example:
the camel processor may dependency on a spring bean by the beanId; but the
spring know nothing about this;
So I am wondering if camel has carefully deal the destroy life cycle? I try
to ch
Is there a way to get the current cache size when using a recipientList?
in my route I am consuming messages from an ActiveMQ queue and then sending
to recipients using the recipientList.
--
View this message in context:
http://camel.465427.n5.nabble.com/getCurrentCacheSize-when-using-recipientL
Hi Willem,
My route looks like this:
http://localhost:9090/client?restletMethod=POST"/>
POST
text/xml
http://localhost:8080/server"/>
The processor at the end is defined as follows:
public class MyResponseProcessor implements Processor
{
public void process(Exc
Hi,
i have the problem that i like to monitor my camel routes with Nagios.
Know anyone a Nagios plugin or something else to monitor camel with
Nagios active easily?
JMX provide a few attributes like ExchangesTotal and ExchangesFailed
this is nice but not easy to monitor. What i need is a attribut
On Fri, Apr 1, 2011 at 9:20 AM, ext2 wrote:
>
>
> Hi:
> With spring, caml processors may depend on many beans. Could camel
> will ensure the camelcontext will be destroy before all the dependencies
> while spring context is destroy?
>
>
Check the spring documentation how it allows you to c
Hi Paul,
Can you check the response from the outside server is right.
I guess the issue of converting the InputStreamCache object to Document
could be caused by the server didn't send the reply message rightly.
Willem
On 4/1/11 4:10 PM, Paul Lowry wrote:
Hi Willem,
I did what you suggested
Hi Willem,
I did what you suggested and got another error...
DefaultTypeConverter DEBUG No type converter available to convert from
type: org.apache.camel.converter.stream.InputStreamCache to the required
type: org.w3c.dom.Document with value
org.apache.camel.converter.stream.InputStreamCache@1cb
Hi:
With spring, caml processors may depend on many beans. Could camel
will ensure the camelcontext will be destroy before all the dependencies
while spring context is destroy?
Hi
The JPA can also do this
http://camel.apache.org/jpa
It will delete the record after it has been processed. If you want to
customize this you can set the option to false and use @Consumed in
the Entity pojo and that method would be invoked. Check the source
code of camel-jpa for examples.
On
25 matches
Mail list logo
