Hi,
We have a Camel application which is running multiple FTP consumers to the same
server and it seems as if one transaction failing affects others, like Client A
sending GOODBYE kills Client B still running STOR (please see the attached log).
[2018-04-05
the second
connection as well.
Is this a race condition or do we need to make sure that concurrency isn't
possible at this level?
-Ursprüngliche Nachricht-
Von: Florian Posch [mailto:florian.po...@performgroup.com]
Gesendet: Mittwoch, 4. April 2018 16:36
An: users@camel.apache.org
Betreff
Hi.
We are using Camel 2.20.2 to transfer files to remote servers.
Our route is built like that - sorry that I can't provide a fully featured
application and all beans.
from("direct:chunk.process")
gt;> > VERY
>> easy
>> > to do and just use the producerTemplate to send thing to camel routes.
>> This
>> > is what I do.
>> >
>>
>> No camel-http-starter does not need any changes.
>> That link your provided is to some old ar
/camel-dependency-sample
I hope this helps.
Kind regards,
Florian
Florian Posch // Software Engineer
T -
RunningBall Sports Information GmbH
M -
Plabutscher Straße 63
F -
8051 Graz
E florian.po...@performgroup.com
Austria
Skype rb.fposch
W www.performgro
that might not get initialized properly
during startup.
There's a more detailed snippet given on my Stackoverflow post:
https://stackoverflow.com/questions/46680985/spring-boot-camel-autowiring-issues-in-camel-components
Any question, please let me know...
Kind regards,
Florian
Florian Posch
