Re: camel-core not detecting converters on bundle restart in karaf4

I don’t know enough about how you are doing this to be sure, but this sounds suspiciously similar to an issue I’ve been fighting for quite a while now. I don’t know if it applies, but you may want to look at the workaround in this ticket ( https://issues.apache.org/jira/browse/CAMEL-9570

Re: camel-core not detecting converters on bundle restart in karaf4

Hi Claus, I havent checked upgrading karaf and camel and to be frank its a little tedious for us to get it upgraded for now but anyways i will try checking that. I ran down into a similar issue with JPA enabled bundles only to discover that Hibernate was causing the issue. https://hibernate.atlass

Re: Processing large PDF files using apache camel 2.10

Hi Claus, Thanks for the reply. Do you mean to place the pdf in a file location and use the stream component http://camel.apache.org/stream.html to get data as stream? Also can you please tell me how the data transfer happens using stream component? Using claim check EIP also at some point stores

Re: Restarting an Endpoint from an ErrorHandler

You can use the controlbus to stop and start routes from another route so in theory if you use the control bus then it should work. On Fri, Dec 16, 2016 at 1:55 PM, sa_james [via Camel] < ml-node+s465427n5791563...@n5.nabble.com> wrote: > Does something like the following make sense? > > onExcept

Re: Restarting an Endpoint from an ErrorHandler

Hi Guess it depends on your case if restarting can fix the connection problem, but try the control bus to stop/start. https://camel.apache.org/controlbus.html Cheers On 16 Dec 2016 14:56, "sa_james" wrote: > Does something like the following make sense? > > onException(*ConnectionException.cla

Restarting an Endpoint from an ErrorHandler

Does something like the following make sense? onException(*ConnectionException.class*).*process( ...stop and restart myendpoint here ...) *from("myendpoint").to("log:test-exception") -- View this message in context: http://camel.465427.n5.nabble.com/Restarting-an-Endpoint-from-an-ErrorHandl

AW: Custom MDC property per exchange

Maybe something like this will end up in the MDC property ("camel.foo") Within the MDCUnitOfWork, we could remove "camel.*". Von: Claus Ibsen Gesendet: Freitag, 16. Dezember 2016 12:30:33 An: users@camel.apache.org Betreff: Re: Custom MDC property per exchan

Re: mutually-authenticated SSL with websockets

I recently did something very similar (not with websocket, instead with netty4-http though). However looking at websocket docs, its very much similar. You'll have to use sslContextParameters endpoint option to specify the contextparameter. In my case I created it as a (spring) bean and provided

Re: Custom MDC property per exchange

Hmm its more a Where you can set a value from any expression, eg a simple ${body.callMe} The trick is to keep track of these custom MDC headers and ensure they are all cleared on thread context switches etc, which is what the MDCUnitOfWork ensures for the OOTB provided. On Fri, Dec 16

Re: camel-core not detecting converters on bundle restart in karaf4

Have you tried with newer versions of karaf and camel. On Fri, Dec 16, 2016 at 2:52 AM, yogu13 wrote: > Any views or ideas on how to come around it? > > Let me know if anyother information is needed. > > Regards, > -Yogesh > > > > -- > View this message in context: > http://camel.465427.n5.nabbl

Re: Catching Exception

See this FAQ http://camel.apache.org/why-does-my-file-consumer-not-pick-up-the-file-and-how-do-i-let-the-file-consumer-use-the-camel-error-handler.html And if you have a copy of the Camel in Action book its explained in the error handler chapter. On Fri, Dec 16, 2016 at 12:08 PM, sa_james wrote

Catching Exception

Does Camel catch Exceptions that occur in the first Producer in a route? lets say I have this: *onException(Exception.class).to("log:exception ${Body}") *from("sjms:queue").to("log:test ${Body}") If I shut down the Queue, an exception is throws in the console but camel does not log it. Am I unde

sjms creating too many unnecessary threadpools and proposal for fixing it

Hi, In my spring+camel integration application we are using SJMS extensively. There are more than 100 producers and more than 50 consumers that we have in our application. Recently I started discovering the usage of threads and noticed from JMX console there are way t many threadpools most

AW: Custom MDC property per exchange

Hi Claus Thanks for the feedback. I've read this as well but I got the opinion that it's not a fit for me. As far as I understand from the interface UnitOfWork it looks to me to allow only a hook before the route starts and after. I'm more looking for an option where during processing time to

Re: NotifyBuilder whenDoneSatisfied mock

When you use from(something) then you filter the messages to be only from that route. So you may have more routes also process messages which then impacts your assertions. On Fri, Dec 16, 2016 at 9:47 AM, sa_james wrote: > I Mean the Assertion error, like so: > > java.lang.AssertionError: mock://

Re: NotifyBuilder whenDoneSatisfied mock

I Mean the Assertion error, like so: java.lang.AssertionError: mock://test Received message count. Expected: <1> but was: <2> I also noticed that when I used the notifyBuilder.*from("something").*whenDoneSatisfied(mock) then it always works. Without the *from("something") *part, it does not alway