I am running into weired situation while trying to do a sftp from an 
application 
deployed on weblogic.While running same application wrapped in a command line 
java program works.

Here is the environment details......

Server :  Unix
Jsch Client Version:  1.42
JDK Version : JDK1.5_12

When I try to do sftp a file from application deployed on weblogic 9 I get this 
error.

2010-11-17 14:48:58,762 [[ACTIVE] ExecuteThread: '0' for queue: 
'weblogic.kernel.Default (self-tuning)']   ERROR xxx.EDABuilder:? - 
com.jcraft.jsch.JSchException: Session.connect: java.io.IOException: invalid 
data

Here is the output from jsch.Logger: >>>>>

Connecting to 10.10.127.42 port 2222
Connection established
Remote version string: SSH-2.0-Sun_SSH_1.1.3
Local version string: SSH-2.0-JSCH-0.1.42
CheckCiphers: 
aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,3des-ctr,arcfour,arcfour128,arcfour256

aes256-ctr is not available.
aes192-ctr is not available.
aes256-cbc is not available.
aes192-cbc is not available.
arcfour256 is not available.
SSH_MSG_KEXINIT sent
SSH_MSG_KEXINIT received
kex: server->client aes128-ctr hmac-md5 none
kex: client->server aes128-ctr hmac-md5 none
SSH_MSG_KEXDH_INIT sent
expecting SSH_MSG_KEXDH_REPLY
ssh_rsa_verify: signature true
Permanently added '10.10.127.42' (RSA) to the list of known hosts.
SSH_MSG_NEWKEYS sent
SSH_MSG_NEWKEYS received
SSH_MSG_SERVICE_REQUEST sent
Disconnecting from 10.10.127.42 port 2222


Here is the server log....

debug1: Server will not fork when  running in debugging mode.
Connection from 10.10.127.42 port  48204
debug1: Client protocol version 2.0;  client software version JSCH-0.1.42
debug1: no match:  JSCH-0.1.42
debug1: Enabling compatibility mode  for protocol 2.0
debug1: Local version string  SSH-2.0-Sun_SSH_1.1.3
monitor debug1: list_hostkey_types:  ssh-rsa,ssh-dss
debug2: Waiting for  monitor
monitor debug2: Monitor pid 6038,  unprivileged child pid 6044
debug2: Monitor signalled  readiness
monitor debug1: reading the context  from the child
debug1: use_engine is  'yes'
debug1: pkcs11 engine initialized,  now setting it as default for RSA, DSA, and 
symmetric  ciphers
debug1: pkcs11 engine initialization  complete
debug1: list_hostkey_types:  ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:  
diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit:  ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:  
aes128-ctr,aes128-cbc,arcfour,3des-cbc,blowfish-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc

debug2: kex_parse_kexinit:  
aes128-ctr,aes128-cbc,arcfour,3des-cbc,blowfish-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc

debug2: kex_parse_kexinit:  hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:  hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:  none,zlib
debug2: kex_parse_kexinit:  none,zlib
debug2: kex_parse_kexinit:  en-CA,en-US,es-MX,es,fr,fr-CA,i-default
debug2: kex_parse_kexinit:  en-CA,en-US,es-MX,es,fr,fr-CA,i-default
debug2: kex_parse_kexinit:  first_kex_follows 0
debug2: kex_parse_kexinit: reserved  0
debug2: GSS-API Mechanism encoded as  toWM5Slw5Ew8Mqkay+al2g==
debug1: SSH2_MSG_KEXINIT  sent
debug3: kex_reset_dispatch -- should  we dispatch_set(KEXINIT) here? 0 && !0
debug1: SSH2_MSG_KEXINIT  received
debug2: kex_parse_kexinit:  
gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1

debug2: kex_parse_kexinit:  ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:  
aes128-ctr,aes128-cbc,arcfour,3des-cbc,blowfish-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc

debug2: kex_parse_kexinit:  
aes128-ctr,aes128-cbc,arcfour,3des-cbc,blowfish-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc

debug2: kex_parse_kexinit:  hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:  hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:  none,zlib
debug2: kex_parse_kexinit:  none,zlib
debug2: kex_parse_kexinit:  en-CA,en-US,es-MX,es,fr,fr-CA,i-default
debug2: kex_parse_kexinit:  en-CA,en-US,es-MX,es,fr,fr-CA,i-default
debug2: kex_parse_kexinit:  first_kex_follows 0
debug2: kex_parse_kexinit: reserved  0
debug2: kex_parse_kexinit:  
diffie-hellman-group1-sha1,diffie-hellman-group-exchange-sha1
debug2: kex_parse_kexinit:  ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:  aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc
debug2: kex_parse_kexinit:  aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc
debug2: kex_parse_kexinit:  hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:  hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:  none
debug2: kex_parse_kexinit:  none
debug2:  kex_parse_kexinit:
debug2:  kex_parse_kexinit:
debug2: kex_parse_kexinit:  first_kex_follows 0
debug2: kex_parse_kexinit: reserved  0
debug2: mac_init: found  hmac-md5
debug1: kex: client->server  aes128-ctr hmac-md5 none
debug2: mac_init: found  hmac-md5
debug1: kex: server->client  aes128-ctr hmac-md5 none
debug1: Peer sent proposed langtags,  ctos:
debug1: Peer sent proposed langtags,  stoc:
debug1: We proposed langtags, ctos:  en-CA,en-US,es-MX,es,fr,fr-CA,i-default
debug1: We proposed langtags, stoc:  en-CA,en-US,es-MX,es,fr,fr-CA,i-default
debug1: dh_gen_key: priv key bits  set: 131/256
debug1: bits set:  514/1024
debug1: expecting  SSH2_MSG_KEXDH_INIT
debug1: bits set:  517/1024
debug2:  kex_derive_keys
debug3: kex_reset_dispatch -- should  we dispatch_set(KEXINIT) here? 0 && !0
debug1: newkeys: mode  1
debug1: set_newkeys: setting new  keys for 'out' mode
debug3: aes-128-ctr NID  found
debug1: SSH2_MSG_NEWKEYS  sent
debug1: expecting  SSH2_MSG_NEWKEYS
debug1: newkeys: mode  0
debug1: set_newkeys: setting new  keys for 'in' mode
debug3: aes-128-ctr NID  found
debug1: SSH2_MSG_NEWKEYS  received
debug1: KEX  done
Disconnecting:  Bad packet length.
debug1: Calling cleanup  0x200e4(0x92058)
debug1: Calling cleanup  0x465d8(0x0)
monitor debug1: child closed the  communication pipe before user auth was 
finished
monitor debug1: Calling cleanup  0x465d8(0x0)
monitor debug1: Calling cleanup  0x465d8(0x0)


Any ideas what might be happening? Any suggestions and help would be much 
appreciated...


      
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
JSch-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jsch-users

Reply via email to