Re: Camel Netty could not process on heavy load

Hi Tadayoshi, If we increase workerCount to 50 - 100 system becomes slow. >From Redhat Team, they are suggesting to keep the workercount between 8-16. Thanks, Jayashankar -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Netty-could-not-handle-more-request-on-load-te

Re: weaveAddFirst doesn't work correctly with route level onException

Yes, changed the method call order. :D We are doing several weave* calls, just put a weaveById first, then it works fine. Actually, in our case, we have to put it last to be sure that our advice is the last(actually the first :)), so it's not just a hack. Anyway, I may report a bug on their issue t

Re: Sftp known_host as byte array

There is a option with byte array /** * Sets the known_hosts from the byte array, so that the SFTP endpoint can do host key verification. */ public void setKnownHosts(byte[] knownHosts) { this.knownHosts = knownHosts; } On Sun, Sep 25, 2016 at 4:12 PM, Goyal, Arpit wrote: > Hi colleagues >

CamelSpringTestSupport - NullPointer on context.getRouteDefinition

Hi, Here is my question.. I'm trying to test an existing route with CamelSpringTestSupport, want to mock endpoints with 'adviceWith', but there get NullPointerException on context.getRouteDefinitions().get(0).. as there're no route definitions, neither routes.. Please, give me a hint of what I'm

Re: CamelSpringTestSupport - NullPointer on context.getRouteDefinition

sorry.. found a solution myself. forgot to add: http://camel.apache.org/schema/spring";> -- View this message in context: http://camel.465427.n5.nabble.com/CamelSpringTestSupport-NullPointer-on-context-getRouteDefinition-tp5788079p5788080.html Sent from the Camel - U

CamelSpringTestSupport - NullPointer on context.getRouteDefinition

Hi, Here is my question.. I'm trying to test an existing route with CamelSpringTestSupport, want to mock endpoints with 'adviceWith', but there get NullPointerException on context.getRouteDefinitions().get(0).. as there're no route definitions, neither routes.. Please, give me a hint of what I'

RE: Sftp known_host as byte array

Hi Colleagues, Anyone has idea here? Regards, Arpit. -Original Message- From: Goyal, Arpit [mailto:arpit.go...@sap.com] Sent: Sunday, September 25, 2016 7:12 AM To: users@camel.apache.org Subject: Sftp known_host as byte array Hi colleagues Is it possible to set the known host of a

Re: Camel isMockEndpointsAndSkip doesn't skip jdbc endpoint

Hi That string you pass can be regex. So if you got something like jdbc:blah?option1=dsff&option2=sdf… You can pass any of the following jdbc.* jdbc:blah.* And to get the reference to the mockendpoint in your unit test @EndpointInject(uri=“mock:jdbc:blah”) private MockEndpoint jdbcEndpoint;

Re: Can't understand what inOnly is doing

On point 5. from the tests I did it appears that direct:xyz is not necessarily InOut/InOnly. Since the producer template with sendBody was an InOnly the behavior of the routes downstream behaved differently than when I used the requestBody which starts as an InOut. Most of the time when using a s

Re: Can't understand what inOnly is doing

Thanks for the all the exploration and explanation. I offer this summary, for comment: 1. The template starts the route with a Message Exchange Pattern (MEP) "InOnly" or "InOut", depending on whether we use template.sendBody() or template.requestBody() respectively 2. The inOut() and inOnly() se

NullPointer. org.apache.camel.component.jms.DefaultJmsMessageListenerContainer

NullPointer. org.apache.camel.component.jms.DefaultJmsMessageListenerContainer I am getting the following runtime exception. Caused by: java.lang.NullPointerException 2016-09-23 16:02:02,682 logLevel="ERROR", thread="Camel (MyRoute) thread #1670 - TemporaryQueueReplyManager[mytopic]", class="org.

Re: weaveAddFirst doesn't work correctly with route level onException

Were you able to finally get it to work correctly? On Mon, Sep 26, 2016 at 1:10 AM, ncsibra wrote: > Yes, weaveById works fine, but in my case I use it in a base class, used by > almost every integration test and those tests are able to modify the route > too before start, so I can't be sure tha

Re: Websocket over HTTP connection

Just as a follow-up, I understand that websockets runs over HTTP with and upgraded HTTP connection but the javascript code will only accept specific URLS. On Mon, Sep 26, 2016 at 11:32 AM, Mark wrote: > > I am working to set up a websocket server using Apache Camel. My > requirement is that the

Re: Can't understand what inOnly is doing

The ExchangePattern appears to have more scope than I'd initially believed. Just haven't had much need to delve into it that deep as most of my use cases are for request/response we services or file unmarshaling or even request/response with a pass of to seda or JMS and a quick response back to

Re: Camel isMockEndpointsAndSkip doesn't skip jdbc endpoint

Usually, I'd just override createCamelContext() and add "jdbc" as a StubComponent. On 26 September 2016 at 09:37, dermoritz wrote: > I have a route that end on a jdbc endpoint: > > > > The jdbc Endpoint is created this way: > > > > In my unit test i want "mock and skip" the database: > > > > I

Websocket over HTTP connection

I am working to set up a websocket server using Apache Camel. My requirement is that the javascript code requires an http/https based URL. I am trying to figure out how to proxy this data through Apache but now I'm wondering if it would be easier to do all this using Camel. Does anyone have any e

Re: Can't understand what inOnly is doing

I have checked the code of PatternDefinition.inOnly(...) and this just calls the PatternDefinition.to(...) method with the ExchangePattern set to InOnly. So let us forget the method inOnly(). What does it mean to set the ExchangePattern to "InOnly" (or even "InOut")? There are various ways how t

Camel isMockEndpointsAndSkip doesn't skip jdbc endpoint

I have a route that end on a jdbc endpoint: The jdbc Endpoint is created this way: In my unit test i want "mock and skip" the database: I also tried other patterns: "jdbc:db", "jdbc://db" (this string is shown in log and is the output of toString) But no matter what pattern used the

Re: Loop should continue after exception caught.

Yes, I use 2.17.3. -- View this message in context: http://camel.465427.n5.nabble.com/Loop-should-continue-after-exception-caught-tp5787979p5788064.html Sent from the Camel - Users mailing list archive at Nabble.com.