[jira] [Created] (CAMEL-7967) camel-rabbitmq logging exceptions as debug
Marco Crivellaro created CAMEL-7967: --- Summary: camel-rabbitmq logging exceptions as debug Key: CAMEL-7967 URL: https://issues.apache.org/jira/browse/CAMEL-7967 Project: Camel Issue Type: Bug Components: camel-rabbitmq Affects Versions: 2.14.0 Reporter: Marco Crivellaro 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 we usually set INFO as threshold. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-7057) Issue with password having double
Marco Crivellaro created CAMEL-7057: --- Summary: Issue with password having double Key: CAMEL-7057 URL: https://issues.apache.org/jira/browse/CAMEL-7057 Project: Camel Issue Type: Bug Affects Versions: 2.12.2 Reporter: Marco Crivellaro Priority: Minor 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 resolve endpoint: http://hostname/script.php?authMethod=BasicauthPassword=RAW(paword)authUsername=usr due to: Invalid uri syntax: Double marker found. Check the uri and remove the duplicate marker. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (CAMEL-6479) New FileExist option for File component: TryRename
Marco Crivellaro created CAMEL-6479: --- Summary: New FileExist option for File component: TryRename Key: CAMEL-6479 URL: https://issues.apache.org/jira/browse/CAMEL-6479 Project: Camel Issue Type: New Feature Components: camel-core Affects Versions: 2.11.0 Reporter: Marco Crivellaro Priority: Minor Fix For: 2.11.1, Future This patch introduces a new FileExist option for File component which works great when using on an FTP producer: the producer won't check if the file exists (sometime this is taking a long time) on the destination endpoint and simply rename it after the temporary file has been deployed. Most of FTP server implementation will overwrite the final file in case this already exists. Pull request created on GitHub: https://github.com/apache/camel/pull/24 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-5394) dinamic timeout for recipientList
Marco Crivellaro created CAMEL-5394: --- Summary: dinamic timeout for recipientList Key: CAMEL-5394 URL: https://issues.apache.org/jira/browse/CAMEL-5394 Project: Camel Issue Type: Improvement Components: camel-core Affects Versions: 2.9.2 Reporter: Marco Crivellaro Priority: Minor it would be great to have the possibility to define a dynamic timeout for recipientList in a similar way of aggretate -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
