Re: URI contains unsafe characters

Any idea? Thanks -- View this message in context: http://camel.465427.n5.nabble.com/URI-contains-unsafe-characters-tp5779497p5780919.html Sent from the Camel - Users mailing list archive at Nabble.com.

URI contains unsafe characters

Hi, when using the below URI Camel is logging a warning: ftp://user@host:21//?binary=false=true=false=true=Override=3=3=3=false=aPass=1000=3=false=RAW(${file:name.noext}.${in.header.x-feed_id}.tmp) Supplied URI '[truncated for readability]' contains unsafe characters, please

How to customized Log Format of DefaultErrorHandler

Hi, I am using Camel 2.15.3-SNAPSHOT How do I customise the Log Format of default error handler? I would like to output the endpoint uri, exchange id, error message and stack trace only thanks a lot, Marco -- View this message in context:

java.net.URISyntaxException using recipientList

Hi, I am trying to upgrade to Camel 2.15 from camel 2.8.6 and I am finding a problem when trying to serve endpoints which URIs contains the character { as a java.net.URISyntaxException is thrown. As an example a destination FTP endpoint contains the character '{' in the password; ie: '12{34'

Re: java.net.URISyntaxException using recipientList

Fastest fix ever! I don't see it yet in master or 2.15.x branch, was just wondering where the problem was. -- View this message in context: http://camel.465427.n5.nabble.com/java-net-URISyntaxException-using-recipientList-tp5769103p5769115.html Sent from the Camel - Users mailing list archive

Re: java.net.URISyntaxException using recipientList

Thanks for the feedback, much appreciated. -- View this message in context: http://camel.465427.n5.nabble.com/java-net-URISyntaxException-using-recipientList-tp5769103p5769126.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: HttpProducer to ignore response body avoiding stream caching

Should I take care of opening a JIRA issue to request the feature? Thanks -- View this message in context: http://camel.465427.n5.nabble.com/HttpProducer-to-ignore-response-body-avoiding-stream-caching-tp5767260p5768274.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: HttpProducer to ignore response body avoiding stream caching

yes that's exactly what I'd need. Should I open a JIRA issue? Best, Marco -- View this message in context: http://camel.465427.n5.nabble.com/HttpProducer-to-ignore-response-body-avoiding-stream-caching-tp5767260p5767416.html Sent from the Camel - Users mailing list archive at Nabble.com.

camel HttpProducer caching stream

Hi, I just found out HttpProducer (camel-http) is always caching the response stream, having a look a the Camel Stream Caching documentation (http://camel.apache.org/stream-caching.html) I would expected this to not occur since on camel 2.x Stream Caching is off by default. I would think it worth

HttpProducer to ignore response body avoiding stream caching

I am using camel-http to send HTTP Post notifications to a wide range of endpoints which I don't control directly, sometimes the endpoints response is quite big and due to the fact HttpProducer is caching the response stream temporary files are being written to disk. I can set the caching

Re: request-reply with ActiveMQ and Camel

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

Re: camel-rabbitmq logging exceptions as debug

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.

camel-rabbitmq logging exceptions as debug

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

Re: loggingErrorHandler formatting

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:

loggingErrorHandler formatting

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:

Re: Issue with password having double

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.

Re: issue with ExchangeHelper.resolveEndpoint when using RAW() parameter on authPassword

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

Issue with password having double

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=BasicauthPassword=RAW(paword)authUsername=usr throws the exception: org.apache.camel.ResolveEndpointFailedException: Failed to

issue with ExchangeHelper.resolveEndpoint when using RAW() parameter on authPassword

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,

Re: issue with ExchangeHelper.resolveEndpoint when using RAW() parameter on authPassword

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.

Re: issue with ExchangeHelper.resolveEndpoint when using RAW() parameter on authPassword

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

Re: ActiveMQ composite destination producer

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

ActiveMQ composite destination producer

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: to

bean String parameter binding

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: to uri=bean:theHeaderUtil?method=SetMissingHeaderToZero(*, 'XHeader1') / method signature is: SetMissingHeaderToZero(Exchange exchange, String

Re: camel-sql, connection test required?

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.

camel-sql, connection test required?

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

Re: camel-sql, connection test required?

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: bean id=mysqlPooled

JMS properties to In message headers

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

Re: Ignore JMSReplyTo

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.

Ignore JMSReplyTo

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

Re: camel processor in InOut to send 2 replies

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:

camel processor in InOut to send 2 replies

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: camelContext id=hulkcontext xmlns=http://camel.apache.org/schema/spring; autoStartup=true route from uri=jms:queue:data/

camel shutsdown route even when using failover

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

Re: camel shutsdown route even when using failover

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 =

Re: camel shutsdown route even when using failover

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);

Re: little issue with ActiveMQ Consumer having prefetch set to 0 (polling)

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

little issue with ActiveMQ Consumer having prefetch set to 0 (polling)

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

Re: Issues with URI containing %40 or %26

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:

Re: Issues with URI containing %40 or %26

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:

Re: Issues with URI containing %40 or %26

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=tst -- View this message in context:

Re: Issues with URI containing %40 or %26

% 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:

Re: Issues with URI containing %40 or %26

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:

stop a quartz route

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:

Re: recipientList with parallelProcessing, how to stop thread(s)

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:

recipientList with parallelProcessing, how to stop thread(s)

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

Re: URISupport.normalizeUri different result from camel 2.8.2 to 2.10.0

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:

Re: URISupport.normalizeUri different result from camel 2.8.2 to 2.10.0

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 the

Re: URISupport.normalizeUri different result from camel 2.8.2 to 2.10.0

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:

Re: URISupport.normalizeUri different result from camel 2.8.2 to 2.10.0

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

Re: URISupport.normalizeUri different result from camel 2.8.2 to 2.10.0

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 uris

Re: URISupport.normalizeUri different result from camel 2.8.2 to 2.10.0

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:

URISupport.normalizeUri different result from camel 2.8.2 to 2.10.0

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

Aggregator Exchange.MULTICAST_COMPLETE recipientList

Hi, I am currently using a recipientList with parallel processing and streaming option with a custom aggregator strategy. Exchange.MULTICAST_COMPLETE property read on aggregation seems to rely on the recipient list order instead of the order in which they are aggregated. For instance if in

recipientList, aggregationStrategy and completionTimeout

Hi all, I am re-factoring a component which makes use of Camel (just moved to camel 2.9.2), a part of the route is currently built as: .recipientList(header(recipientListHeader).tokenize(,)) .parallelProcessing().timeout(aggregationTimeout) .executorService(customThreadPoolExecutor)

Re: recipientList, aggregationStrategy and completionTimeout

Is there a chance dinamic timeout can be added in a future version? I suppose it can be done provided the fact it is avaliable in aggregation. Is there a way to make use of completionTimeout of the aggregation strategy? -- View this message in context:

information about the inflight exchange(s) when shutting down

Is there any way to collect some information (exhange.properties / headers) of any inflight exchange while shutting down camel context? I'd need this in order to track down an issue I have with a camel based application. I am using camel 2.8.0 -- View this message in context:

Re: information about the inflight exchange(s) when shutting down

Claus Ibsen-2 wrote: The default in flight registry only stores number of in flights. You can implement a custom in flight registry and include more details. Is there a reference in the documentation on how to create a custom inflight repository? Claus Ibsen-2 wrote: We wanted a light

RecipientList-AggregateTask thread creation

I have a route with a recipientList parallel processed and than streamed to an aggregation strategy: .recipientList(header(recipientListHeader).tokenize(,)) .parallelProcessing().timeout(3) .executorService(customThreadPoolExecutor) .streaming().aggregationStrategy(new

how to try delivery again after a recipientlist timeout

Hi all! I would like to ask you which would be the best way of attempting a redelivery after a recipient list timeout. I currently have a route which receives a message from JMS with a list of recipients and through a processor it changes the payload of the message and builds the recipientlist

GenericFileOperations optimization

Hi, when using camel as FTP/SFTP producer the exchange process is taking longer time when many files are stored in the destination folder. This should be related to the operations.existsFile calls being processed by the method. At the moment GenericFileProducer.processExchange is calling twice

Re: GenericFileOperations optimization

Thank you, what about the second point about lock? -- View this message in context: http://camel.465427.n5.nabble.com/GenericFileOperations-optimization-tp4315363p4315567.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: missing region property in aws-sns component

You have to create an AmazonSNSClient and specify the endpoint otherwise it will default to us-east-1 AWSCredentials awsCredentials = new BasicAWSCredentials(***, !!!); AmazonSNSClient client = new AmazonSNSClient(awsCredentials); client.setEndpoint(http://sns.eu-west-1.amazonaws.com/;);

Re: Exchange.MAXIMUM_CACHE_POOL_SIZE is not affecting producers created by recipientList

Excellent! That is something I was looking for since Camel 2.5! -- View this message in context: http://camel.465427.n5.nabble.com/Exchange-MAXIMUM-CACHE-POOL-SIZE-is-not-affecting-producers-created-by-recipientList-tp4257273p4279856.html Sent from the Camel - Users mailing list archive at

getCurrentCacheSize when using recipientList

Is there a way to get the current cache size when using a recipientList? in my route I am consuming messages from an ActiveMQ queue and then sending to recipients using the recipientList. -- View this message in context:

Re: getCurrentCacheSize when using recipientList

reason why I am asking is because I've tried to set it to a low value (say 50) and then send several messages to a list of 100 unique recipents (3 recipient for each exchange). I than took a snapshot with jmap and found all 100 producers -- View this message in context:

Re: Exchange.MAXIMUM_CACHE_POOL_SIZE is not affecting producers created by recipientList

Thank you, I will check it using the example provided. -- View this message in context: http://camel.465427.n5.nabble.com/Exchange-MAXIMUM-CACHE-POOL-SIZE-is-not-affecting-producers-created-by-recipientList-tp4257273p4275924.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: java.util.concurrent.RejectedExecutionException using interceptSendToEndpoint

Hi Claus, I've seen you closed the ticket and added a unit test. The unit test uses mock up endpoint which does not show the wrong behaviour. The test I've attached to the ticket does not make use of custom thread pool as you've reported:

Exchange.MAXIMUM_CACHE_POOL_SIZE is not affecting producers created by recipientList

Camel 2.7.0-SNAPSHOT I've tried to set the maximum producer cache size to 5 and send messages to 100 of different ftp endpoints (using several recipientList exchanges), checking the jmap heap dump I've found out there were 100 FTPClient, FTPConfigurations, FTPOperations ... loaded in memory. Is

Re: java.util.concurrent.RejectedExecutionException using interceptSendToEndpoint

I've created a ticket and attached a test to it https://issues.apache.org/jira/browse/CAMEL-3795 please let me know if you need further details. -- View this message in context:

Re: java.util.concurrent.RejectedExecutionException using interceptSendToEndpoint

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:

Re: java.util.concurrent.RejectedExecutionException using interceptSendToEndpoint

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

java.util.concurrent.RejectedExecutionException using interceptSendToEndpoint

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

Re: ActiveMQ connection with failover and prefetch

This is the URI format to use: failover:(tcp://localhost:61616?wireFormat.maxInactivityDuration=0keepAlive=true)?jms.prefetchPolicy.queuePrefetch=1initialReconnectDelay=1useExponentialBackOff=falsemaxReconnectAttempts=0randomize=false more details can be found here:

Re: camel caching producers

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

camel caching producers

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:

Re: camel caching producers

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.

Re: issue with sftp producer

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.

Re: camel caching producers

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

Re: camel caching producers

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:

Re: camel caching producers

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

Re: camel caching producers

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

Re: ActiveMQ connection with failover and prefetch

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=0jms.prefetchPolicy.queuePrefetch=1initialReconnectDelay=10maxReconnectDelay=15000 producer -Dsubject=test the only

Re: ActiveMQ connection with failover and prefetch

I've tried the same using a local instance: ant -Durl=failover://tcp://localhost:61616?wireFormat.maxInactivityDuration=0jms.prefetchPolicy.queuePrefetch=1initialReconnectDelay=10maxReconnectDelay=15000 producer -Dsubject=test same result: producer doesn't start -- View this message in context:

Re: ActiveMQ connection with failover and prefetch

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

issue with sftp producer

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

Re: issue with sftp producer

I am using Camel 2.7 SNAPSHOT with jsch 0.1.44 the endpoint URI is as follow: sftp://user@hostname:22?disconnect=trueeagerDeleteTargetFile=false%3Bstepwise%3DfalsefileName=SYSTEM01password=**soTimeout=3tempFileName=%24%7Bfile%3Aname.noext%7D.8937937.tmp stack trace: [2011-03-03

Re: issue with sftp producer

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.

Re: issue with sftp producer

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.

Re: ActiveMQ connection with failover and prefetch

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

Re: ActiveMQ connection with failover and prefetch

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 -

Re: ActiveMQ connection with failover and prefetch

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

ActiveMQ connection with failover and prefetch

Following ActiveMQ connection string should be valid but Camel fails connecting to the broker (hangs forever): failover:(tcp://SOMEHOST:61616?wireFormat.maxInactivityDuration=0jms.prefetchPolicy.queuePrefetch=1)?initialReconnectDelay=10maxReconnectDelay=15000 it works fine specifying

Re: Memory leak in camel mail component

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

Re: Memory leak in camel mail component

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:

Re: Memory leak in camel mail component

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

Re: Memory leak in camel mail component

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

Re: Memory leak in camel mail component

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

Re: FTP creating connections for every file name in the uri

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

Re: FTP creating connections for every file name in the uri

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:

Re: FTP creating connections for every file name in the uri

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:

  1   2   >