Hi all,
we have a route which is delivering of a given message to a list of
endpoints (HTTP, MAIL, FTP...)
to achieve this we are using a recipentList (the endpoint list is dinamic).
In order to process all deliveries in parallel we are using
parallelProcessing
once the delivery to a given endpoi
Looking forward to give it a try!
--
View this message in context:
http://camel.465427.n5.nabble.com/recipientList-parallelProcessing-aggregationStrategy-tp2255971p2256665.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I am a subscriber now.
--
View this message in context:
http://camel.465427.n5.nabble.com/recipientList-aggregationStrategy-timeout-tp2262831p2262903.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi all,
we have a route which is delivering of a given message to a list of
endpoints (HTTP, MAIL, FTP, JMS)
to achieve this we are using a recipentList (the endpoint list is dinamic)
once the delivery to a given endpoint is processed we need to update a
delivery trail through a web service, to
Hello,
I am using camel 2.4
trying to deliver to an FTP endpoint with following parameters
eagerDeleteTargetFile=false
fileName=srml-5-2009-results.xml
ftpClient.connectTimeout=12
ftpClient.dataTimeout=15000
ftpClient.defaultTimeout=15000
password=
soTimeout=6
tempFileName=%24%7Bfile%
This might help investigating the issue.
The route has a retryUntil; the first time we try to connect to the endpoint
it takes a long time (much more than the specified timeout), the other
attempts seems to run in timeout the specified millisecs.
Maybe this is related to a new endpoint?
The erro
I've noticed you introduced a new timeout for recipientList aggregation,
I can't find a way of adding it to my route:
from("jms-cif:queue:" + _notificationQueue).process(processor)
I am using 2.5-SNAPSHOT I've updated my local repo this morning
timeout seems to have a problem even on your Unit test route:
from("direct:start")
.recipientList(header("slip")).aggregationStrategy(
new AggregationStrategy() {
publi
sorry this was my fault, I don't know why but it was recognize by multicast
processor and not recipentlist,
now it is working fine.
my route has a retry bean, is there a way to cancel retrying in case the
aggregation runs in timeout?
currenlty in case it runs in timeout my route hits the end but
the problem I see right now is that in case aggregation runs in timeout the
endpoint processing thread is not aborted, I am not sure on how to demo as
unit test such a thing
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-2-5-recipientList-aggregationStrategy-timeout-tp2
This is the route I am currently using:
from("jms-cif:queue:" + _notificationQueue).process(processor)
.onException(Exception.class).retryWhile(bean("myRetryBean")).end()
.recipientList(header("recipientLis
I've tried current snapshot; the timeout is working as expected, although the
task doesn't get cancelled.
I receive messages from running thread (connection timeout to an FTP) after
the timeout is raised (many seconds afterwards).
you can try this behaviour by seding and FTP exchange to an IP whi
That is exactly what I am experiencing (sorry for the late reply).
If an FTP endpoint is not reliable I am not receiving a connection timeout
even though I've set it to 10 secs or less; the timeout is raised after
several minutes (even 60mins)... in such a case the recipient list runs in
timeout i
I am still receiving the FTP connection timeout error after a while the
aggregation is runned in timeout.
I still don't understand why it runs in connection timeout after the
specified timeout though (I've already opened a discussion for this).
2010-08-09 09:02:36,221 [pool-1-thread-2] DEBUG
org.
Hello, is there a way to access the exchange properties within the timeout
callback of TimeoutAwareAggregationStrategy associated to a recipientList?
I can use the oldExchange parameter but if the all the endpoints defined in
the recipienList runs in timeout this value is set to null.
--
View
Is there a chance you change the way FTP connections are created?
In the case you are producing many files for always the same FTP endpoint
you are forced to set the disconnect=true which is leading to client
application to "connect, deploy, disconnect" each time which is not ideal.
--
View this
Do you prefer me opening a new conversation/ticket?
--
View this message in context:
http://camel.465427.n5.nabble.com/FTP-creating-connections-for-every-file-name-in-the-uri-tp478938p2856347.html
Sent from the Camel - Users mailing list archive at Nabble.com.
When the route is used to deliver several files (fileName option) via FTP a
new connection to the given FTP server is created for each file and left
opened unless we set the disconnect option to true.
In my honest opinion this is leading to a lot of time being spent to connect
and disconnect each
24
To: users@camel.apache.org
Subject: Re: FTP creating connections for every file name in the uri
On Tue, Sep 28, 2010 at 12:06 PM, Marco Crivellaro
wrote:
>
> When the route is used to deliver several files (fileName option) via
> FTP a new connection to the given FTP server is created
As I am using a recipientList and it might happen not all the endpoints will
receive the content with the same filename do you think I can use an
interceptor interceptSendToEndpoint and remove the filename option from URI
setting the filename in the header? Or is at this time the endpoint already
Using interceptSendToEndpoint I've tried setting the header
Exchange.INTERCEPTED_ENDPOINT
to the new endpoint URI (without the fileName) and setting the filename as
Exchange.FILE_NAME.
However the enpoint parameters being used remain the original one.
this is the my interceptSendToEndpoint:
i
Thanks I'll try in that way!
can you link me to the ticket you created about the fix at FTP component
level?
just want to keep an eye on it looking forward for the enhancement to come
--
View this message in context:
http://camel.465427.n5.nabble.com/FTP-creating-connections-for-every-file-name
Hi All,
I am working together with Sri in a project which makes an extensive use of
camel (you've seen some posts from me in the past).
I can confirm the number of endpoints being created grows constantly using
any protocol,
with our system we are serving a very high number of endpoints and at the
Our system is built on top of the recipientList component and camel
components URI parameters, we are using FTP, JMS, email and HTTP
therefore we'd need a way to 'cleanup' the list of allocated endpoints,
can't you provide a way of forcing endpoints list cleanup or perhaps
customizing the maximum
I've just used jConsole to analyze our application after running it through
the weekend, many endpoints URI have been served and all of them have been
cached. It appears it is not caching 1000 endpoints at most.
--
View this message in context:
http://camel.465427.n5.nabble.com/Memory-leak-in-ca
Yes I am viewing JMX, sorry.
but mail recipients or ftp parameters in URI won't allow us to make use of
the recipientList which is very handy and it is on the basis of our
application (we are serving a very high number of endpoints dynamically
using the recipientList).
--
View this message in c
Thank you for your reply,
I can see a lot of org.apache.camel endpoints, I guess these are related to
the fact we are sending a huge number of file having a unique file name and
having the fileName option in the URI is making unique all those endpoints
even though FTP server is always the same (
my list of recipients might contain several endpoints which does not
necessarily make use of the same fileName for the current message so adding
a processor/bean before the recipientList won't work (file name header
should be unique for each endpoint).
would it be feasibel to add an interceptSend
Following ActiveMQ connection string should be valid but Camel fails
connecting to the broker (hangs forever):
failover:(tcp://SOMEHOST:61616?wireFormat.maxInactivityDuration=0&jms.prefetchPolicy.queuePrefetch=1)?initialReconnectDelay=10&maxReconnectDelay=15000
it works fine specifying jms.prefe
Thank you I'll give it a try and let you know...
without prefetch option it works so I thought it was correct to use that URI
format
--
View this message in context:
http://camel.465427.n5.nabble.com/ActiveMQ-connection-with-failover-and-prefetch-tp3387737p3394410.html
Sent from the Camel - Use
I've tried to use the URI format you suggested but the result is the same
using the URI I posted
--
View this message in context:
http://camel.465427.n5.nabble.com/ActiveMQ-connection-with-failover-and-prefetch-tp3387737p3394630.html
Sent from the Camel - Users mailing list archive at Nabble.com
As the connection string you suggested is not working should I consider this
a Camel or an ActiveMQ issue?
--
View this message in context:
http://camel.465427.n5.nabble.com/ActiveMQ-connection-with-failover-and-prefetch-tp3387737p3406724.html
Sent from the Camel - Users mailing list archive at N
Hi,
I am experiencing an issue with and sftp producer, I am not sure if this
should be considered a camel or a JCraft JSCH libray issue.
The exchange run in exception when it comes to list check if file exists on
destination org.apache.camel.component.file.remote.SftpOperations.existsFile
I've fo
I am using Camel 2.7 SNAPSHOT with jsch 0.1.44
the endpoint URI is as follow:
sftp://user@hostname:22?disconnect=true&eagerDeleteTargetFile=false%3Bstepwise%3Dfalse&fileName=SYSTEM01&password=**&soTimeout=3&tempFileName=%24%7Bfile%3Aname.noext%7D.8937937.tmp
stack trace:
[2011-03-03 14:
I can work on a patch, have two proposal as solution:
solution 1: in case directory information on filename cannot be retrieved
uses "/"
solution 2: in case directory information on filename cannot be retrieved
uses current directory (there should be a way to retrieve it)
I'd prefer the latter.
I've forgot to the JIRA ticket link:
https://issues.apache.org/jira/browse/CAMEL-3749
--
View this message in context:
http://camel.465427.n5.nabble.com/issue-with-sftp-producer-tp3408052p3408268.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I've tried to run the example you suggested and the producer hangs (same
issue shown by camel)
ant
-Durl="failover://tcp://hostname:61616?wireFormat.maxInactivityDuration=0&jms.prefetchPolicy.queuePrefetch=1&initialReconnectDelay=10&maxReconnectDelay=15000"
producer -Dsubject="test"
the only dif
I've tried the same using a local instance:
ant
-Durl="failover://tcp://localhost:61616?wireFormat.maxInactivityDuration=0&jms.prefetchPolicy.queuePrefetch=1&initialReconnectDelay=10&maxReconnectDelay=15000"
producer -Dsubject="test"
same result: producer doesn't start
--
View this message in co
doesn't work... it is the first URL format I've used.
--
View this message in context:
http://camel.465427.n5.nabble.com/ActiveMQ-connection-with-failover-and-prefetch-tp3387737p3409686.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I've created a new discussion on ActiveMQ forum.
http://activemq.2283324.n4.nabble.com/ActiveMQ-connection-with-failover-and-prefetch-td3335495.html
--
View this message in context:
http://camel.465427.n5.nabble.com/ActiveMQ-connection-with-failover-and-prefetch-tp3387737p3409712.html
Sent from
Hi all,
having a look the to memory usage of my camel based application; I've found
out camel is caching producers.
I am running a huge amount of deliveries to distinct endpoints, is there a
way to limit the amount of producers cached?
--
View this message in context:
http://camel.465427.n5.nabbl
thanks a lot!
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-caching-producers-tp3412417p3412449.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I've tested latest snapshot, everything works like a charm!
Camel rocks!
--
View this message in context:
http://camel.465427.n5.nabble.com/issue-with-sftp-producer-tp3408052p3412452.html
Sent from the Camel - Users mailing list archive at Nabble.com.
even setting cache limit to 10 and disabling camel JMX support
(-Dorg.apache.camel.jmx.disabled=true)
I can see the number of FTPClient, FTPConfiguration, FTPOperations,
FTPEndpoint and ListenerList growing constantly.
Each exchange I run has a distinct endpoint URI
--
View this message in contex
that means that if I need to deliver to 1000 distinct ftp servers I should
expect space to be allocated even if they are used just once? Isn't there a
way to get the garbage collected?
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-caching-producers-tp3412417p3412643.htm
problem is I am using a recipientList to serve our endpoints as we are not
serving only FTP endpoints.
any way to limit LRU cache?
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-caching-producers-tp3412417p3412665.html
Sent from the Camel - Users mailing list archive at
thanks,
the temporary file name we use is also dinamic, which is the Exchange header
to set the tempFileName uri property?
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-caching-producers-tp3412417p3412698.html
Sent from the Camel - Users mailing list archive at Nabble.c
thank you.
Is there any way I can access the list of producers and stop them at the end
of the route?
In such a way I will ensure I won't risk a high memory consumption if the
route will server thousands of distinct ftp servers (which could be the case
in the future)
--
View this message in conte
Hi,
I've just bumped into an issue with ExchangeHelper.resolveEndpoint when
used on a URI which has authPassword parameter value using RAW() value
ExchangeHelper.resolveEndpoint(exch,
"http://host:80/script.php?httpClient.soTimeout=360&authMethod=Basic&authPassword=RAW(pass!)&authUsername=us
I have forgotten to mention I am using camel 2.12.1
--
View this message in context:
http://camel.465427.n5.nabble.com/issue-with-ExchangeHelper-resolveEndpoint-when-using-RAW-parameter-on-authPassword-tp5744246p5744247.html
Sent from the Camel - Users mailing list archive at Nabble.com.
why does it work in a different way between authPassword on HTTP and password
on FTP endpoint parameters?
--
View this message in context:
http://camel.465427.n5.nabble.com/issue-with-ExchangeHelper-resolveEndpoint-when-using-RAW-parameter-on-authPassword-tp5744246p5744268.html
Sent from the Ca
my bad, it is the same for FTP.
I got confused by another issue I've found... will open a separate thread
--
View this message in context:
http://camel.465427.n5.nabble.com/issue-with-ExchangeHelper-resolveEndpoint-when-using-RAW-parameter-on-authPassword-tp5744246p5744320.html
Sent from the Ca
Hi,
there is an issue with handling password with double && even when wrapping
it into RAW() constraint
For instance the use of URI
http://hostname/script.php?authMethod=Basic&authPassword=RAW(pa&&word)&authUsername=usr
throws the exception:
org.apache.camel.ResolveEndpointFailedException: Fail
created https://issues.apache.org/jira/browse/CAMEL-7057
--
View this message in context:
http://camel.465427.n5.nabble.com/Issue-with-password-having-double-tp5744323p5744570.html
Sent from the Camel - Users mailing list archive at Nabble.com.
how do I define the log format when using loggingErrorHandler?
I am interested in setting properties like: showExchangeId,
showExchangePattern, showBody... the default format is too verbose
--
View this message in context:
http://camel.465427.n5.nabble.com/loggingErrorHandler-formatting-tp57446
I have tried the suggested approach but it doesn't seem to work like having a
DefaultErrorHandler; in my route there is an aggregator and once an exchange
runs in error the routing does not proceed to the step after the aggregation
if this runs in timeout.
--
View this message in context:
http:
Hi,
I am using Camel 2.14.0
Connecting to RabbitMQ using camel-rabbitmq I've noticed that no ERROR is
logged if the component cannot connect, the exceptions are handled and
logged as DEBUG.
This is a bit inconvenient as logging all DEBUG messages for the component
fills up our logs, in production w
opened https://issues.apache.org/jira/browse/CAMEL-7967
thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-rabbitmq-logging-exceptions-as-debug-tp5757936p5758069.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
I have managed to get a simple request-reply working with ActiveMQ and
Camel/NMS.
- The Producer is an NMS client which creates a temporary queue and then
sends the request to a queue (queue.request) setting the replyTo header to
the temporary queue.
- The Consumer is a Java component which use
Thanks for the replies
Camel is only used to consume the request queue and post the replies, the
requestor is a .NET app based on NMS and the aggregation part works fine as
the setup works fine when using a standard queue on JMSReplyTo header: camel
is sending the multiple replies to the queue and
Hi,
I have a very simple route where messages are sent to an ActiveMQ queue with
JMSReplyTo header set which I would like to ignore. I cannot avoid setting
the header as messages are pushed using composite destination by another
component.
I've set the route as following but the messages are still
That worked, thanks a lot!
--
View this message in context:
http://camel.465427.n5.nabble.com/Ignore-JMSReplyTo-tp5729973p5730015.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi all,
I am using Camel 2.11.1
By default Camel adds the a list of JMS properties to the In message headers
when it receives a JMS message, for instance: JMSTimestamp, JMSType,
JMSXGroupID...
is there a way to extend this list without having to create a Processor to
the route?
I would like to a
Hi all,
when using camel-sql should connection pooling and connection test be
implemented?
I am building a camel based application which will run as a daemon and might
write the database once every few days. This means between writes the
connection to the database (mysql) might timeout. Is camel te
I've found out you can use c3p0 library
(http://www.mchange.com/projects/c3p0) so you can rely on connection pooling
are not forced to write your own connection testing in the route.
here is an example of the jdbc datasource bean:
Thanks for pointing that out, I'll have a look at it.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-sql-connection-test-required-tp5736549p5736624.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi All,
I am using Camel 2.11.2 with a spring context.
In my route I am calling a bean method passing 2 wildcard params and a
string.
for example:
method signature is:
SetMissingHeaderToZero(Exchange exchange, String headersCSV)
everything works fine but camel is writing following WARN:
WARN
Hi,
works fine on 2.12-SNAPSHOT, I can't fetch some dependencies to test it on
2.11.2-SNAPSHOT
I reported I was using 2.11.2 by mistake, the issue is shown on 2.11.1
Thanks,
Marco
--
View this message in context:
http://camel.465427.n5.nabble.com/bean-String-parameter-binding-tp5736688p57366
Hi All,
I have a requirement to send the same message to 2 distinct destinations (a
queue and a topic) on ActiveMQ and I would like to use the composite
destination feature of ActiveMQ.
http://activemq.apache.org/composite-destinations.html
I've tried to setup the producer URI as follow:
the m
Thanks
The example I reported though is properly pushing 2 messages on the broker
though. So it seems to work but not supporting a mix of topic and queue in
the list.
correct me if I am wrong but using multicast is not exactly the same thing
of using composite destinations,
if I've understood it
Hi all,
I am migrating my application from Camel 2.8.2 to Camel 2.10.0 and found
following issue:
when normalizing a uri with URISupport.normalizeUri which contains %26 in
one of its parameters the entity is transformed to '&' and essentially lost
from the parameter value; this was not happening w
can you please let me know if this is how it should work and therefore camel
2.8.2 was buggy?
I just need to know if I have to find a workaround until a bugfix is release
or instead I am implementing it in the wrong way.
Thank you.
--
View this message in context:
http://camel.465427.n5.nabble
thank you Henryk.
I saw you planned to fix it for Camel 2.11.0; is there a chance to have in
2.10 too since it is a major bug?
Marco
--
View this message in context:
http://camel.465427.n5.nabble.com/URISupport-normalizeUri-different-result-from-camel-2-8-2-to-2-10-0-tp5716633p5716870.html
Sen
hekonsek wrote
>
> Ok. The good news is that I got a workaround for you :) .
>
> Create the component without the FTP password defined in the
> parameters and then programatically set it on the endpoint.
>
I wish it was this easy... unfortunately our architecture is build around
the endpoint u
hadrian wrote
>
> Would using properties be acceptable as a solution (including
> camel-jasypt maybe if you don't want the pwd in clear)?
>
> Hadrian
>
No sure what you mean, would it be possible for you to provide an example?
--
View this message in context:
http://camel.465427.n5.nabbl
hadrian wrote
>
> Would using properties be acceptable as a solution (including
> camel-jasypt maybe if you don't want the pwd in clear)?
>
> Hadrian
>
Hi Hadrian,
unfortunately I can't use properties without re engineering the whole
application. we manage hundreds of endpoints centrally and
Unfortunately interceptors cannot be used. We use a recipientList in our
route and password cannot be set in a header like filename... really need
this to be fixed.
--
View this message in context:
http://camel.465427.n5.nabble.com/URISupport-normalizeUri-different-result-from-camel-2-8-2-to-2-
Hi All,
in our route we are using a recipientList with parallelProcessing which is
than aggregated.
We also use an aggregation timeout.
When the aggregation runs in timeout the threads which have been created to
process in parallel the recipient list will continue running. Is there a way
to list th
Thank you,
in the meantime I've worked it around by using an InflightRepository keeping
track of exchange alive time, but it would be great to have a way to
graceful stop running tasks.
--
View this message in context:
http://camel.465427.n5.nabble.com/recipientList-with-parallelProcessing-how-
Hi All,
my Camel context is making use of a watchdog to monitor the status of the
application. In case a flag is set I would like to stop the watchdog, I
cannot find a way to stop the route.
The watchdog have been implemented using camel-quartz:
from("quartz://watchdog/checkpendingexchanges?trigge
Hi all,
using camel 2.8.0 it was possible to have endpoint uris containing %26 (&)
or %40 (@) encoded values.
This is essential if you want to support credentials such as username 'us@r'
or password 't&st'.
Many of the endpoints we are serving makes use of @ or & in their
parameters.
We've recentl
Claus Ibsen-2 wrote
>
> Give 2.10.1 a try
>
2.10.1 have issues as well
valid uri: ftp://us%40r@host?password=t%26st
is normalized to invalid uri: ftp://us@r@host?password=t&st
--
View this message in context:
http://camel.465427.n5.nabble.com/Issues-with-URI-containing-40-or-26-tp5719118p5
% is encoded as %25
calling URISupport.normalizeURI on
ftp://us%2540r@host?password=t%2526st
returns following URI which doesn't seem correct either:
ftp://us%40r@host?password=t%2526st
it seems URI parameters are not being decoded.. I would expect following
result:
ftp://us%40r@host?password=t
in which version have this behaviour been introduced? I'd prefer to use an
older version which supports %40 and %26 in URI until this is URISupport is
fixed. Would 2.9.x be ok?
--
View this message in context:
http://camel.465427.n5.nabble.com/Issues-with-URI-containing-40-or-26-tp5719118p57191
Thanks for letting me know.
The ticket doesn't have any target milestone, is there a short term plan to
work on this issue?
Othewise I suppose the only way out for me would be to roll back to last
2.8.x...
--
View this message in context:
http://camel.465427.n5.nabble.com/Issues-with-URI-contai
I took the decision to go back to camel 2.8 (2.8.6) as all our endpoints had
user in the authority part.
I am looking forward for a fix on camel 2.10 (or 2.11 even) since camel is
too cool to stay behind... :)
--
View this message in context:
http://camel.465427.n5.nabble.com/Issues-with-URI-co
Hi All,
I am looking into a small issue I am facing when using ActiveMQ consumer
(Camel route, standalone application) configured to poll messages (ActiveMQ
connectionstring parameter jms.prefetchPolicy.queuePrefetch=0)
current setup involves 450 consumers which are restarted by a cron (not all
at
Hi all,
I just noticed an issue related to deleting the target file when writing
using temporary file names and eagerDeleteTargetFile is set to false.
the producer first checks if target file exists, it than writes the
temporary file. Once temporary file is written the target file is deleted in
ca
Any idea on how Client ID and Connection ID are created when connecting to
ActiveMQ?
--
View this message in context:
http://camel.465427.n5.nabble.com/little-issue-with-ActiveMQ-Consumer-having-prefetch-set-to-0-polling-tp5725050p5725391.html
Sent from the Camel - Users mailing list archive at
Hi All,
I am setting up a camel context with 2 routes consuming 2 ActiveMQ queues.
The connectionstring to the broker specifies failover protocol, however if
the broker for some reason goes offline the context shutsdown itself
automatically. Is there a way to keep the context trying to reconnect to
I've tried what you've suggested but the route will shutdown in in case the
broker connection is lost, in my previous test it looked like System.Runtime
was being called. This is how my main method looks like now:
public class MainHulk {
private static Logger LOG = LoggerFactory.getLogge
I manage to get it working, I think I was setting the context in the wrong
way.
This now works, camel context won't stop and wait for the broker to
reconnect using failover provided via config
public class MainHulk {
private static Logger LOG = LoggerFactory.getLogger(MainHulk.class);
Hi All,
I have a requirement to send 2 messages in as reply of a request using InOut
pattern.
How can I achieve this?
My route looks as following:
http://camel.apache.org/schema/spring"; autoStartup="true">
Hi Hadrian,
thanks for your reply. Sorry if I've been unclear.
The messages I am publishing to the In queue have JMSReplyTo header set.
As you suggested I've used the reply to header to send an additional
message using a bespoke producer in the process method of the Processor:
javax.jm
This is the URI format to use:
failover:(tcp://localhost:61616?wireFormat.maxInactivityDuration=0&keepAlive=true)?jms.prefetchPolicy.queuePrefetch=1&initialReconnectDelay=1&useExponentialBackOff=false&maxReconnectAttempts=0&randomize=false
more details can be found here:
http://activemq.22833
in some circumstances interceptSendToEndpoint in conjunction with
recipientList and parallel processing is running in exception. this seems to
be the case when and http endpoint is sent in the recipient list after
having processed and ftp in the previous exchange
attached test case shows the expec
That is not an heavy load sample, it runs in exception after the 2nd time it
runs the for cycle...
--
View this message in context:
http://camel.465427.n5.nabble.com/java-util-concurrent-RejectedExecutionException-using-interceptSendToEndpoint-tp3425179p3556257.html
Sent from the Camel - Users ma
Is there a way to access the list of camel producers and cleanup all
instances so that they can be collected by the garbage collector?
--
View this message in context:
http://camel.465427.n5.nabble.com/cleanup-camel-cached-producers-tp3708189p3708189.html
Sent from the Camel - Users mailing list
why isn't the route running in exception if instead of using an intercept
send to endpoint for all protocols I define 2 different inteceptors, 1 for
ftp and 1 for http?
--
View this message in context:
http://camel.465427.n5.nabble.com/java-util-concurrent-RejectedExecutionException-using-interce
to make it run in exception you don't even need to run a cycle of with many
messages sent, you just need to define an the interceptor for ftp and http:
interceptSendToEndpoint("(ftp|sftp|ftps|http):.*").process(
new Processor() {
public void process(Exchange exchange) throws Exception {
1 - 100 of 130 matches
Mail list logo
