[jira] [Commented] (CAMEL-11497) Migrate the rest of the Confluence content

2018-03-09 Thread JIRA

[ 
https://issues.apache.org/jira/browse/CAMEL-11497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393539#comment-16393539
 ] 

Önder Sezgin commented on CAMEL-11497:
--

There may be some other documents to migrate.. even though eips are done, it is 
better we keep this open, i guess

> Migrate the rest of the Confluence content
> --
>
> Key: CAMEL-11497
> URL: https://issues.apache.org/jira/browse/CAMEL-11497
> Project: Camel
>  Issue Type: Sub-task
>  Components: website
>Reporter: Zoran Regvart
>Assignee: Önder Sezgin
>Priority: Major
> Fix For: Future
>
>
> There are still pages in the Confluence that are not migrated to Asciidoctor



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-10837) Migrate EIP patterns to adoc

2018-03-09 Thread JIRA

[ 
https://issues.apache.org/jira/browse/CAMEL-10837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393535#comment-16393535
 ] 

Önder Sezgin commented on CAMEL-10837:
--

Maybe we can close this ticket :)

> Migrate EIP patterns to adoc
> 
>
> Key: CAMEL-10837
> URL: https://issues.apache.org/jira/browse/CAMEL-10837
> Project: Camel
>  Issue Type: Task
>  Components: camel-core
>Reporter: Sébastien COL
>Assignee: Claus Ibsen
>Priority: Minor
>  Labels: documentation
> Fix For: 2.21.0
>
>
> Task 1 of the Camel 2.19 Roadmap:
> Finish migrating the wiki documentation to adoc files. I think its
> most of the EIP patterns that are missing. There is a basic list of
> EIPs here: 
> https://github.com/apache/camel/blob/master/camel-core/readme-eip.adoc
> I create this issue so I can submit a PR of my ongoing work. Still working on 
> it but I wanted to check that what I do is what's expected.
> Regards,
> Sebastien



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-12337) camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found

2018-03-09 Thread abccbaandy (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-12337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393315#comment-16393315
 ] 

abccbaandy commented on CAMEL-12337:


Those exception I post in the Description is WARN in the logs, and I use 
autoCreate=false because I only have read permission.

btw I update my previous comment, hope it's enough to understand.

> camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found
> --
>
> Key: CAMEL-12337
> URL: https://issues.apache.org/jira/browse/CAMEL-12337
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-ftp, camel-sftp
>Affects Versions: 2.20.2
>Reporter: abccbaandy
>Priority: Minor
>
> I tried something like these code, but when "notexist" folder not exist, it 
> still give me exception
> {code:java}
> sftp://testserver:22/notexist?autoCreate=false=true
> {code}
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot 
> list directory: notexist
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: com.jcraft.jsch.SftpException: No such file
>   at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2873)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2225)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2242)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1592)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1553)
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:641)
>   ... 12 common frames omitted
> {code}
> ftp has the same issue.
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: File 
> operation failed: 550 The system cannot find the file specified. 
>  Cannot change directory to: notexist. Code: 550
>   at 
> org.apache.camel.component.file.remote.FtpOperations.doChangeDirectory(FtpOperations.java:790)
>   at 
> org.apache.camel.component.file.remote.FtpOperations.changeCurrentDirectory(FtpOperations.java:768)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.doPollDirectory(FtpConsumer.java:112)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.pollDirectory(FtpConsumer.java:83)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (CAMEL-12337) camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found

2018-03-09 Thread abccbaandy (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-12337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393152#comment-16393152
 ] 

abccbaandy edited comment on CAMEL-12337 at 3/9/18 6:15 PM:


yes and no.

In fact, I need a way to control the exception"s", especially file/directory 
not found.

In my case : there is a feature to poll files from a directory and process 
them, but the directory may not exist at first.

So, it's not error when directory not found in my case, but I still need to 
know if there is 0 file in the directory or the directory not exist.

for ex, my log should looks like :
[0:00] dir not exist
[0:10] dir not exist
[0:20] dir not exist
[0:30] dir not exist
[0:40] 0 files process  <= directory exist, but no file yet !!
[0:50] 2 files process
[1:00] 23 files process
...

Current "file not found" exception is too verbose to me, and I can't format it.
Because of that, my current log looks like :
[0:00] org.apache.camel.component.file.GenericFileOperationFailedException: 
Cannot list directory: notexist
at 
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
at 
org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
at 
org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
at 
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
at 
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
[0:10] org.apache.camel.component.file.GenericFileOperationFailedException: 
Cannot list directory: notexist
at 
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
at 
org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
at 
org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
at 
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
at 
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
[0:30] org.apache.camel.component.file.GenericFileOperationFailedException: 
Cannot list directory: notexist
at 
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
at 
org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
at 
org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
at 
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
at 
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
[0:40] 0 files process  <= directory exist, but no file yet !!
[0:50] 2 files process
[1:00] 23 files process


was (Author: abccbaandy):
yes and no.

In fact, I need a way to control the exception"s", especially file/directory 
not found.

In my case : there is a feature to poll files from a directory and process 
them, but the directory may not exist at first.

So, it's not error when directory not found, but I still need to know if there 
is 0 file in the directory or the directory not exist.

for ex, my log may looks like :
[0:00] dir not exist
[0:10] dir not exist
[0:20] dir not exist
[0:30] dir not exist
[0:40] 0 files process  <= directory exist, but no file yet !!
[0:50] 2 files process
[1:00] 23 files process
...

Current "file not found" exception is too verbose to me, and I can't format it.
Because of that, my current log looks like :
[0:00] org.apache.camel.component.file.GenericFileOperationFailedException: 
Cannot list directory: notexist
at 
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
at 
org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
at 
org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
at 
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
at 
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
[0:10] org.apache.camel.component.file.GenericFileOperationFailedException: 
Cannot list directory: notexist
at 
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
at 
org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
at 
org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
at 
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
at 
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
[0:30] org.apache.camel.component.file.GenericFileOperationFailedException: 
Cannot 

[jira] [Comment Edited] (CAMEL-12337) camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found

2018-03-09 Thread abccbaandy (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-12337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393152#comment-16393152
 ] 

abccbaandy edited comment on CAMEL-12337 at 3/9/18 6:14 PM:


yes and no.

In fact, I need a way to control the exception"s", especially file/directory 
not found.

In my case : there is a feature to poll files from a directory and process 
them, but the directory may not exist at first.

So, it's not error when directory not found, but I still need to know if there 
is 0 file in the directory or the directory not exist.

for ex, my log may looks like :
[0:00] dir not exist
[0:10] dir not exist
[0:20] dir not exist
[0:30] dir not exist
[0:40] 0 files process  <= directory exist, but no file yet !!
[0:50] 2 files process
[1:00] 23 files process
...

Current "file not found" exception is too verbose to me, and I can't format it.
Because of that, my current log looks like :
[0:00] org.apache.camel.component.file.GenericFileOperationFailedException: 
Cannot list directory: notexist
at 
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
at 
org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
at 
org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
at 
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
at 
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
[0:10] org.apache.camel.component.file.GenericFileOperationFailedException: 
Cannot list directory: notexist
at 
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
at 
org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
at 
org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
at 
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
at 
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
[0:30] org.apache.camel.component.file.GenericFileOperationFailedException: 
Cannot list directory: notexist
at 
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
at 
org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
at 
org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
at 
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
at 
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
[0:40] 0 files process  <= directory exist, but no file yet !!
[0:50] 2 files process
[1:00] 23 files process


was (Author: abccbaandy):
yes and no.

In fact, I need a way to control the exception"s", especially file/directory 
not found.

In my case, it's not error when directory not found, but I still need to know 
if there is 0 file in the directory or the directory not exist.

for ex:
mylog.log
[0:00] dir not exist
[0:10] dir not exist
[0:20] dir not exist
[0:30] dir not exist
[0:40] 0 files process  <= directory exist, but no file yet !!
[0:50] 2 files process
[1:00] 23 files process
...

Current "file not found" exception is too verbose to me, and I can't format it.

> camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found
> --
>
> Key: CAMEL-12337
> URL: https://issues.apache.org/jira/browse/CAMEL-12337
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-ftp, camel-sftp
>Affects Versions: 2.20.2
>Reporter: abccbaandy
>Priority: Minor
>
> I tried something like these code, but when "notexist" folder not exist, it 
> still give me exception
> {code:java}
> sftp://testserver:22/notexist?autoCreate=false=true
> {code}
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot 
> list directory: notexist
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at 

[jira] [Resolved] (CAMEL-11370) Problem with MTOM in Camel-CXF

2018-03-09 Thread Claus Ibsen (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-11370.
-
Resolution: Unresolved

> Problem with MTOM in Camel-CXF
> --
>
> Key: CAMEL-11370
> URL: https://issues.apache.org/jira/browse/CAMEL-11370
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxf
>Reporter: Joerg Kessler
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.21.0
>
> Attachments: MTOM-conversion.patch, 
> accept-also-sub-classes-of-orgapachecxfjaxbJAXBDataB.patch, mtom.test.zip
>
>
> I originally opened the issue on CXF:
> https://issues.apache.org/jira/browse/CXF-7388
> but ther CXF guys think the problem is in camel-cxf. Please have a look at 
> this ticket. Basically the MTOM conversion seems not to work anymore when 
> using CXF in Camel. I provided a unit test that demonstrates the observed 
> behaviour.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Reopened] (CAMEL-11370) Problem with MTOM in Camel-CXF

2018-03-09 Thread Claus Ibsen (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen reopened CAMEL-11370:
-

> Problem with MTOM in Camel-CXF
> --
>
> Key: CAMEL-11370
> URL: https://issues.apache.org/jira/browse/CAMEL-11370
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxf
>Reporter: Joerg Kessler
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.21.0
>
> Attachments: MTOM-conversion.patch, 
> accept-also-sub-classes-of-orgapachecxfjaxbJAXBDataB.patch, mtom.test.zip
>
>
> I originally opened the issue on CXF:
> https://issues.apache.org/jira/browse/CXF-7388
> but ther CXF guys think the problem is in camel-cxf. Please have a look at 
> this ticket. Basically the MTOM conversion seems not to work anymore when 
> using CXF in Camel. I provided a unit test that demonstrates the observed 
> behaviour.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-11370) Problem with MTOM in Camel-CXF

2018-03-09 Thread Claus Ibsen (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393289#comment-16393289
 ] 

Claus Ibsen commented on CAMEL-11370:
-

I dont think anyone going to work on this that hybrid stuff is added in 2010

> Problem with MTOM in Camel-CXF
> --
>
> Key: CAMEL-11370
> URL: https://issues.apache.org/jira/browse/CAMEL-11370
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxf
>Reporter: Joerg Kessler
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.21.0
>
> Attachments: MTOM-conversion.patch, 
> accept-also-sub-classes-of-orgapachecxfjaxbJAXBDataB.patch, mtom.test.zip
>
>
> I originally opened the issue on CXF:
> https://issues.apache.org/jira/browse/CXF-7388
> but ther CXF guys think the problem is in camel-cxf. Please have a look at 
> this ticket. Basically the MTOM conversion seems not to work anymore when 
> using CXF in Camel. I provided a unit test that demonstrates the observed 
> behaviour.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-12337) camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found

2018-03-09 Thread Claus Ibsen (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-12337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393283#comment-16393283
 ] 

Claus Ibsen commented on CAMEL-12337:
-

And how do you run that code, eg what do you do with that endpoint to poll 
those files, can you show more of that

> camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found
> --
>
> Key: CAMEL-12337
> URL: https://issues.apache.org/jira/browse/CAMEL-12337
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-ftp, camel-sftp
>Affects Versions: 2.20.2
>Reporter: abccbaandy
>Priority: Minor
>
> I tried something like these code, but when "notexist" folder not exist, it 
> still give me exception
> {code:java}
> sftp://testserver:22/notexist?autoCreate=false=true
> {code}
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot 
> list directory: notexist
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: com.jcraft.jsch.SftpException: No such file
>   at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2873)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2225)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2242)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1592)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1553)
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:641)
>   ... 12 common frames omitted
> {code}
> ftp has the same issue.
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: File 
> operation failed: 550 The system cannot find the file specified. 
>  Cannot change directory to: notexist. Code: 550
>   at 
> org.apache.camel.component.file.remote.FtpOperations.doChangeDirectory(FtpOperations.java:790)
>   at 
> org.apache.camel.component.file.remote.FtpOperations.changeCurrentDirectory(FtpOperations.java:768)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.doPollDirectory(FtpConsumer.java:112)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.pollDirectory(FtpConsumer.java:83)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-12337) camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found

2018-03-09 Thread Claus Ibsen (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-12337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393281#comment-16393281
 ] 

Claus Ibsen commented on CAMEL-12337:
-

Do you see any WARN in the logs, something about cannot auto-create directory 
or something?

> camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found
> --
>
> Key: CAMEL-12337
> URL: https://issues.apache.org/jira/browse/CAMEL-12337
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-ftp, camel-sftp
>Affects Versions: 2.20.2
>Reporter: abccbaandy
>Priority: Minor
>
> I tried something like these code, but when "notexist" folder not exist, it 
> still give me exception
> {code:java}
> sftp://testserver:22/notexist?autoCreate=false=true
> {code}
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot 
> list directory: notexist
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: com.jcraft.jsch.SftpException: No such file
>   at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2873)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2225)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2242)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1592)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1553)
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:641)
>   ... 12 common frames omitted
> {code}
> ftp has the same issue.
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: File 
> operation failed: 550 The system cannot find the file specified. 
>  Cannot change directory to: notexist. Code: 550
>   at 
> org.apache.camel.component.file.remote.FtpOperations.doChangeDirectory(FtpOperations.java:790)
>   at 
> org.apache.camel.component.file.remote.FtpOperations.changeCurrentDirectory(FtpOperations.java:768)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.doPollDirectory(FtpConsumer.java:112)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.pollDirectory(FtpConsumer.java:83)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (CAMEL-12318) Exception from aggregate() of AggregationStrategy has been hiden since Camel 2.16.x

2018-03-09 Thread Claus Ibsen (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-12318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-12318.
-
   Resolution: Implemented
 Assignee: Claus Ibsen
Fix Version/s: 2.21.0

Thanks for looking into this

> Exception from aggregate() of AggregationStrategy has been hiden since Camel 
> 2.16.x
> ---
>
> Key: CAMEL-12318
> URL: https://issues.apache.org/jira/browse/CAMEL-12318
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.16.5, 2.20.2
> Environment: Java 8
>Reporter: Xilai Dai
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 2.21.0
>
>
> In case of any exception thrown from aggregate() of the custom 
> AggregationStrategy class, the exception is hiden by Camel core and couldn't 
> be catched by any errorhandler.
> A simple use case project is created for easy reproduce this issue, 
> https://github.com/xldai/test/tree/master/test-multicast
> With setting camel.ver to 2.15.x in the pom.xml, the Exception is thrown as 
> expected:
> {code:java}
> Caused by: java.lang.RuntimeException: Deliberate Exception
>     at 
> beans.FD_MulticastAggregator.aggregate(FD_MulticastAggregator.java:16)
>     at 
> org.apache.camel.processor.MulticastProcessor.doAggregateInternal(MulticastProcessor.java:848)
>     at 
> org.apache.camel.processor.MulticastProcessor.doAggregate(MulticastProcessor.java:830)
>     at 
> org.apache.camel.processor.MulticastProcessor$AggregateOnTheFlyTask.aggregateOnTheFly(MulticastProcessor.java:489)
>     at 
> org.apache.camel.processor.MulticastProcessor$AggregateOnTheFlyTask.run(MulticastProcessor.java:394){code}
> With setting camel.ver to higher than 2.16.x in the pom.xml, the Exception is 
> not exposed anymore.
> Looking into the commit changes, seems this is happening after the changes of 
> CAMEL-8587.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (CAMEL-12341) camel-spring-boot - Add actuator to dump routes in xml format

2018-03-09 Thread Claus Ibsen (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-12341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-12341.
-
Resolution: Fixed

> camel-spring-boot - Add actuator to dump routes in xml format
> -
>
> Key: CAMEL-12341
> URL: https://issues.apache.org/jira/browse/CAMEL-12341
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-spring-boot
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 2.21.0
>
>
> So you can get a XML dump of a route, we can get details and other stats 
> today. This should only be possible if its not in read-only mode



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (CAMEL-12340) camel uses org.springframework.boot.bind.RelaxedPropertyResolver which is removed from spring 2.0.0

2018-03-09 Thread Claus Ibsen (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-12340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-12340.
-
   Resolution: Invalid
 Assignee: Claus Ibsen
Fix Version/s: 2.21.0

Spring Boot 2 is not supported - wait for Camel 2.22 release

> camel uses org.springframework.boot.bind.RelaxedPropertyResolver which is 
> removed from spring 2.0.0
> ---
>
> Key: CAMEL-12340
> URL: https://issues.apache.org/jira/browse/CAMEL-12340
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.20.2
>Reporter: Dag Framstad
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 2.21.0
>
>
> I'm using camel 2.20.2 and I've upgraded to spring boot 2.0.0 (from 1.5.10) 
> and am getting this stacktrace when I start my application:
> {code:java}
> // code placeholder
> 2018-03-09 17:47:34,372 ERROR org.springframework.boot.SpringApplication 
> Application run failed
> org.springframework.beans.factory.BeanDefinitionStoreException: Failed to 
> process import candidates for configuration class 
> [no.nav.helse.utbetaling.UtbetalingsOppdragApplication]; nested exception is 
> java.lang.IllegalStateException: Could not evaluate condition on 
> org.apache.camel.spring.boot.health.HealthCheckRoutesAutoConfiguration due to 
> org/springframework/boot/bind/RelaxedPropertyResolver not found. Make sure 
> your own configuration does not rely on that class. This can also happen if 
> you are @ComponentScanning a springframework package (e.g. if you put a 
> @ComponentScan in the default package by mistake)
> at 
> org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:616)
>  ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
> at 
> org.springframework.context.annotation.ConfigurationClassParser.processDeferredImportSelectors(ConfigurationClassParser.java:548)
>  ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
> at 
> org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:184)
>  ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
> at 
> org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:316)
>  ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
> at 
> org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:233)
>  ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
> at 
> org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(PostProcessorRegistrationDelegate.java:273)
>  ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
> at 
> org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:93)
>  ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
> at 
> org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:693)
>  ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
> at 
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:531)
>  ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
> at 
> org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140)
>  ~[spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
> at 
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:752)
>  [spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
> at 
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:388)
>  [spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
> at org.springframework.boot.SpringApplication.run(SpringApplication.java:327) 
> [spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
> at 
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1246) 
> [spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
> at 
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1234) 
> [spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
> at 
> no.nav.helse.utbetaling.UtbetalingsOppdragApplication.main(UtbetalingsOppdragApplication.java:19)
>  [classes/:?]
> Caused by: java.lang.IllegalStateException: Could not evaluate condition on 
> org.apache.camel.spring.boot.health.HealthCheckRoutesAutoConfiguration due to 
> org/springframework/boot/bind/RelaxedPropertyResolver not found. Make sure 
> your own configuration does not rely on that class. This can also happen if 
> you are @ComponentScanning a springframework package (e.g. if you put a 
> @ComponentScan in the default package by mistake)
> at 
> 

[jira] [Created] (CAMEL-12341) camel-spring-boot - Add actuator to dump routes in xml format

2018-03-09 Thread Claus Ibsen (JIRA)
Claus Ibsen created CAMEL-12341:
---

 Summary: camel-spring-boot - Add actuator to dump routes in xml 
format
 Key: CAMEL-12341
 URL: https://issues.apache.org/jira/browse/CAMEL-12341
 Project: Camel
  Issue Type: Improvement
  Components: camel-spring-boot
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 2.21.0


So you can get a XML dump of a route, we can get details and other stats today. 
This should only be possible if its not in read-only mode



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-11370) Problem with MTOM in Camel-CXF

2018-03-09 Thread Sascha Dirbach (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393220#comment-16393220
 ] 

Sascha Dirbach commented on CAMEL-11370:


[~davsclaus] my comment was only related to the memory consumption. I suspect 
that the original issue still persists...

> Problem with MTOM in Camel-CXF
> --
>
> Key: CAMEL-11370
> URL: https://issues.apache.org/jira/browse/CAMEL-11370
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxf
>Reporter: Joerg Kessler
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.21.0
>
> Attachments: MTOM-conversion.patch, 
> accept-also-sub-classes-of-orgapachecxfjaxbJAXBDataB.patch, mtom.test.zip
>
>
> I originally opened the issue on CXF:
> https://issues.apache.org/jira/browse/CXF-7388
> but ther CXF guys think the problem is in camel-cxf. Please have a look at 
> this ticket. Basically the MTOM conversion seems not to work anymore when 
> using CXF in Camel. I provided a unit test that demonstrates the observed 
> behaviour.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (CAMEL-12340) camel uses org.springframework.boot.bind.RelaxedPropertyResolver which is removed from spring 2.0.0

2018-03-09 Thread Dag Framstad (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-12340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dag Framstad updated CAMEL-12340:
-
Description: 
I'm using camel 2.20.2 and I've upgraded to spring boot 2.0.0 (from 1.5.10) and 
am getting this stacktrace when I start my application:
{code:java}
// code placeholder
2018-03-09 17:47:34,372 ERROR org.springframework.boot.SpringApplication 
Application run failed
org.springframework.beans.factory.BeanDefinitionStoreException: Failed to 
process import candidates for configuration class 
[no.nav.helse.utbetaling.UtbetalingsOppdragApplication]; nested exception is 
java.lang.IllegalStateException: Could not evaluate condition on 
org.apache.camel.spring.boot.health.HealthCheckRoutesAutoConfiguration due to 
org/springframework/boot/bind/RelaxedPropertyResolver not found. Make sure your 
own configuration does not rely on that class. This can also happen if you are 
@ComponentScanning a springframework package (e.g. if you put a @ComponentScan 
in the default package by mistake)
at 
org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:616)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.annotation.ConfigurationClassParser.processDeferredImportSelectors(ConfigurationClassParser.java:548)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:184)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:316)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:233)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(PostProcessorRegistrationDelegate.java:273)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:93)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:693)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:531)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140)
 ~[spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at 
org.springframework.boot.SpringApplication.refresh(SpringApplication.java:752) 
[spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at 
org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:388)
 [spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:327) 
[spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1246) 
[spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1234) 
[spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at 
no.nav.helse.utbetaling.UtbetalingsOppdragApplication.main(UtbetalingsOppdragApplication.java:19)
 [classes/:?]
Caused by: java.lang.IllegalStateException: Could not evaluate condition on 
org.apache.camel.spring.boot.health.HealthCheckRoutesAutoConfiguration due to 
org/springframework/boot/bind/RelaxedPropertyResolver not found. Make sure your 
own configuration does not rely on that class. This can also happen if you are 
@ComponentScanning a springframework package (e.g. if you put a @ComponentScan 
in the default package by mistake)
at 
org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:55)
 ~[spring-boot-autoconfigure-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at 
org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:109)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:217)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:606)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
... 15 more
Caused by: java.lang.NoClassDefFoundError: 
org/springframework/boot/bind/RelaxedPropertyResolver
at 

[jira] [Created] (CAMEL-12340) camel uses org.springframework.boot.bind.RelaxedPropertyResolver which is removed from spring 2.0.0

2018-03-09 Thread Dag Framstad (JIRA)
Dag Framstad created CAMEL-12340:


 Summary: camel uses 
org.springframework.boot.bind.RelaxedPropertyResolver which is removed from 
spring 2.0.0
 Key: CAMEL-12340
 URL: https://issues.apache.org/jira/browse/CAMEL-12340
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.20.2
Reporter: Dag Framstad


I'm using camel 2.20.2 and I've upgraded to spring boot 2.0.0 (from 1.5.10) and 
am getting this stacktrace when I start my application:
{code:java}
// code placeholder
2018-03-09 17:47:34,372 ERROR org.springframework.boot.SpringApplication 
Application run failed
org.springframework.beans.factory.BeanDefinitionStoreException: Failed to 
process import candidates for configuration class 
[no.nav.helse.utbetaling.UtbetalingsOppdragApplication]; nested exception is 
java.lang.IllegalStateException: Could not evaluate condition on 
org.apache.camel.spring.boot.health.HealthCheckRoutesAutoConfiguration due to 
org/springframework/boot/bind/RelaxedPropertyResolver not found. Make sure your 
own configuration does not rely on that class. This can also happen if you are 
@ComponentScanning a springframework package (e.g. if you put a @ComponentScan 
in the default package by mistake)
at 
org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:616)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.annotation.ConfigurationClassParser.processDeferredImportSelectors(ConfigurationClassParser.java:548)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:184)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:316)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:233)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(PostProcessorRegistrationDelegate.java:273)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:93)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:693)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:531)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140)
 ~[spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at 
org.springframework.boot.SpringApplication.refresh(SpringApplication.java:752) 
[spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at 
org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:388)
 [spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:327) 
[spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1246) 
[spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1234) 
[spring-boot-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at 
no.nav.helse.utbetaling.UtbetalingsOppdragApplication.main(UtbetalingsOppdragApplication.java:19)
 [classes/:?]
Caused by: java.lang.IllegalStateException: Could not evaluate condition on 
org.apache.camel.spring.boot.health.HealthCheckRoutesAutoConfiguration due to 
org/springframework/boot/bind/RelaxedPropertyResolver not found. Make sure your 
own configuration does not rely on that class. This can also happen if you are 
@ComponentScanning a springframework package (e.g. if you put a @ComponentScan 
in the default package by mistake)
at 
org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:55)
 ~[spring-boot-autoconfigure-2.0.0.RELEASE.jar:2.0.0.RELEASE]
at 
org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:109)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:217)
 ~[spring-context-5.0.4.RELEASE.jar:5.0.4.RELEASE]
at 
org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:606)
 

[jira] [Commented] (CAMEL-12318) Exception from aggregate() of AggregationStrategy has been hiden since Camel 2.16.x

2018-03-09 Thread Sascha Dirbach (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-12318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393218#comment-16393218
 ] 

Sascha Dirbach commented on CAMEL-12318:


Hi,

for parallel processing there is a new option: stopOnAggregateException().

This was introduced in #CAMEL-10272 
[https://github.com/apache/camel/commit/43036a4a574873feaa421abbb5393f865714d790]

I think this can be closed

> Exception from aggregate() of AggregationStrategy has been hiden since Camel 
> 2.16.x
> ---
>
> Key: CAMEL-12318
> URL: https://issues.apache.org/jira/browse/CAMEL-12318
> Project: Camel
>  Issue Type: Bug
>  Components: camel-core
>Affects Versions: 2.16.5, 2.20.2
> Environment: Java 8
>Reporter: Xilai Dai
>Priority: Major
>
> In case of any exception thrown from aggregate() of the custom 
> AggregationStrategy class, the exception is hiden by Camel core and couldn't 
> be catched by any errorhandler.
> A simple use case project is created for easy reproduce this issue, 
> https://github.com/xldai/test/tree/master/test-multicast
> With setting camel.ver to 2.15.x in the pom.xml, the Exception is thrown as 
> expected:
> {code:java}
> Caused by: java.lang.RuntimeException: Deliberate Exception
>     at 
> beans.FD_MulticastAggregator.aggregate(FD_MulticastAggregator.java:16)
>     at 
> org.apache.camel.processor.MulticastProcessor.doAggregateInternal(MulticastProcessor.java:848)
>     at 
> org.apache.camel.processor.MulticastProcessor.doAggregate(MulticastProcessor.java:830)
>     at 
> org.apache.camel.processor.MulticastProcessor$AggregateOnTheFlyTask.aggregateOnTheFly(MulticastProcessor.java:489)
>     at 
> org.apache.camel.processor.MulticastProcessor$AggregateOnTheFlyTask.run(MulticastProcessor.java:394){code}
> With setting camel.ver to higher than 2.16.x in the pom.xml, the Exception is 
> not exposed anymore.
> Looking into the commit changes, seems this is happening after the changes of 
> CAMEL-8587.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-12337) camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found

2018-03-09 Thread abccbaandy (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-12337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393152#comment-16393152
 ] 

abccbaandy commented on CAMEL-12337:


yes and no.

In fact, I need a way to control the exception"s", especially file/directory 
not found.

In my case, it's not error when directory not found, but I still need to know 
if there is 0 file in the directory or the directory not exist.

for ex:
mylog.log
[0:00] dir not exist
[0:10] dir not exist
[0:20] dir not exist
[0:30] dir not exist
[0:40] 0 files process  <= directory exist, but no file yet !!
[0:50] 2 files process
[1:00] 23 files process
...

Current "file not found" exception is too verbose to me, and I can't format it.

> camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found
> --
>
> Key: CAMEL-12337
> URL: https://issues.apache.org/jira/browse/CAMEL-12337
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-ftp, camel-sftp
>Affects Versions: 2.20.2
>Reporter: abccbaandy
>Priority: Minor
>
> I tried something like these code, but when "notexist" folder not exist, it 
> still give me exception
> {code:java}
> sftp://testserver:22/notexist?autoCreate=false=true
> {code}
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot 
> list directory: notexist
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: com.jcraft.jsch.SftpException: No such file
>   at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2873)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2225)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2242)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1592)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1553)
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:641)
>   ... 12 common frames omitted
> {code}
> ftp has the same issue.
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: File 
> operation failed: 550 The system cannot find the file specified. 
>  Cannot change directory to: notexist. Code: 550
>   at 
> org.apache.camel.component.file.remote.FtpOperations.doChangeDirectory(FtpOperations.java:790)
>   at 
> org.apache.camel.component.file.remote.FtpOperations.changeCurrentDirectory(FtpOperations.java:768)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.doPollDirectory(FtpConsumer.java:112)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.pollDirectory(FtpConsumer.java:83)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This 

[jira] [Resolved] (CAMEL-11370) Problem with MTOM in Camel-CXF

2018-03-09 Thread Claus Ibsen (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-11370.
-
   Resolution: Not A Bug
 Assignee: Claus Ibsen
Fix Version/s: 2.21.0

> Problem with MTOM in Camel-CXF
> --
>
> Key: CAMEL-11370
> URL: https://issues.apache.org/jira/browse/CAMEL-11370
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxf
>Reporter: Joerg Kessler
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.21.0
>
> Attachments: MTOM-conversion.patch, 
> accept-also-sub-classes-of-orgapachecxfjaxbJAXBDataB.patch, mtom.test.zip
>
>
> I originally opened the issue on CXF:
> https://issues.apache.org/jira/browse/CXF-7388
> but ther CXF guys think the problem is in camel-cxf. Please have a look at 
> this ticket. Basically the MTOM conversion seems not to work anymore when 
> using CXF in Camel. I provided a unit test that demonstrates the observed 
> behaviour.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-11370) Problem with MTOM in Camel-CXF

2018-03-09 Thread Claus Ibsen (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393087#comment-16393087
 ] 

Claus Ibsen commented on CAMEL-11370:
-

Thanks Sascha for your feedback.

> Problem with MTOM in Camel-CXF
> --
>
> Key: CAMEL-11370
> URL: https://issues.apache.org/jira/browse/CAMEL-11370
> Project: Camel
>  Issue Type: Bug
>  Components: camel-cxf
>Reporter: Joerg Kessler
>Priority: Minor
> Fix For: 2.21.0
>
> Attachments: MTOM-conversion.patch, 
> accept-also-sub-classes-of-orgapachecxfjaxbJAXBDataB.patch, mtom.test.zip
>
>
> I originally opened the issue on CXF:
> https://issues.apache.org/jira/browse/CXF-7388
> but ther CXF guys think the problem is in camel-cxf. Please have a look at 
> this ticket. Basically the MTOM conversion seems not to work anymore when 
> using CXF in Camel. I provided a unit test that demonstrates the observed 
> behaviour.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-12330) camel-rabbitmq - Allow to configure connection settings on component level

2018-03-09 Thread Claus Ibsen (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-12330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393082#comment-16393082
 ] 

Claus Ibsen commented on CAMEL-12330:
-

Got most of the options added, there is still some more, need to look into 
which ones that make sense to add

> camel-rabbitmq - Allow to configure connection settings on component level
> --
>
> Key: CAMEL-12330
> URL: https://issues.apache.org/jira/browse/CAMEL-12330
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-rabbitmq
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 2.21.0
>
>
> The component has no options. But we should allow to configure connection 
> settings etc so you can configure this once. And also maybe let it 
> auto-detect rabbitmq connection factory, so spring-boot users can just 
> configure it the spring-boot way.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-12337) camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found

2018-03-09 Thread Claus Ibsen (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-12337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393080#comment-16393080
 ] 

Claus Ibsen commented on CAMEL-12337:
-

Are you saying you want the ftp consumer to ignore any kind of failure if the 
directory you configured does not exists, and silently do not log any kind of 
error etc?

> camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found
> --
>
> Key: CAMEL-12337
> URL: https://issues.apache.org/jira/browse/CAMEL-12337
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-ftp, camel-sftp
>Affects Versions: 2.20.2
>Reporter: abccbaandy
>Priority: Minor
>
> I tried something like these code, but when "notexist" folder not exist, it 
> still give me exception
> {code:java}
> sftp://testserver:22/notexist?autoCreate=false=true
> {code}
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot 
> list directory: notexist
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: com.jcraft.jsch.SftpException: No such file
>   at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2873)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2225)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2242)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1592)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1553)
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:641)
>   ... 12 common frames omitted
> {code}
> ftp has the same issue.
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: File 
> operation failed: 550 The system cannot find the file specified. 
>  Cannot change directory to: notexist. Code: 550
>   at 
> org.apache.camel.component.file.remote.FtpOperations.doChangeDirectory(FtpOperations.java:790)
>   at 
> org.apache.camel.component.file.remote.FtpOperations.changeCurrentDirectory(FtpOperations.java:768)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.doPollDirectory(FtpConsumer.java:112)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.pollDirectory(FtpConsumer.java:83)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (CAMEL-12331) camel-sql - JdbcMessageIdRepository should have a background task to delete old entries

2018-03-09 Thread Claus Ibsen (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-12331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-12331:

Fix Version/s: 2.22.0

> camel-sql - JdbcMessageIdRepository should have a background task to delete 
> old entries
> ---
>
> Key: CAMEL-12331
> URL: https://issues.apache.org/jira/browse/CAMEL-12331
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-sql
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 2.22.0
>
>
> You may want to cleanup the database table automatically by Camel so it does 
> not contain old data of previous processed files.
> For example to say that entries that are > 24h can be deleted etc. 
> This works under the notion that you only use the idempoten check for 
> clustering where they may race for processing the same files, or that files 
> tomorrow are okay to process with the same name as yesterday etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (CAMEL-12337) camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found

2018-03-09 Thread Claus Ibsen (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-12337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-12337:

Issue Type: Improvement  (was: Bug)

> camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found
> --
>
> Key: CAMEL-12337
> URL: https://issues.apache.org/jira/browse/CAMEL-12337
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-ftp, camel-sftp
>Affects Versions: 2.20.2
>Reporter: abccbaandy
>Priority: Major
>
> I tried something like these code, but when "notexist" folder not exist, it 
> still give me exception
> {code:java}
> sftp://testserver:22/notexist?autoCreate=false=true
> {code}
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot 
> list directory: notexist
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: com.jcraft.jsch.SftpException: No such file
>   at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2873)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2225)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2242)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1592)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1553)
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:641)
>   ... 12 common frames omitted
> {code}
> ftp has the same issue.
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: File 
> operation failed: 550 The system cannot find the file specified. 
>  Cannot change directory to: notexist. Code: 550
>   at 
> org.apache.camel.component.file.remote.FtpOperations.doChangeDirectory(FtpOperations.java:790)
>   at 
> org.apache.camel.component.file.remote.FtpOperations.changeCurrentDirectory(FtpOperations.java:768)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.doPollDirectory(FtpConsumer.java:112)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.pollDirectory(FtpConsumer.java:83)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-12337) camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found

2018-03-09 Thread Claus Ibsen (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-12337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16393077#comment-16393077
 ] 

Claus Ibsen commented on CAMEL-12337:
-

This is for when downloading *files* and was not originally intended for when 
failing to list directories. 

> camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found
> --
>
> Key: CAMEL-12337
> URL: https://issues.apache.org/jira/browse/CAMEL-12337
> Project: Camel
>  Issue Type: Bug
>  Components: camel-ftp, camel-sftp
>Affects Versions: 2.20.2
>Reporter: abccbaandy
>Priority: Major
>
> I tried something like these code, but when "notexist" folder not exist, it 
> still give me exception
> {code:java}
> sftp://testserver:22/notexist?autoCreate=false=true
> {code}
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot 
> list directory: notexist
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: com.jcraft.jsch.SftpException: No such file
>   at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2873)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2225)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2242)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1592)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1553)
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:641)
>   ... 12 common frames omitted
> {code}
> ftp has the same issue.
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: File 
> operation failed: 550 The system cannot find the file specified. 
>  Cannot change directory to: notexist. Code: 550
>   at 
> org.apache.camel.component.file.remote.FtpOperations.doChangeDirectory(FtpOperations.java:790)
>   at 
> org.apache.camel.component.file.remote.FtpOperations.changeCurrentDirectory(FtpOperations.java:768)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.doPollDirectory(FtpConsumer.java:112)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.pollDirectory(FtpConsumer.java:83)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (CAMEL-12337) camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found

2018-03-09 Thread Claus Ibsen (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-12337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-12337:

Priority: Minor  (was: Major)

> camel-ftp - ignoreFileNotFoundOrPermissionError not work when folder not found
> --
>
> Key: CAMEL-12337
> URL: https://issues.apache.org/jira/browse/CAMEL-12337
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-ftp, camel-sftp
>Affects Versions: 2.20.2
>Reporter: abccbaandy
>Priority: Minor
>
> I tried something like these code, but when "notexist" folder not exist, it 
> still give me exception
> {code:java}
> sftp://testserver:22/notexist?autoCreate=false=true
> {code}
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot 
> list directory: notexist
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
>   at 
> org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: com.jcraft.jsch.SftpException: No such file
>   at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2873)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2225)
>   at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2242)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1592)
>   at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1553)
>   at 
> org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:641)
>   ... 12 common frames omitted
> {code}
> ftp has the same issue.
> {code:java}
> org.apache.camel.component.file.GenericFileOperationFailedException: File 
> operation failed: 550 The system cannot find the file specified. 
>  Cannot change directory to: notexist. Code: 550
>   at 
> org.apache.camel.component.file.remote.FtpOperations.doChangeDirectory(FtpOperations.java:790)
>   at 
> org.apache.camel.component.file.remote.FtpOperations.changeCurrentDirectory(FtpOperations.java:768)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.doPollDirectory(FtpConsumer.java:112)
>   at 
> org.apache.camel.component.file.remote.FtpConsumer.pollDirectory(FtpConsumer.java:83)
>   at 
> org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
>   at 
> org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (CAMEL-12339) Add jsonpath to RouteBuilder

2018-03-09 Thread Claus Ibsen (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-12339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-12339.
-
Resolution: Fixed
  Assignee: Claus Ibsen

> Add jsonpath to RouteBuilder
> 
>
> Key: CAMEL-12339
> URL: https://issues.apache.org/jira/browse/CAMEL-12339
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.21.0
>
>
> So you can more easily use jsonpath in Java DSL. We have xpath there already 
> etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (CAMEL-12339) Add jsonpath to RouteBuilder

2018-03-09 Thread Claus Ibsen (JIRA)
Claus Ibsen created CAMEL-12339:
---

 Summary: Add jsonpath to RouteBuilder
 Key: CAMEL-12339
 URL: https://issues.apache.org/jira/browse/CAMEL-12339
 Project: Camel
  Issue Type: Improvement
  Components: camel-core
Reporter: Claus Ibsen
 Fix For: 2.21.0


So you can more easily use jsonpath in Java DSL. We have xpath there already 
etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-11497) Migrate the rest of the Confluence content

2018-03-09 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392689#comment-16392689
 ] 

ASF GitHub Bot commented on CAMEL-11497:


Github user onderson closed the pull request at:

https://github.com/apache/camel/pull/2250


> Migrate the rest of the Confluence content
> --
>
> Key: CAMEL-11497
> URL: https://issues.apache.org/jira/browse/CAMEL-11497
> Project: Camel
>  Issue Type: Sub-task
>  Components: website
>Reporter: Zoran Regvart
>Assignee: Önder Sezgin
>Priority: Major
> Fix For: Future
>
>
> There are still pages in the Confluence that are not migrated to Asciidoctor



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-11497) Migrate the rest of the Confluence content

2018-03-09 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392688#comment-16392688
 ] 

ASF GitHub Bot commented on CAMEL-11497:


onderson closed pull request #2250: CAMEL-11497 - add rollback-eip considering 
transactional-client.adoc …
URL: https://github.com/apache/camel/pull/2250
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/camel-core/src/main/docs/eips/rollback-eip.adoc 
b/camel-core/src/main/docs/eips/rollback-eip.adoc
new file mode 100644
index 000..a749340
--- /dev/null
+++ b/camel-core/src/main/docs/eips/rollback-eip.adoc
@@ -0,0 +1,252 @@
+[[rollback-eip]]
+
+Rollback might be needed if there is a transaction or transactional pieces in 
your design.
+
+Camel recommends supporting the
+http://www.enterpriseintegrationpatterns.com/TransactionalClient.html[Transactional
+Client] from the link:enterprise-integration-patterns.html[EIP patterns]
+using spring transactions.
+
+image:http://www.enterpriseintegrationpatterns.com/img/TransactionalClientSolution.gif[image]
+
+Transaction Oriented Endpoints like 
link:https://github.com/apache/camel/blob/master/components/camel-jms/src/main/docs/jms-component.adoc[JMS]
 support using a
+transaction for both inbound and outbound message exchanges. Endpoints
+that support transactions will participate in the current transaction
+context that they are called from.
+
+Configuration of Redelivery
+
+The redelivery in transacted mode is *not* handled by Camel but by the
+backing system (the transaction manager). In such cases you should
+resort to the backing system how to configure the redelivery.
+
+You should use the
+http://camel.apache.org/maven/current/camel-spring/apidocs/org/apache/camel/spring/SpringRouteBuilder.html[SpringRouteBuilder]
+to setup the routes since you will need to setup the spring context with
+the TransactionTemplates that will define the transaction manager
+configuration and policies.
+
+For inbound endpoint to be transacted, they normally need to be
+configured to use a Spring PlatformTransactionManager. In the case of
+the JMS component, this can be done by looking it up in the spring
+context.
+
+You first define needed object in the spring configuration.
+
+[source,xml]
+
+
+  
+
+ 
+  
+
+
+
+Then you look them up and use them to create the JmsComponent.
+
+[source,java]
+
+PlatformTransactionManager transactionManager = (PlatformTransactionManager) 
spring.getBean("jmsTransactionManager");
+ConnectionFactory connectionFactory = (ConnectionFactory) 
spring.getBean("jmsConnectionFactory");
+JmsComponent component = 
JmsComponent.jmsComponentTransacted(connectionFactory, transactionManager);
+component.getConfiguration().setConcurrentConsumers(1);
+ctx.addComponent("activemq", component);
+
+
+[[TransactionalClient-TransactionPolicies]]
+Transaction Policies
+
+
+Outbound endpoints will automatically enlist in the current transaction
+context. But what if you do not want your outbound endpoint to enlist in
+the same transaction as your inbound endpoint? The solution is to add a
+Transaction Policy to the processing route. You first have to define
+transaction policies that you will be using. The policies use a spring
+TransactionTemplate under the covers for declaring the transaction
+demarcation to use. So you will need to add something like the following
+to your spring xml:
+
+[source,xml]
+
+
+  
+
+
+   
+  
+
+
+
+Then in your
+http://camel.apache.org/maven/current/camel-spring/apidocs/org/apache/camel/spring/SpringRouteBuilder.html[SpringRouteBuilder],
+you just need to create new SpringTransactionPolicy objects for each of
+the templates.
+
+[source,java]
+
+public void configure() { 
+... 
+Policy requried = bean(SpringTransactionPolicy.class, 
"PROPAGATION_REQUIRED")); 
+Policy requirenew = bean(SpringTransactionPolicy.class, 
"PROPAGATION_REQUIRES_NEW")); 
+... 
+}
+
+Once created, you can use the Policy objects in your processing routes:
+
+[source,java]
+
+ // Send to bar in a new transaction
+from("activemq:queue:foo").policy(requirenew).to("activemq:queue:bar");
+// Send to bar without a transaction.
+from("activemq:queue:foo").policy(notsupported).to("activemq:queue:bar");
+
+
+[[TransactionalClient-OSGiBlueprint]]
+OSGi Blueprint
+++
+
+If you are using 
link:https://github.com/apache/camel/blob/master/docs/user-manual/en/using-osgi-blueprint-with-camel.adoc[OSGi

[jira] [Commented] (CAMEL-11497) Migrate the rest of the Confluence content

2018-03-09 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392640#comment-16392640
 ] 

ASF GitHub Bot commented on CAMEL-11497:


oscerd commented on issue #2250: CAMEL-11497 - add rollback-eip considering 
transactional-client.adoc …
URL: https://github.com/apache/camel/pull/2250#issuecomment-371758248
 
 
   I think that's exactly the good one


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Migrate the rest of the Confluence content
> --
>
> Key: CAMEL-11497
> URL: https://issues.apache.org/jira/browse/CAMEL-11497
> Project: Camel
>  Issue Type: Sub-task
>  Components: website
>Reporter: Zoran Regvart
>Assignee: Önder Sezgin
>Priority: Major
> Fix For: Future
>
>
> There are still pages in the Confluence that are not migrated to Asciidoctor



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-11497) Migrate the rest of the Confluence content

2018-03-09 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392639#comment-16392639
 ] 

ASF GitHub Bot commented on CAMEL-11497:


GitHub user onderson opened a pull request:

https://github.com/apache/camel/pull/2250

CAMEL-11497 - add rollback-eip considering transactional-client.adoc …

…from export of current camel-web.

Not sure if that would provide the right whole information about 
rollback-eip.
Could you please review?


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/onderson/camel CAMEL-11497

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/camel/pull/2250.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2250


commit e4a1343a915ff24a7835a49bf5b56728b44356bf
Author: Sezgin 
Date:   2018-03-09T07:59:10Z

CAMEL-11497 - add rollback-eip considering transactional-client.adoc from 
export of current camel-web




> Migrate the rest of the Confluence content
> --
>
> Key: CAMEL-11497
> URL: https://issues.apache.org/jira/browse/CAMEL-11497
> Project: Camel
>  Issue Type: Sub-task
>  Components: website
>Reporter: Zoran Regvart
>Assignee: Önder Sezgin
>Priority: Major
> Fix For: Future
>
>
> There are still pages in the Confluence that are not migrated to Asciidoctor



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-11497) Migrate the rest of the Confluence content

2018-03-09 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392638#comment-16392638
 ] 

ASF GitHub Bot commented on CAMEL-11497:


onderson opened a new pull request #2250: CAMEL-11497 - add rollback-eip 
considering transactional-client.adoc …
URL: https://github.com/apache/camel/pull/2250
 
 
   …from export of current camel-web.
   
   Not sure if that would provide the right whole information about 
rollback-eip.
   Could you please review?
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Migrate the rest of the Confluence content
> --
>
> Key: CAMEL-11497
> URL: https://issues.apache.org/jira/browse/CAMEL-11497
> Project: Camel
>  Issue Type: Sub-task
>  Components: website
>Reporter: Zoran Regvart
>Assignee: Önder Sezgin
>Priority: Major
> Fix For: Future
>
>
> There are still pages in the Confluence that are not migrated to Asciidoctor



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-10424) Bean should act like transform/setBody when setting result

2018-03-09 Thread Hubert Landl (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-10424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392616#comment-16392616
 ] 

Hubert Landl commented on CAMEL-10424:
--

Is this adaption a break against the message exchange pattern?

We use in some routes ExchangePattern.InOnly.
To remove unwanted headers, we set our required headers and body to 
Exchange.OUT.
In the next bean we always get the "cleaned" exchange object where in the IN 
part of the exchange only our expected headers are available.

Due to this adaption headers from IN and OUT are merged in Method 
"MethodInfo.fillResult" because exchange objects will be handled as OUT capable 
when exchange.hasOut()=true.
{code:java}
...
// the bean component forces OUT if the MEP is OUT capable
boolean out = ExchangeHelper.isOutCapable(exchange) || exchange.hasOut();
...
{code}
 

I expected that no "old" headers are available in the next bean and that 
setting from OUT to IN is only done in Method 
"PipelineHelper.createNextExchange(...)":
{code:java}
public static Exchange createNextExchange(Exchange previousExchange) {
 Exchange answer = previousExchange;
// now lets set the input of the next exchange to the output of the
 // previous message if it is not null
 if (answer.hasOut()) {
answer.setIn(answer.getOut());
answer.setOut(null);
 }
 return answer;
 }
{code}
I use currently Camel 2.17.7 and would upgrade to 2.20.2.

> Bean should act like transform/setBody when setting result
> --
>
> Key: CAMEL-10424
> URL: https://issues.apache.org/jira/browse/CAMEL-10424
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core
>Affects Versions: 2.18.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 2.18.1, 2.19.0
>
>
> See SO
> http://stackoverflow.com/questions/40293128/camel-rest-service-throws-exception-when-returning-null/40317432#40317432
> When you use http components that set the message as HttpMessage and then 
> call bean that returns null then we should do like transform/setBody does to 
> set the message as a default message.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (CAMEL-11823) [example] cdi-cassandrasql - nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 'Connection refused'

2018-03-09 Thread Andrea Cosentino (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-11823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-11823.
--
Resolution: Fixed

> [example] cdi-cassandrasql - nodetool: Failed to connect to '127.0.0.1:7199' 
> - ConnectException: 'Connection refused'
> -
>
> Key: CAMEL-11823
> URL: https://issues.apache.org/jira/browse/CAMEL-11823
> Project: Camel
>  Issue Type: Sub-task
>  Components: examples
>Affects Versions: 2.20.0
>Reporter: Tomohisa Igarashi
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.21.0
>
>
> something wrong with docker image
> {code}
> $ docker exec -ti master_node /opt/cassandra/bin/nodetool status
> nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 
> 'Connection refused'.
> {code}
> {code}
> $ docker logs master_node
> *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
> *** Running /etc/rc.local...
> *** Booting runit daemon...
> *** Runit started as PID 8
> I'm starting cassandra
> tail: unrecognized file system type 0x794c7630 for ‘/var/log/syslog’. please 
> report this to bug-coreut...@gnu.org. reverting to polling
> Filling in the blanks inside cassandra.yaml
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:28 Killed  bin/cassandra -Rf
> I'm starting cassandra
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:93 Killed  bin/cassandra -Rf
> I'm starting cassandra
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:   159 Killed  bin/cassandra -Rf
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-11823) [example] cdi-cassandrasql - nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 'Connection refused'

2018-03-09 Thread Andrea Cosentino (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392614#comment-16392614
 ] 

Andrea Cosentino commented on CAMEL-11823:
--

{code:java}
> docker logs master_node
*** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 9
I'm starting cassandra
Filling in the blanks inside cassandra.yaml
Mar 9 08:52:38 6965825dac1a syslog-ng[17]: syslog-ng starting up; 
version='3.5.3'
Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file bin/../logs/gc.log 
due to No such file or directory

CompilerOracle: dontinline 
org/apache/cassandra/db/Columns$Serializer.deserializeLargeSubset 
(Lorg/apache/cassandra/io/util/DataInputPlus;Lorg/apache/cassandra/db/Columns;I)Lorg/apache/cassandra/db/Columns;
CompilerOracle: dontinline 
org/apache/cassandra/db/Columns$Serializer.serializeLargeSubset 
(Ljava/util/Collection;ILorg/apache/cassandra/db/Columns;ILorg/apache/cassandra/io/util/DataOutputPlus;)V
CompilerOracle: dontinline 
org/apache/cassandra/db/Columns$Serializer.serializeLargeSubsetSize 
(Ljava/util/Collection;ILorg/apache/cassandra/db/Columns;I)I
CompilerOracle: dontinline 
org/apache/cassandra/db/commitlog/AbstractCommitLogSegmentManager.advanceAllocatingFrom
 (Lorg/apache/cassandra/db/commitlog/CommitLogSegment;)V
CompilerOracle: dontinline 
org/apache/cassandra/db/transform/BaseIterator.tryGetMoreContents ()Z
CompilerOracle: dontinline 
org/apache/cassandra/db/transform/StoppingTransformation.stop ()V
CompilerOracle: dontinline 
org/apache/cassandra/db/transform/StoppingTransformation.stopInPartition ()V
CompilerOracle: dontinline 
org/apache/cassandra/io/util/BufferedDataOutputStreamPlus.doFlush (I)V
CompilerOracle: dontinline 
org/apache/cassandra/io/util/BufferedDataOutputStreamPlus.writeExcessSlow ()V
CompilerOracle: dontinline 
org/apache/cassandra/io/util/BufferedDataOutputStreamPlus.writeSlow (JI)V
CompilerOracle: dontinline 
org/apache/cassandra/io/util/RebufferingInputStream.readPrimitiveSlowly (I)J
CompilerOracle: inline 
org/apache/cassandra/db/rows/UnfilteredSerializer.serializeRowBody 
(Lorg/apache/cassandra/db/rows/Row;ILorg/apache/cassandra/db/SerializationHeader;Lorg/apache/cassandra/io/util/DataOutputPlus;)V
CompilerOracle: inline org/apache/cassandra/io/util/Memory.checkBounds (JJ)V
CompilerOracle: inline org/apache/cassandra/io/util/SafeMemory.checkBounds (JJ)V
CompilerOracle: inline 
org/apache/cassandra/utils/AsymmetricOrdering.selectBoundary 
(Lorg/apache/cassandra/utils/AsymmetricOrdering/Op;II)I
CompilerOracle: inline 
org/apache/cassandra/utils/AsymmetricOrdering.strictnessOfLessThan 
(Lorg/apache/cassandra/utils/AsymmetricOrdering/Op;)I
CompilerOracle: inline org/apache/cassandra/utils/BloomFilter.indexes 
(Lorg/apache/cassandra/utils/IFilter/FilterKey;)[J
CompilerOracle: inline org/apache/cassandra/utils/BloomFilter.setIndexes 
(JJIJ[J)V
CompilerOracle: inline org/apache/cassandra/utils/ByteBufferUtil.compare 
(Ljava/nio/ByteBuffer;[B)I
CompilerOracle: inline org/apache/cassandra/utils/ByteBufferUtil.compare 
([BLjava/nio/ByteBuffer;)I
CompilerOracle: inline 
org/apache/cassandra/utils/ByteBufferUtil.compareUnsigned 
(Ljava/nio/ByteBuffer;Ljava/nio/ByteBuffer;)I
CompilerOracle: inline 
org/apache/cassandra/utils/FastByteOperations$UnsafeOperations.compareTo 
(Ljava/lang/Object;JILjava/lang/Object;JI)I
CompilerOracle: inline 
org/apache/cassandra/utils/FastByteOperations$UnsafeOperations.compareTo 
(Ljava/lang/Object;JILjava/nio/ByteBuffer;)I
CompilerOracle: inline 
org/apache/cassandra/utils/FastByteOperations$UnsafeOperations.compareTo 
(Ljava/nio/ByteBuffer;Ljava/nio/ByteBuffer;)I
CompilerOracle: inline org/apache/cassandra/utils/vint/VIntCoding.encodeVInt 
(JI)[B
INFO [main] 2018-03-09 08:52:39,287 YamlConfigurationLoader.java:89 - 
Configuration location: file:/opt/cassandra/conf/cassandra.yaml
INFO [main] 2018-03-09 08:52:39,568 Config.java:474 - Node 
configuration:[allocate_tokens_for_keyspace=null; 
authenticator=AllowAllAuthenticator; authorizer=AllowAllAuthorizer; 
auto_bootstrap=true; auto_snapshot=true; back_pressure_enabled=false; 
back_pressure_strategy=null; batch_size_fail_threshold_in_kb=50; 
batch_size_warn_threshold_in_kb=5; batchlog_replay_throttle_in_kb=1024; 
broadcast_address=null; broadcast_rpc_address=172.17.0.2; 
buffer_pool_use_heap_if_exhausted=true; cas_contention_timeout_in_ms=1000; 
cdc_enabled=false; cdc_free_space_check_interval_ms=250; 
cdc_raw_directory=/var/lib/cassandra/cdc_raw; cdc_total_space_in_mb=0; 
client_encryption_options=; cluster_name=Test Cluster; 
column_index_cache_size_in_kb=2; column_index_size_in_kb=64; 
commit_failure_policy=stop; commitlog_compression=null; 
commitlog_directory=/opt/cassandra/commitlog; 
commitlog_max_compression_buffers_in_pool=3; commitlog_periodic_queue_size=-1; 
commitlog_segment_size_in_mb=32; 

[jira] [Commented] (CAMEL-11823) [example] cdi-cassandrasql - nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 'Connection refused'

2018-03-09 Thread Andrea Cosentino (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392611#comment-16392611
 ] 

Andrea Cosentino commented on CAMEL-11823:
--

Actually this works fine because it is using the oscerd/cassandra latest image 
from docker hub. So we can close this.

> [example] cdi-cassandrasql - nodetool: Failed to connect to '127.0.0.1:7199' 
> - ConnectException: 'Connection refused'
> -
>
> Key: CAMEL-11823
> URL: https://issues.apache.org/jira/browse/CAMEL-11823
> Project: Camel
>  Issue Type: Sub-task
>  Components: examples
>Affects Versions: 2.20.0
>Reporter: Tomohisa Igarashi
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.21.0
>
>
> something wrong with docker image
> {code}
> $ docker exec -ti master_node /opt/cassandra/bin/nodetool status
> nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 
> 'Connection refused'.
> {code}
> {code}
> $ docker logs master_node
> *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
> *** Running /etc/rc.local...
> *** Booting runit daemon...
> *** Runit started as PID 8
> I'm starting cassandra
> tail: unrecognized file system type 0x794c7630 for ‘/var/log/syslog’. please 
> report this to bug-coreut...@gnu.org. reverting to polling
> Filling in the blanks inside cassandra.yaml
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:28 Killed  bin/cassandra -Rf
> I'm starting cassandra
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:93 Killed  bin/cassandra -Rf
> I'm starting cassandra
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:   159 Killed  bin/cassandra -Rf
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (CAMEL-12338) Add a Camel-Xchange Karaf feature

2018-03-09 Thread Andrea Cosentino (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-12338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-12338.
--
Resolution: Fixed

> Add a Camel-Xchange Karaf feature
> -
>
> Key: CAMEL-12338
> URL: https://issues.apache.org/jira/browse/CAMEL-12338
> Project: Camel
>  Issue Type: Task
>  Components: karaf
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.21.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (CAMEL-12338) Add a Camel-Xchange Karaf feature

2018-03-09 Thread Andrea Cosentino (JIRA)
Andrea Cosentino created CAMEL-12338:


 Summary: Add a Camel-Xchange Karaf feature
 Key: CAMEL-12338
 URL: https://issues.apache.org/jira/browse/CAMEL-12338
 Project: Camel
  Issue Type: Task
  Components: karaf
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
 Fix For: 2.21.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-11823) [example] cdi-cassandrasql - nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 'Connection refused'

2018-03-09 Thread Andrea Cosentino (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392586#comment-16392586
 ] 

Andrea Cosentino commented on CAMEL-11823:
--

Ok, I'll see if I'm able to do it today :)

> [example] cdi-cassandrasql - nodetool: Failed to connect to '127.0.0.1:7199' 
> - ConnectException: 'Connection refused'
> -
>
> Key: CAMEL-11823
> URL: https://issues.apache.org/jira/browse/CAMEL-11823
> Project: Camel
>  Issue Type: Sub-task
>  Components: examples
>Affects Versions: 2.20.0
>Reporter: Tomohisa Igarashi
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.21.0
>
>
> something wrong with docker image
> {code}
> $ docker exec -ti master_node /opt/cassandra/bin/nodetool status
> nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 
> 'Connection refused'.
> {code}
> {code}
> $ docker logs master_node
> *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
> *** Running /etc/rc.local...
> *** Booting runit daemon...
> *** Runit started as PID 8
> I'm starting cassandra
> tail: unrecognized file system type 0x794c7630 for ‘/var/log/syslog’. please 
> report this to bug-coreut...@gnu.org. reverting to polling
> Filling in the blanks inside cassandra.yaml
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:28 Killed  bin/cassandra -Rf
> I'm starting cassandra
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:93 Killed  bin/cassandra -Rf
> I'm starting cassandra
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:   159 Killed  bin/cassandra -Rf
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (CAMEL-12337) ignoreFileNotFoundOrPermissionError not work when folder not found

2018-03-09 Thread abccbaandy (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-12337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

abccbaandy updated CAMEL-12337:
---
Description: 
I tried something like these code, but when "notexist" folder not exist, it 
still give me exception
{code:java}
sftp://testserver:22/notexist?autoCreate=false=true
{code}

{code:java}
org.apache.camel.component.file.GenericFileOperationFailedException: Cannot 
list directory: notexist
at 
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
at 
org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
at 
org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
at 
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
at 
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
at 
org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.jcraft.jsch.SftpException: No such file
at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2873)
at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2225)
at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2242)
at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1592)
at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1553)
at 
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:641)
... 12 common frames omitted

{code}

ftp has the same issue.
{code:java}
org.apache.camel.component.file.GenericFileOperationFailedException: File 
operation failed: 550 The system cannot find the file specified. 
 Cannot change directory to: notexist. Code: 550
at 
org.apache.camel.component.file.remote.FtpOperations.doChangeDirectory(FtpOperations.java:790)
at 
org.apache.camel.component.file.remote.FtpOperations.changeCurrentDirectory(FtpOperations.java:768)
at 
org.apache.camel.component.file.remote.FtpConsumer.doPollDirectory(FtpConsumer.java:112)
at 
org.apache.camel.component.file.remote.FtpConsumer.pollDirectory(FtpConsumer.java:83)
at 
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
at 
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
at 
org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}


  was:
I tried something like these code, but when "notexist" folder not exist, it 
still give me exception
{code:java}
sftp://testserver:22/notexist?autoCreate=false=true
{code}
ftp has the same issue.

{code:java}
org.apache.camel.component.file.GenericFileOperationFailedException: Cannot 
list directory: notexist
at 
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
at 
org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
at 
org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
at 
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
at 
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
at 
org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at 

[jira] [Created] (CAMEL-12337) ignoreFileNotFoundOrPermissionError not work when folder not found

2018-03-09 Thread abccbaandy (JIRA)
abccbaandy created CAMEL-12337:
--

 Summary: ignoreFileNotFoundOrPermissionError not work when folder 
not found
 Key: CAMEL-12337
 URL: https://issues.apache.org/jira/browse/CAMEL-12337
 Project: Camel
  Issue Type: Bug
  Components: camel-ftp, camel-sftp
Affects Versions: 2.20.2
Reporter: abccbaandy


I tried something like these code, but when "notexist" folder not exist, it 
still give me exception
{code:java}
sftp://testserver:22/notexist?autoCreate=false=true
{code}
ftp has the same issue.

{code:java}
org.apache.camel.component.file.GenericFileOperationFailedException: Cannot 
list directory: notexist
at 
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:650)
at 
org.apache.camel.component.file.remote.SftpConsumer.doPollDirectory(SftpConsumer.java:118)
at 
org.apache.camel.component.file.remote.SftpConsumer.pollDirectory(SftpConsumer.java:80)
at 
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:124)
at 
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)
at 
org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.jcraft.jsch.SftpException: No such file
at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2873)
at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2225)
at com.jcraft.jsch.ChannelSftp._stat(ChannelSftp.java:2242)
at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1592)
at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1553)
at 
org.apache.camel.component.file.remote.SftpOperations.listFiles(SftpOperations.java:641)
... 12 common frames omitted

{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (CAMEL-12229) Some RabbitMQ channels are never started when target queue doesn't exist during component startup

2018-03-09 Thread Claus Ibsen (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-12229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-12229:

Fix Version/s: (was: 2.21.0)
   2.21.1

> Some RabbitMQ channels are never started when target queue doesn't exist 
> during component startup
> -
>
> Key: CAMEL-12229
> URL: https://issues.apache.org/jira/browse/CAMEL-12229
> Project: Camel
>  Issue Type: Bug
>  Components: camel-rabbitmq
>Affects Versions: 2.20.2
>Reporter: Vaclav Bystricky
>Priority: Minor
> Fix For: 2.20.3, 2.21.1
>
>
> Commit 8311af003ab888ca53a042ce5e9955b7cd5a845b reveals previously hidden bug.
> *Steps to reproduce*:
>  # configure rabbitmq consumer to connect to existing rabbitmq server but to 
> non existing queue Q1
>  # start rabbitmq consumer with several channels.
>  # after some time create Q1 on target rabbitmq server
> *Expected result*:
> All channels are connected to  rabbitmq server and can consume messages from 
> Q1
>  
> *Actual result*:
> All channels are connected to  rabbitmq server and but only one channel can 
> consume messages from Q1
>  
> Note:
> Separation on channels creating and their starting causes that channels are 
> not started in reconnect loop if  they were successfully created in 
> createConsumer but not started in startConsumers().
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-11823) [example] cdi-cassandrasql - nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 'Connection refused'

2018-03-09 Thread Claus Ibsen (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-11823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392564#comment-16392564
 ] 

Claus Ibsen commented on CAMEL-11823:
-

Andrea if you find some time you are welcome to look into this example, if not 
lets then move it to 2.21.1 release.

> [example] cdi-cassandrasql - nodetool: Failed to connect to '127.0.0.1:7199' 
> - ConnectException: 'Connection refused'
> -
>
> Key: CAMEL-11823
> URL: https://issues.apache.org/jira/browse/CAMEL-11823
> Project: Camel
>  Issue Type: Sub-task
>  Components: examples
>Affects Versions: 2.20.0
>Reporter: Tomohisa Igarashi
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 2.21.0
>
>
> something wrong with docker image
> {code}
> $ docker exec -ti master_node /opt/cassandra/bin/nodetool status
> nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 
> 'Connection refused'.
> {code}
> {code}
> $ docker logs master_node
> *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
> *** Running /etc/rc.local...
> *** Booting runit daemon...
> *** Runit started as PID 8
> I'm starting cassandra
> tail: unrecognized file system type 0x794c7630 for ‘/var/log/syslog’. please 
> report this to bug-coreut...@gnu.org. reverting to polling
> Filling in the blanks inside cassandra.yaml
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:28 Killed  bin/cassandra -Rf
> I'm starting cassandra
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:93 Killed  bin/cassandra -Rf
> I'm starting cassandra
> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file 
> bin/../logs/gc.log due to No such file or directory
> ./run: line 31:   159 Killed  bin/cassandra -Rf
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (CAMEL-12229) Some RabbitMQ channels are never started when target queue doesn't exist during component startup

2018-03-09 Thread Claus Ibsen (JIRA)

[ 
https://issues.apache.org/jira/browse/CAMEL-12229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16392563#comment-16392563
 ] 

Claus Ibsen commented on CAMEL-12229:
-

Can you possible provide some details on how to create Q1 on the rabbitmq 
server. We have an instance running via Docker and the integration test suite 
we have runs automatic and have the queues auto-created. But if we can find a 
way to reproduce this either auto or manually it would be good to help track 
down and implement a fix for this.

> Some RabbitMQ channels are never started when target queue doesn't exist 
> during component startup
> -
>
> Key: CAMEL-12229
> URL: https://issues.apache.org/jira/browse/CAMEL-12229
> Project: Camel
>  Issue Type: Bug
>  Components: camel-rabbitmq
>Affects Versions: 2.20.2
>Reporter: Vaclav Bystricky
>Priority: Minor
> Fix For: 2.20.3, 2.21.1
>
>
> Commit 8311af003ab888ca53a042ce5e9955b7cd5a845b reveals previously hidden bug.
> *Steps to reproduce*:
>  # configure rabbitmq consumer to connect to existing rabbitmq server but to 
> non existing queue Q1
>  # start rabbitmq consumer with several channels.
>  # after some time create Q1 on target rabbitmq server
> *Expected result*:
> All channels are connected to  rabbitmq server and can consume messages from 
> Q1
>  
> *Actual result*:
> All channels are connected to  rabbitmq server and but only one channel can 
> consume messages from Q1
>  
> Note:
> Separation on channels creating and their starting causes that channels are 
> not started in reconnect loop if  they were successfully created in 
> createConsumer but not started in startConsumers().
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)