Hi All,
I am using camel to call REST URLs. In doing so, I am setting the
CamelHttpUri header to override the URI. This works properly with http/https
(Http client 3.x). However, it fails for http4/https4 (Http Client 4.x).
Below is the stack trace for https4
Stacktrace
Hi
I’m using Camel 2.18.0 and Spring Boot. I’m trying to write a unit test that
excludes any Camel from starting up.
Prior to 2.18.0, I could do this by simply excluding CamelAutoConfiguration.
But now in 2.18.0, it looks like a whole bunch of other AutoConfiguration for
Camel has been added.
Hi All,
Is there any test(in GitHub or tutorial) that i can refer to test the
routes with various USER Roles. I couldn't find any test online using
the producer template injecting various roles.
Please let me know.
Regards,
Aravind
We have a camel route which uses the length of exchange message body to
determine data types. It works fine when the body contains a string or array
of objects, but if it contains array of primitive types, it only returns 1
as length. Below is a simplified version of the route:
Camel uses the id of the route as the logger name by default. If you
want to use a different name you can specify the logger name in the
On Thu, Oct 20, 2016 at 8:08 PM, ychawla wrote:
> Hi Shuston,
> I can do log:set DEBUG but then I log everything. I have a file
I'm only guessing sort of, but try the camel context id.
You could get a more definitive answer by letting it log DEBUG everything, find
the lines you want from your route(s) and note the name they're logged under,
then just use that.
-Steve
> -Original Message-
> From: ychawla
Hi Shuston,
I can do log:set DEBUG but then I log everything. I have a file endpoint
that I poll from and that generates too much logging for it to be useful.
Is there a way to isolate it to the route or context level?
Thanks,
Yogesh
--
View this message in context:
Try log:set DEBUG
> -Original Message-
> From: ychawla [mailto:premiergenerat...@gmail.com]
> Sent: Thursday, October 20, 2016 11:34 AM
> To: users@camel.apache.org
> Subject: Camel Log - Karaf
>
> Hello All,
> I have a log statement in a camel route that is at the DEBUG loggingLevel:
>
Hello All,
I have a log statement in a camel route that is at the DEBUG loggingLevel:
>From the karaf console, how can I set the logging level for the camel
context?
I know that I can run a karaf command like this to set the logging level for
a java package:
log:set DEBUG org.packagename.here
Requirement: Convert the Webservices & MQ's running in WAS 8.5 to Apache
Camel framework project and eliminate WAS 8.5.
Currently we have Play projects running in Play servers(2.2.2).
Ask is
1. can we deploy the Camel framework in Play?
2. is there any Camel module in Play ?
3. I raised a
Requirement: Convert the Webservices & MQ's running in WAS 8.5 to Apache
Camel framework project and eliminate WAS 8.5.
Currently we have Play projects running in Play servers(2.2.2).
Ask is
1. can we deploy the Camel framework in Play?
2. is there any Camel module in Play ?
3. I raised a
Hi All,
We are using camel to build a back end Rest API layer. The security is
handled by Spring Security. We don't have a dedicated authentication
provider and we piggy back on a back end rest service to do the
authentication.
I have my own authentication manager and Authentication provider
Hi
Just a heads up for Camel users that ApacheCon has a full day track
about Camel on the 2nd day of the conference.
I wrote a blog piece about this where you can find more details
http://www.davsclaus.com/2016/10/i-am-going-to-apachecon-eu-2016-all-day.html
On Wed, Oct 19, 2016 at 8:20 PM,
Hi,
I have a sftp route that runs ok for a while, but after a few days it
doesn't pick up any (new) files anymore.
When looking at the hawtio console, nothing was inflight and the route was
running.
Anybody experienced this behaviour ?
i'm using camel-2.15
My endpoint is:
Yes if you can see file content is actually loaded in
populateRequestParameters(), I think it's likely to be a bug. Please make sure
it's not just a file name, and update the description with what you found. If
you can attach a minimal reproducer project that would be better.
On 10/20/2016
I can add a description that parameter is read twice.
2016-10-20 13:34 GMT+03:00 Vova Shelgunov :
> *Tomohisa*, actually initially I posted a bug in Jira (
> https://issues.apache.org/jira/browse/CAMEL-10399), but Claus closed it,
> can I reopen it?
>
> 2016-10-20 10:49
*Tomohisa*, actually initially I posted a bug in Jira (
https://issues.apache.org/jira/browse/CAMEL-10399), but Claus closed it,
can I reopen it?
2016-10-20 10:49 GMT+03:00 Tomohisa Igarashi :
> Hmm that smells like a bug in DefaultHttpBinding.populateRequestParameters(),
Hi all,
I have a external reference XML and would like to map the exchange content
by referring the XML.
Can you please let me know what is the better way to implement it.
I am using Apache camel 2.10 .
--
View this message in context:
Hi,
I am trying to use CamelHttpUri instead of
setting CamelHttpUri header with the below url:
https4://xxx.xxx.xx/-
${property[redeem_uri]}
application/json
application/vnd.api+json
java.lang.Exception
Note: when i am removing
I should also point out that I"m using Keep-Alive in my http client
would putting "close" in the Connection resolve this issue?
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-Bean-and-RedeliveryPolicy-tp5788975p5788979.html
Sent from the Camel - Users mailing list
Can someone let me know how to do guaranteed delivery using camel-redis?
My use case is something like below:-
from("jetty:http://localhost:/hello;).to("redis://...")
Once the message is written to redis send a success response to http
client, so that the client is not blocked waiting for
Hmm that smells like a bug in DefaultHttpBinding.populateRequestParameters(),
it shouldn't read a parameter value which is already handled in
populateAttachments(). Would you file a JIRA for it?
On 10/20/2016 03:18 PM, Vova Shelgunov wrote:
Hi,
I tried to debug populateRequestParameters in
Hi,
I tried to debug populateRequestParameters in DefaultHttpBinding and
noticed that request parameters contain file (with byte[] array value) that
I am sending to endpoint:
It is a reason why I have OOM error.
Let me note that I am sending file using google http client:
I attached
23 matches
Mail list logo