unexpected disconnect

[Maynard]

Thanks for the debugging leads. Here is the additional info, displayed in
the console at disconnect.

** 07:20:13.537 SSH2Listener : 'connect from: 127.0.0.1:64036 on
127.0.0.1:105,new ch. #1'
** 07:20:13.662 SSH2Transport.disconnectInternal() : 'disconnect: I/O
error: Connection reset'
** 07:20:13.662 SSH2Transport.disconnectInternal() : 'error writing
disconnect msg: com.mindbright.ssh2.bc: Couldn't write packet of type
MSG_DISCONNECT'
** 07:20:13.662 SSH2Transport.transportTransmitLoop() : 'stopping'
** 07:20:13.670 SSH2SessionChannel : 'session (ch. #0) exit with status -1'
** 07:20:13.670 SSH2StreamChannel : 'exiting ch. #0 (session) receiver,
535 bytes rx'
** 07:20:13.685 SSH2Channel : 'closing ch. #0 (session)'
** 07:20:13.685 SSH2Listener : 'stopping listener on 127.0.0.1:105'
** 07:20:13.693 SSH2Channel : 'closing ch. #1 (direct-tcpip)'
** 07:20:13.693 SSH2Listener : 'stopping listener on 127.0.0.1:104'
** 07:20:13.693 SSH2Transport.transportReceiveLoop() : 'stopping'
** 07:20:13.693 SSH2Listener : 'stopping listener on 127.0.0.1:103'
** 07:20:13.693 SSH2Listener : 'stopping listener on 127.0.0.1:102'
** 07:20:13.693 SSH2StreamChannel : 'exiting ch. #0 (session) transmitter,
0 bytes tx'



Per Allansson said:
> try starting MT with:
>
>    java -jar mindterm.jar --D --v
>
> which should provide you with more debugging info. The error
> message you get is not uncommon and is usually not a problem
> with MT or the JVM - it is probably caused by the connection
> being closed down for some reason (network failure, firewall,
> anti-virus software or something similar).



> Maynard wrote:
>> Hi.
>>
>> When MindTerm client disconnects unexpectedly (definitely NOT dropped by
>> remote host or timeout), the JVM console records the following:
>>
>> ** 15:19:49.923 SSH2Transport.disconnectInternal() : 'disconnect: I/O
>> error: Connection reset'
>>
>> ** 15:19:49.939 SSH2Transport.disconnectInternal() : 'error writing
>> disconnect msg: com.mindbright.ssh2.bc: Couldn't write packet of type
>> MSG_DISCONNECT'
>>
>> Does this issue reside with MindTerm or with the JVM?
>>
>> Is there a way I can set --debug mode (in MindTerm or JVM) or otherwise
>> generate more information about the unexpected disconnect?
>>
>> Thanks,
>> --Maynard
>>
>> java version "1.4.1_07"
>> Java(TM) 2 Runtime Environment, Standard Edition
>> (1.4.1_07-gcd-b42-20040728)
>> Java HotSpot(TM) Client VM (1.4.1_07-fcs-gcd-b42-20040728, mixed mode)
>>
>> _______________________________________________
>> Mindterm-users mailing list
>> Mindterm-users at mindterm.appgate.com
>> http://mindterm.appgate.com/mailman/listinfo/mindterm-users
>>
>> 
>>
>


!DSPAM:41a33dcb212393160413364!