Good catch.
If you have not done so already can you please create a jira issue for this.
We love contributions
Thanks
Pontus
On Thu, 26 Jan 2017 at 19:12 Tim Dudgeon wrote:
> What I've found out so far is that the box library used by Camel is an old
> project.
>
> The one currently recommende
The current implementation of CamelHealthIndicator[1] only verifies that
the CamelContext is started not the state of the routes.
I guess a improvement could be to allow for a property that lists a number
of routes by routeId and add logic to also check the state of the routes to
decide the status
Wondering what the UP status on the /health end point in a camel spring boot
application indicates,
Ran the example in camel\examples\camel-example-spring-boot , looked at the
health check end point and it showed
{"status":"UP","camel":{"status":"UP","version":"2.18.1","contextStatus":"Started"},"d
thanks again Claus
yeah, I've already looked at that and unfortunately that's not it. bummer,
would've been an easy fix.
yes, I really do not need the lock because am the only one reading it. I
will give this a try.
I am upgrading also, I'll do this first, since I am using JBoss Fuse OSGI
con
What I've found out so far is that the box library used by Camel is an old
project.
The one currently recommended by box.com is this this GitHub project
https://github.com/box/box-java-sdk which has maven coordinates of
com.box:box-java-sdk:2.1.1
(https://search.maven.org/#search%7Cga%7C1%7Ca%3A%2
*Solution:*So I found the problem. The problem was with my
doTry...Catch...[endDoTry] block.Do not use the endDoTry closing method.
Just call end to end your try catch block. Can we some how add to the
docmentation to not use the endDoTry and/or explain what the endDoTry
does.Or can we remove th
To add some amplifying information, this behavior only shows up when using a
ProducerTemplate. If I use the netty4 component to a ".to()" Endpoint
everything works as expected.
*
I am not sure if its spring related, I used netty with tcp with the java dsl on
2.17 and that works. You could
I am not sure if its spring related, I used netty with tcp with the java
dsl on 2.17 and that works. You could log an issue as it is perhaps a bug?
On Thu, Jan 26, 2017 at 3:32 PM, Giordano, Michael [via Camel] <
ml-node+s465427n5793087...@n5.nabble.com> wrote:
> Yes except the error message chan
Yes except the error message changes to
Failed to resolve endpoint: tcp://10.18.2.161:6509 due to: No component found
with scheme: tcp
-Original Message-
From: souciance [mailto:souciance.eqdam.ras...@gmail.com]
Sent: Thursday, January 26, 2017 6:24 AM
To: users@camel.apache.org
Subjec
I would think by default it would move the file after route 3 has finished
successfully. You could probably change that using seda queues.
--
View this message in context:
http://camel.465427.n5.nabble.com/Exchange-is-complete-meaning-tp5790648p5793086.html
Sent from the Camel - Users mailing l
That is not possible as the property is a single entry, not a map structure.
Maybe you can just have multiple properties with the key name included
ftp.endpoint.foo=xxx
ftp.endpoint.bar=xxx
And then select it using the properties function from simple
toD("${properties:ftp.endpoint.${header.with
Hello,
in the properties file would be one entry (row) for each ftp server, ftp1,
ftp2...
The key is specified in a header. Now i would like to get the value of the
property using the header value as a key.
Somehow the properties entries got concatenated in the previous mail.
Kind regardsLaji
Its not super easy but you need to use a separator in your properties
file for the ftp servers
And then you can use the split method and grab the first array
Something a like
${headers.ftp.endpoint.split(";")[0]}
On Wed, Jan 25, 2017 at 9:18 AM, L F wrote:
> Hello camel users,
> I have a spri
You need to add a step after to mina, where you can work / log the response.
Or turn on DEBUG logging where mina may log a response.
On Tue, Jan 24, 2017 at 1:12 PM, santoshkeleti
wrote:
> Hi,
>
> I have a scenario that i need to send a request to TCP/IP port from camel
> and i need to read the
*Does it mean that it is complete when it has gone through route3?*
The reason why I am asking is because, when using the file consumer, the
file will be moved into the .camel folder when */the exchange has
completed/*. Does it mean that the file is moved when it has passed route1
or when it has pa
Yes there is the method call
setHeader "foo" method(MyBean.class, "doSomething")
On Tue, Jan 24, 2017 at 4:39 PM, buyleg wrote:
> Is it possible to manage the header with a bean instead of setHeader for each
> value?
> What I mean: Could you use replace the following:
> from("file://{{main.dir}}
I suggest to keep research the internet with that failure. And maybe
build a java app without the camel component to see if that box java
api works for you there, and compare with the camel box component.
If you find a bug / fix then we love contributions
http://camel.apache.org/contributing
For
Hi
Maybe you do some custom processing or something where you dont close
the file / input stream etc.
Also do you need the read lock at all? If you are the only one reading
those files you can then turn that off.
Also test with newer Camel versions
On Tue, Jan 24, 2017 at 9:38 PM, GaryLeeMills
Where do you see that? Or do you mean in general. I would imagine it means
that the exchange is no longer in transit? It has passed all the steps it
should without any errors.
On Thu, Jan 26, 2017 at 12:08 PM, sa_james [via Camel] <
ml-node+s465427n5793072...@n5.nabble.com> wrote:
> Still struggl
Hmm strange, do you get the same error if you switch from udp to tcp just
for the sake of it?
On Wed, Jan 25, 2017 at 11:20 PM, Giordano, Michael [via Camel] <
ml-node+s465427n5793064...@n5.nabble.com> wrote:
> I am running into an issue when I use the netty4 component with a
> ProducerTemplate.
Any thoughts on how to address this?
As the box route starts OK and I'm only getting this error when I trigger an
event on the box.com side it seems to me that the authentication is working
OK (but how can I be sure of this?).
I checked the version of the box java library being used and Camel seem
Still struggling a little bit with the meaning of "Exchange is complete".
Consider:
Route1: from("direct:A").to("direct:temp")
Route2: from("direct:temp").to("seda:temp")
Route3: from("seda:temp").to("mock:sink")
template.sendBody("direct:A", "message")
What does Exchange is complete mean?
T
22 matches
Mail list logo
