You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by sharma_arun_se <ar...@gmail.com> on 2016/03/28 10:18:15 UTC
Camel ftp component : JSCH-0.1.44 Vs OpenSSH_6.6.1 issue: Leads to
error : com.jcraft.jsch.JSchException: Session.connect:
java.io.IOException: End of IO Stream Read
We are facing below mentioned error once our client applied latest changes
for SSH.
Is this problem with camel-ftp component? Do we need to change to latest
camel-ftp component 2.16? Do Fuse/servicemix version
(apache-servicemix-4.3.1-fuse-03-01) support camel 2.16?
Current Software version:
1. apache-servicemix-4.3.1-fuse-03-01
2. camel-ftp - 2.6.0
Connection String
-------------------
2016-03-21 12:27:01 | DEBUG | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | Using private
keyfile: C:/TEST/Fuse/client/SFTP/client_ppk.openssh
2016-03-21 12:27:01 | DEBUG | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | Using
StrickHostKeyChecking: no
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> Connecting
to xxx.xx.xx.xxx port 22
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> Connection
established
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> Remote
version string: SSH-2.0-OpenSSH_6.6.1
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> Local
version string: SSH-2.0-JSCH-0.1.44
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH ->
CheckCiphers:
aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,3des-ctr,arcfour,arcfour128,arcfour256
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> aes256-ctr
is not available.
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> aes192-ctr
is not available.
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> aes256-cbc
is not available.
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> aes192-cbc
is not available.
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> arcfour256
is not available.
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH ->
SSH_MSG_KEXINIT sent
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH ->
SSH_MSG_KEXINIT received
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> kex:
server->client aes128-ctr hmac-sha1 none
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> kex:
client->server aes128-ctr hmac-sha1 none
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH ->
SSH_MSG_KEX_DH_GEX_REQUEST(1024<1024<1024) sent
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH ->* expecting
SSH_MSG_KEX_DH_GEX_GROUP*
2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
| 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH ->
Disconnecting from xxx.xx.xx.xxx port 22
Error Stack trace:
2016-03-21 12:27:02 | ERROR | tenerContainer-1 | EndpointMessageListener
| 68 - org.apache.camel.camel-core - 2.6.0.fuse-01-09 | Caused by:
[org.apache.camel.component.file.GenericFileOperationFailedException -
Cannot connect to sftp://abc@xxx.xx.xx.xxx:22
org.apache.camel.component.file.GenericFileOperationFailedException: Cannot
connect to sftp://abc@xxx.xx.xx.xxx:22
at
org.apache.camel.component.file.remote.SftpOperations.connect(SftpOperations.java:113)[207:org.apache.camel.camel-ftp:2.6.0.fuse-01-09]
at
org.apache.camel.component.file.remote.RemoteFileProducer.connectIfNecessary(RemoteFileProducer.java:199)[207:org.apache.camel.camel-ftp:2.6.0.fuse-01-09]
at
org.apache.camel.component.file.remote.RemoteFileProducer.recoverableConnectIfNecessary(RemoteFileProducer.java:189)[207:org.apache.camel.camel-ftp:2.6.0.fuse-01-09]
at
org.apache.camel.component.file.remote.RemoteFileProducer.preWriteCheck(RemoteFileProducer.java:117)[207:org.apache.camel.camel-ftp:2.6.0.fuse-01-09]
at
org.apache.camel.component.file.GenericFileProducer.processExchange(GenericFileProducer.java:113)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.component.file.remote.RemoteFileProducer.process(RemoteFileProducer.java:50)[207:org.apache.camel.camel-ftp:2.6.0.fuse-01-09]
at
org.apache.camel.impl.converter.AsyncProcessorTypeConverter$ProcessorToAsyncProcessorBridge.process(AsyncProcessorTypeConverter.java:50)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:104)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:272)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.SendProcessor.process(SendProcessor.java:98)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:98)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:89)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:98)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:89)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:99)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:299)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:208)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.DefaultChannel.process(DefaultChannel.java:269)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.Pipeline.process(Pipeline.java:125)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.Pipeline.process(Pipeline.java:80)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:102)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:98)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:89)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:91)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:85)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
at
org.apache.camel.component.jms.EndpointMessageListener.onMessage(EndpointMessageListener.java:92)[208:org.apache.camel.camel-jms:2.6.0.fuse-01-09]
at
org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560)[95:org.springframework.jms:3.0.5.RELEASE]
at
org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498)[95:org.springframework.jms:3.0.5.RELEASE]
at
org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467)[95:org.springframework.jms:3.0.5.RELEASE]
at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325)[95:org.springframework.jms:3.0.5.RELEASE]
at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)[95:org.springframework.jms:3.0.5.RELEASE]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)[95:org.springframework.jms:3.0.5.RELEASE]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)[95:org.springframework.jms:3.0.5.RELEASE]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)[95:org.springframework.jms:3.0.5.RELEASE]
at java.lang.Thread.run(Unknown Source)[:1.6.0_23]
Caused by: com.jcraft.jsch.JSchException: Session.connect:
java.io.IOException: End of IO Stream Read
at
com.jcraft.jsch.Session.connect(Session.java:504)[206:org.apache.servicemix.bundles.jsch:0.1.44.1]
at
org.apache.camel.component.file.remote.SftpOperations.connect(SftpOperations.java:85)[207:org.apache.camel.camel-ftp:2.6.0.fuse-01-09]
... 42 more
-----
It seems client applied this:
kexalgorithms
diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1
macs umac-64@openssh.com,hmac-sha2-256,hmac-ripemd160,hmac-sha1
ciphers aes256-ctr,aes128-ctr "
-----
Regards,
Arun Kumar (sharma_arun_se)
Expert SOA (Fuse ESB, Camel, ActiveMQ, OSGi) and RESTful Solution Architect, Open Source Contributor.
linkedin: http://in.linkedin.com/in/aronkumar
twitter: https://twitter.com/#!/SharmaArunKumar
blog: http://techiesweek.blogspot.com/
Gtalk: arun.kaundal@gmail.com
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-ftp-component-JSCH-0-1-44-Vs-OpenSSH-6-6-1-issue-Leads-to-error-com-jcraft-jsch-JSchException-d-tp5779854.html
Sent from the Camel - Users mailing list archive at Nabble.com.
RE: Camel ftp component : JSCH-0.1.44 Vs OpenSSH_6.6.1 issue: Leads
to error : com.jcraft.jsch.JSchException: Session.connect:
java.io.IOException: End of IO Stream Read
Posted by sharma_arun_se <ar...@gmail.com>.
It works !
I changed from Fuse to Apache camel only solution.
I used latest Apache Camel ftp component version 2.17.0 and JSCH version:
0.1.53.
It works perfectly fine.
-----
Regards,
Arun Kumar (sharma_arun_se)
Expert SOA (Fuse ESB, Camel, ActiveMQ, OSGi) and RESTful Solution Architect, Open Source Contributor.
linkedin: http://in.linkedin.com/in/aronkumar
twitter: https://twitter.com/#!/SharmaArunKumar
blog: http://techiesweek.blogspot.com/
Gtalk: arun.kaundal@gmail.com
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-ftp-component-JSCH-0-1-44-Vs-OpenSSH-6-6-1-issue-Leads-to-error-com-jcraft-jsch-JSchException-d-tp5779854p5782445.html
Sent from the Camel - Users mailing list archive at Nabble.com.
RE: Camel ftp component : JSCH-0.1.44 Vs OpenSSH_6.6.1 issue: Leads
to error : com.jcraft.jsch.JSchException: Session.connect:
java.io.IOException: End of IO Stream Read
Posted by Hans Orbaan <ha...@docdata.eu>.
Hi,
The code I sent is for camel-ftp. It uses static methods to do those changes in JSch. But after looking at your stacktrace in a browser and not my email client I am sure you are facing different issues then we were.
What I did was hooking up my debugger and line for line walk with my thread through the connection procedure to find out what was going wrong. Starting in RemoteFileConsumer.
With kind regards,
Hans Orbaan
-----Oorspronkelijk bericht-----
Van: sharma_arun_se [mailto:arun.kaundal@gmail.com]
Verzonden: Wednesday 30 March 2016 15:15
Aan: users@camel.apache.org
Onderwerp: RE: Camel ftp component : JSCH-0.1.44 Vs OpenSSH_6.6.1 issue: Leads to error : com.jcraft.jsch.JSchException: Session.connect: java.io.IOException: End of IO Stream Read
Hi Claus, Hans,
We are using Camel FTP component (http://camel.apache.org/ftp2.html) to connect with FTP server.
We are not directly using "Jsch". I understand that Camel-ftp component make use of "Jsch" library internally. Do we need to change something or configure "Jsch" internally?
We started facing this SSH/Jsch issue once our customer applied latest fix for SSH.
-----
Regards,
Arun Kumar (sharma_arun_se)
Expert SOA (Fuse ESB, Camel, ActiveMQ, OSGi) and RESTful Solution Architect, Open Source Contributor.
linkedin: http://in.linkedin.com/in/aronkumar
twitter: https://twitter.com/#!/SharmaArunKumar
blog: http://techiesweek.blogspot.com/
Gtalk: arun.kaundal@gmail.com
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-ftp-component-JSCH-0-1-44-Vs-OpenSSH-6-6-1-issue-Leads-to-error-com-jcraft-jsch-JSchException-d-tp5779854p5780030.html
Sent from the Camel - Users mailing list archive at Nabble.com.
RE: Camel ftp component : JSCH-0.1.44 Vs OpenSSH_6.6.1 issue: Leads
to error : com.jcraft.jsch.JSchException: Session.connect:
java.io.IOException: End of IO Stream Read
Posted by sharma_arun_se <ar...@gmail.com>.
Hi Claus, Hans,
We are using Camel FTP component (http://camel.apache.org/ftp2.html) to
connect with FTP server.
We are not directly using "Jsch". I understand that Camel-ftp component make
use of "Jsch" library internally. Do we need to change something or
configure "Jsch" internally?
We started facing this SSH/Jsch issue once our customer applied latest fix
for SSH.
-----
Regards,
Arun Kumar (sharma_arun_se)
Expert SOA (Fuse ESB, Camel, ActiveMQ, OSGi) and RESTful Solution Architect, Open Source Contributor.
linkedin: http://in.linkedin.com/in/aronkumar
twitter: https://twitter.com/#!/SharmaArunKumar
blog: http://techiesweek.blogspot.com/
Gtalk: arun.kaundal@gmail.com
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-ftp-component-JSCH-0-1-44-Vs-OpenSSH-6-6-1-issue-Leads-to-error-com-jcraft-jsch-JSchException-d-tp5779854p5780030.html
Sent from the Camel - Users mailing list archive at Nabble.com.
RE: Camel ftp component : JSCH-0.1.44 Vs OpenSSH_6.6.1 issue: Leads
to error : com.jcraft.jsch.JSchException: Session.connect:
java.io.IOException: End of IO Stream Read
Posted by Hans Orbaan <ha...@docdata.eu>.
HI,
I am not sure if you have the same issue with Jsch as we had, but give this a go:
{code}
{
// change the order of PreferredAuthentications. put gssapi-with-mic as last
String preferredAuthentications = JSch.getConfig("PreferredAuthentications").replace("gssapi-with-mic", "") .replace(",,", ",");
preferredAuthentications = StringUtils.strip(preferredAuthentications, ",") + ",gssapi-with-mic";
JSch.setConfig("PreferredAuthentications", preferredAuthentications);
}
{code}
It simply makes gssapi-with-mic the last authentication that will be used when connecting. We had timeouts because of that authentication with a few servers...
With kind regards,
Hans Orbaan
-----Oorspronkelijk bericht-----
Van: Claus Ibsen [mailto:claus.ibsen@gmail.com]
Verzonden: Wednesday 30 March 2016 14:37
Aan: users@camel.apache.org
Onderwerp: Re: Camel ftp component : JSCH-0.1.44 Vs OpenSSH_6.6.1 issue: Leads to error : com.jcraft.jsch.JSchException: Session.connect: java.io.IOException: End of IO Stream Read
Give it a try. You can download the latest version and try it with Camel only as you desire to do.
Also mind that Camel does not do the actual SSH/JSCH implementation.
It may also be an issue with that library so upgrading it or reporting to that community may help.
On Wed, Mar 30, 2016 at 2:17 PM, sharma_arun_se <ar...@gmail.com> wrote:
> Hi Claus,
>
>
> Thanks for replying.
> We are planning to get rid of Fuse, ServiceMix and planning to use
> Camel only solution.
> Do you think Camel latest version have SSH/JSCH issue fixed. That is
> we do not face such issue with "Camel only" solution?
>
>
> I suppose, now I am asking question in right forum. This is what I found in:
> http://camel.apache.org/discussion-forums.html
>
> "Use the user forum for you Camel questions, and asking for help.
>
> Camel User Forum <-- Use this forum"
>
>
>
>
> -----
> Regards,
>
> Arun Kumar (sharma_arun_se)
>
> Expert SOA (Fuse ESB, Camel, ActiveMQ, OSGi) and RESTful Solution Architect, Open Source Contributor.
> linkedin: http://in.linkedin.com/in/aronkumar
> twitter: https://twitter.com/#!/SharmaArunKumar
> blog: http://techiesweek.blogspot.com/
> Gtalk: arun.kaundal@gmail.com
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-ftp-component-JSCH-0-1-44-Vs-O
> penSSH-6-6-1-issue-Leads-to-error-com-jcraft-jsch-JSchException-d-tp57
> 79854p5780023.html Sent from the Camel - Users mailing list archive at
> Nabble.com.
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel ftp component : JSCH-0.1.44 Vs OpenSSH_6.6.1 issue: Leads
to error : com.jcraft.jsch.JSchException: Session.connect:
java.io.IOException: End of IO Stream Read
Posted by Claus Ibsen <cl...@gmail.com>.
Give it a try. You can download the latest version and try it with
Camel only as you desire to do.
Also mind that Camel does not do the actual SSH/JSCH implementation.
It may also be an issue with that library so upgrading it or reporting
to that community may help.
On Wed, Mar 30, 2016 at 2:17 PM, sharma_arun_se <ar...@gmail.com> wrote:
> Hi Claus,
>
>
> Thanks for replying.
> We are planning to get rid of Fuse, ServiceMix and planning to use Camel
> only solution.
> Do you think Camel latest version have SSH/JSCH issue fixed. That is we do
> not face such issue with "Camel only" solution?
>
>
> I suppose, now I am asking question in right forum. This is what I found in:
> http://camel.apache.org/discussion-forums.html
>
> "Use the user forum for you Camel questions, and asking for help.
>
> Camel User Forum <-- Use this forum"
>
>
>
>
> -----
> Regards,
>
> Arun Kumar (sharma_arun_se)
>
> Expert SOA (Fuse ESB, Camel, ActiveMQ, OSGi) and RESTful Solution Architect, Open Source Contributor.
> linkedin: http://in.linkedin.com/in/aronkumar
> twitter: https://twitter.com/#!/SharmaArunKumar
> blog: http://techiesweek.blogspot.com/
> Gtalk: arun.kaundal@gmail.com
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-ftp-component-JSCH-0-1-44-Vs-OpenSSH-6-6-1-issue-Leads-to-error-com-jcraft-jsch-JSchException-d-tp5779854p5780023.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel ftp component : JSCH-0.1.44 Vs OpenSSH_6.6.1 issue: Leads
to error : com.jcraft.jsch.JSchException: Session.connect:
java.io.IOException: End of IO Stream Read
Posted by sharma_arun_se <ar...@gmail.com>.
Hi Claus,
Thanks for replying.
We are planning to get rid of Fuse, ServiceMix and planning to use Camel
only solution.
Do you think Camel latest version have SSH/JSCH issue fixed. That is we do
not face such issue with "Camel only" solution?
I suppose, now I am asking question in right forum. This is what I found in:
http://camel.apache.org/discussion-forums.html
"Use the user forum for you Camel questions, and asking for help.
Camel User Forum <-- Use this forum"
-----
Regards,
Arun Kumar (sharma_arun_se)
Expert SOA (Fuse ESB, Camel, ActiveMQ, OSGi) and RESTful Solution Architect, Open Source Contributor.
linkedin: http://in.linkedin.com/in/aronkumar
twitter: https://twitter.com/#!/SharmaArunKumar
blog: http://techiesweek.blogspot.com/
Gtalk: arun.kaundal@gmail.com
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-ftp-component-JSCH-0-1-44-Vs-OpenSSH-6-6-1-issue-Leads-to-error-com-jcraft-jsch-JSchException-d-tp5779854p5780023.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel ftp component : JSCH-0.1.44 Vs OpenSSH_6.6.1 issue: Leads
to error : com.jcraft.jsch.JSchException: Session.connect:
java.io.IOException: End of IO Stream Read
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
This is a very old version of Fuse ESB with older version of Apache Camel.
You can contact the vendor of that product to ask them about what
support offerings they have.
Here at Apache Camel we do not support the product of those vendors,
and the Camel version they use is also no longer maintained here.
All we can say here is upgrade.
PS: Do not send direct emails to Camel team users, as we say here
http://camel.apache.org/support.html
On Mon, Mar 28, 2016 at 10:18 AM, sharma_arun_se <ar...@gmail.com> wrote:
> We are facing below mentioned error once our client applied latest changes
> for SSH.
> Is this problem with camel-ftp component? Do we need to change to latest
> camel-ftp component 2.16? Do Fuse/servicemix version
> (apache-servicemix-4.3.1-fuse-03-01) support camel 2.16?
>
> Current Software version:
> 1. apache-servicemix-4.3.1-fuse-03-01
> 2. camel-ftp - 2.6.0
>
> Connection String
> -------------------
> 2016-03-21 12:27:01 | DEBUG | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | Using private
> keyfile: C:/TEST/Fuse/client/SFTP/client_ppk.openssh
> 2016-03-21 12:27:01 | DEBUG | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | Using
> StrickHostKeyChecking: no
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> Connecting
> to xxx.xx.xx.xxx port 22
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> Connection
> established
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> Remote
> version string: SSH-2.0-OpenSSH_6.6.1
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> Local
> version string: SSH-2.0-JSCH-0.1.44
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH ->
> CheckCiphers:
> aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,3des-ctr,arcfour,arcfour128,arcfour256
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> aes256-ctr
> is not available.
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> aes192-ctr
> is not available.
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> aes256-cbc
> is not available.
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> aes192-cbc
> is not available.
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> arcfour256
> is not available.
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH ->
> SSH_MSG_KEXINIT sent
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH ->
> SSH_MSG_KEXINIT received
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> kex:
> server->client aes128-ctr hmac-sha1 none
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH -> kex:
> client->server aes128-ctr hmac-sha1 none
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH ->
> SSH_MSG_KEX_DH_GEX_REQUEST(1024<1024<1024) sent
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH ->* expecting
> SSH_MSG_KEX_DH_GEX_GROUP*
> 2016-03-21 12:27:01 | INFO | tenerContainer-1 | SftpOperations
> | 207 - org.apache.camel.camel-ftp - 2.6.0.fuse-01-09 | JSCH ->
> Disconnecting from xxx.xx.xx.xxx port 22
>
> Error Stack trace:
> 2016-03-21 12:27:02 | ERROR | tenerContainer-1 | EndpointMessageListener
> | 68 - org.apache.camel.camel-core - 2.6.0.fuse-01-09 | Caused by:
> [org.apache.camel.component.file.GenericFileOperationFailedException -
> Cannot connect to sftp://abc@xxx.xx.xx.xxx:22
> org.apache.camel.component.file.GenericFileOperationFailedException: Cannot
> connect to sftp://abc@xxx.xx.xx.xxx:22
> at
> org.apache.camel.component.file.remote.SftpOperations.connect(SftpOperations.java:113)[207:org.apache.camel.camel-ftp:2.6.0.fuse-01-09]
> at
> org.apache.camel.component.file.remote.RemoteFileProducer.connectIfNecessary(RemoteFileProducer.java:199)[207:org.apache.camel.camel-ftp:2.6.0.fuse-01-09]
> at
> org.apache.camel.component.file.remote.RemoteFileProducer.recoverableConnectIfNecessary(RemoteFileProducer.java:189)[207:org.apache.camel.camel-ftp:2.6.0.fuse-01-09]
> at
> org.apache.camel.component.file.remote.RemoteFileProducer.preWriteCheck(RemoteFileProducer.java:117)[207:org.apache.camel.camel-ftp:2.6.0.fuse-01-09]
> at
> org.apache.camel.component.file.GenericFileProducer.processExchange(GenericFileProducer.java:113)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.component.file.remote.RemoteFileProducer.process(RemoteFileProducer.java:50)[207:org.apache.camel.camel-ftp:2.6.0.fuse-01-09]
> at
> org.apache.camel.impl.converter.AsyncProcessorTypeConverter$ProcessorToAsyncProcessorBridge.process(AsyncProcessorTypeConverter.java:50)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:104)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:272)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:98)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:98)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:89)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:98)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:89)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:99)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:299)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:208)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.DefaultChannel.process(DefaultChannel.java:269)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.Pipeline.process(Pipeline.java:125)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.Pipeline.process(Pipeline.java:80)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:102)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:98)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:89)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:91)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:85)[68:org.apache.camel.camel-core:2.6.0.fuse-01-09]
> at
> org.apache.camel.component.jms.EndpointMessageListener.onMessage(EndpointMessageListener.java:92)[208:org.apache.camel.camel-jms:2.6.0.fuse-01-09]
> at
> org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560)[95:org.springframework.jms:3.0.5.RELEASE]
> at
> org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498)[95:org.springframework.jms:3.0.5.RELEASE]
> at
> org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467)[95:org.springframework.jms:3.0.5.RELEASE]
> at
> org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325)[95:org.springframework.jms:3.0.5.RELEASE]
> at
> org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)[95:org.springframework.jms:3.0.5.RELEASE]
> at
> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)[95:org.springframework.jms:3.0.5.RELEASE]
> at
> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)[95:org.springframework.jms:3.0.5.RELEASE]
> at
> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)[95:org.springframework.jms:3.0.5.RELEASE]
> at java.lang.Thread.run(Unknown Source)[:1.6.0_23]
> Caused by: com.jcraft.jsch.JSchException: Session.connect:
> java.io.IOException: End of IO Stream Read
> at
> com.jcraft.jsch.Session.connect(Session.java:504)[206:org.apache.servicemix.bundles.jsch:0.1.44.1]
> at
> org.apache.camel.component.file.remote.SftpOperations.connect(SftpOperations.java:85)[207:org.apache.camel.camel-ftp:2.6.0.fuse-01-09]
> ... 42 more
>
>
> -----
> It seems client applied this:
> kexalgorithms
> diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1
> macs umac-64@openssh.com,hmac-sha2-256,hmac-ripemd160,hmac-sha1
> ciphers aes256-ctr,aes128-ctr "
>
>
>
> -----
> Regards,
>
> Arun Kumar (sharma_arun_se)
>
> Expert SOA (Fuse ESB, Camel, ActiveMQ, OSGi) and RESTful Solution Architect, Open Source Contributor.
> linkedin: http://in.linkedin.com/in/aronkumar
> twitter: https://twitter.com/#!/SharmaArunKumar
> blog: http://techiesweek.blogspot.com/
> Gtalk: arun.kaundal@gmail.com
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-ftp-component-JSCH-0-1-44-Vs-OpenSSH-6-6-1-issue-Leads-to-error-com-jcraft-jsch-JSchException-d-tp5779854.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Camel ftp component : JSCH-0.1.44 Vs OpenSSH_6.6.1 issue: Leads
to error : com.jcraft.jsch.JSchException: Session.connect:
java.io.IOException: End of IO Stream Read
Posted by sharma_arun_se <ar...@gmail.com>.
Hi,
Do let me know, if you need additional information.
-----
Regards,
Arun Kumar (sharma_arun_se)
Expert SOA (Fuse ESB, Camel, ActiveMQ, OSGi) and RESTful Solution Architect, Open Source Contributor.
linkedin: http://in.linkedin.com/in/aronkumar
twitter: https://twitter.com/#!/SharmaArunKumar
blog: http://techiesweek.blogspot.com/
Gtalk: arun.kaundal@gmail.com
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-ftp-component-JSCH-0-1-44-Vs-OpenSSH-6-6-1-issue-Leads-to-error-com-jcraft-jsch-JSchException-d-tp5779854p5779939.html
Sent from the Camel - Users mailing list archive at Nabble.com.