Hi Ranx,
Thanks for the response.
I will not be able to pass any object type other string to setBody or
simpleExpression methods. I just want to pass a dynamic value to the route.
The message i'm getting is,
Message History
---
thanks it worked.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-2-16-2-spring-and-java-DSL-register-tp5780772p5780844.html
Sent from the Camel - Users mailing list archive at Nabble.com.
By the way, when the quartz timer fires what are you expecting that data to
be in the bodyMap? Is that just an instance variable at that point?
Perhaps if you posted the complete code it would make that a bit clearer.
>From what I can see of your route snippet I'd expect some quartz timer
event to
.setBody(new SimpleExpression(bodyMap.toString()))
.convertBodyTo(Map.class)
Aren't you converting the object twice? First to a String and then telling
it to convert the String to a Map (which it doesn't know how to handle)?
bodyMap.toString(). Assuming it doe
Hi,
I'm accessing a route through both producertemplate and a QuartzScheduler.
*Route:*
select * from table where empId=${in.body.EmpId}
*I'm able to successfully pass employee id using producer template like
below,*
Map bodyMap = new HashMap();
bodyMap.put("EmpId"
The Camel community announces the immediate availability of the new
patch release Camel 2.16.3, the last planned release for the 2.16.x
branch. This release contains over 75 bug fixes and improvements
applied in the past months by the community on the Camel 2.16.x
branch.
The artifacts are publish
Yes, but curl is hardly a yardstick to measure. For one, you're testing
sequentially with curl, which means you close your connection before starting
the next one. If we consider a server limit, bear in mind that http4 in Camel
uses keep-alive. You can control that using the connectionTimeToLive
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Hive-Issue-tp5780522p5780842.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Loannis,
On Apr 9, 2016 20:18, "Ioannis Mavroukakis" wrote:
>
> You're getting a 400 back, but you're not giving us a whole lot to go on
:-).
Its all I am getting :)
>
> Is there a limit set server side perhaps? Can you consistently sustain 39
iterations?
Yes It goes up to 41. I don't think th
You're getting a 400 back, but you're not giving us a whole lot to go on :-).
Is there a limit set server side perhaps? Can you consistently sustain 39
iterations?
> On 9 Apr 2016, at 15:22, rajan agarwal wrote:
>
> Hi All,
>
> I am facing a issue when i try to call a external webservice in
Hi All,
I am facing a issue when i try to call a external webservice in a loop. It
runs fine if the loop runs for upto 40 iterations but begins failing after
that. I am unable to understand the cause as well. I think that it might be
due to some sort of limit getting reached, i implemented a throt
The issue is the login rest endpoint is getting called twice when I invoke it
once by below process.
When I hit http://localhost:8080/login it calls the cxfrs server which calls
the cxfrs client according to below route.
Then the client is calling another cxfrs service which has got the
Try this
* in your `log4.properties`:
log4j.logger.org.apache.http=DEBUG
* or if you use Camel with Spring Boot in your `application.properties`:
logging.level.org.apache.http=DEBUG
Am 09.04.2016 um 11:39 schrieb Debraj Manna:
Yeah that is what I am looking for. But I did not find anyth
Yeah that is what I am looking for. But I did not find anything in the
Camel Http Component doc.
http://people.apache.org/~dkulp/camel/http4.html
On Sat, Apr 9, 2016 at 11:38 AM, Claus Ibsen wrote:
> Its the http4 client that sends the http request, so it may have some
> logging you can see if
Hi
Ah well spotted. You are welcome to log a JIRA ticket.
http://camel.apache.org/support.html
And work on a patch to make Camel create parent nodes. Yeah the ZK api
is low level and you need to manually do a bunch to make it work.
There is a ticket to use Curator to make working with ZK pleasant
No it runs fast for us.
I suspect its on your end. Maybe some proxy http server or that 2.17
needs to be downloaded while older releases is already.
On Fri, Apr 8, 2016 at 9:24 AM, Thomas Weinschenk
wrote:
> Hi everyone,
>
> I tried to upgrade from Camel 2.16.2 to 2.17.0 but I am facing the prob
Hi
Sorry but its hard to help you with such a problem. You paste a bunch
of configuration but dont talk so much about what rest is called two
times, and what you do.
Please dive more into your problem and try to narrow down what happens.
It may be that you are indeed calling it 2 times.
On Wed,
Hi
I logged a ticket to avoid attempting to close if already closed
https://issues.apache.org/jira/browse/CAMEL-9845
On Wed, Apr 6, 2016 at 7:43 PM, VinothKR wrote:
> I was able to make it work with a older version of camel 2.13.2. But with the
> 2.16.1 version it is throwing this issue. Ideal
That would be a bit odd as this is the code that maps the netty status to Camel
headers.put(Exchange.HTTP_RESPONSE_CODE, response.getStatus().code());
headers.put(Exchange.HTTP_RESPONSE_TEXT, response.getStatus().reasonPhrase());
Have you turned off mapHeaders by any chance?
On Fri, Apr 8, 201
19 matches
Mail list logo