WSAECONNRESET Connection reset by peer every 10 min
We are getting an error WSAECONNRESET Connection reset by peer every 10 min. We are running SAP on windows Small Business Server.
If I log in on server or within LAN it is working file without any problem. When we use WAN or outside network and connect SAP using SAP router it is giving an error of Connection reset by peer every 10 min.
I have reviewed OSS 155147 - WinNT: Connection reset by peer, 107407 - Win95: Connection Reset by Peer and 500235 - Network Diagnosis with NIPING without any success. I have played with registry parameters as per OSS 413330.
Could any one explain how to resolve this problem?
Thanks in advance...
> But the consistency is It reset exactly every 10 min.
Maybe you connection (whatever technical kind it is) resets connections all 10 minutes, maybe a firewall tears down the connection after that time... without knowing anything about the infrastructure I can just guess.
If the system is running internally fine without any interruptions then it's not a problem of the SAP system.
Markus
Similar Messages
-
WSAECONNRESET:connection reset by peer
If SAP login is left idle for 10/12 minutes it logos out with this message.
*HOP connection to partner broken
WSAECONNRESET:connection reset by peer
do you want to see the detailed error description*
+HOP: connection to partner broken
time thurs aug
component NI(network interface)
release 640
version 37
module ninti.c
line 792
method nipread
return code -6
system call recv
error no 10054
error text WSAECONNRESET:connectionr reset by peer
counter 1+Change it to 3600..... and check whether you getting the same message before 1 hour.
Yes , Markus is right... WSAECONNRESET can not come with auto logout settings.
Check SM21 entries when you are getting this error. Is this issue being faced by all the users?
Edited by: Anindya Bose on Aug 21, 2009 5:23 PM -
ERROR disp+work.exe WSAECONNRESET: Connection reset by peer
Hi,
I've a Netweaver 2004s installed on Windows 2003 Server and SQL Server. The name of the amchine is solution and the domain where it's on is grupotec.local, so when I start it from SAP MMC, the dispatcher appears with yellow colour. When I read the trace, an error appears:
Wed Apr 16 18:10:18 2008
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4361]
ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1484
(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:1460) [nixxi.cpp 4361]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=4912)
ERROR => DpProcKill: kill failed [dpntdisp.c 371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
***LOG Q0I=> NiPGetHostByName: hostname 'solution.gruposap.local' not found: gethostbyname (11004: WSANO_DATA: Valid name, no data record of requested type) [ninti.c 320]
Wed Apr 16 18:10:19 2008
MBUF state ACTIVE
DpModState: change server state from STARTING to ACTIVE
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Wed Apr 16 18:10:20 2008
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Wed Apr 16 18:10:21 2008
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Wed Apr 16 18:10:22 2008
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
Wed Apr 16 18:10:23 2008
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
The abap stack works fine, I'm able to logon and work with the system BUT the java stack doesn't work. I've looking for this error in SAP Notes page, SDN portal,... also I've revised:
-file host, located C:\WINDOWS\system32\drivers\etc contains a line 192.168.100.42 solution.grupotec.local SAPTRANSHOST and the last line of this file is in blank
this machine was in domain 'solution.gruposap.local' and now is in the domain solution.grupotec.local
In order to solve it, I've chequed:
-SQL Server 2003 is up and running
-I've taken out and in the machine from the domain
-I've turned off the machine in order it refresh the new domain(solution.grupotec.local )
-Filesystem has enough free space
-I've updated SAP Kernel
Please could you help me?
Thanks and regardsHi,
full computer name:solution.grupotec.local
domain:grupotec.local
SID:SOL
DBSID:SOLUTION
number SOL instances:
C:\usr\sap\SOL\DVEBMGS01
C:\usr\sap\SOL\SCS00
DEFAULT.PFL:
j2ee/dbtype mss
j2ee/dbhost SOLUTION
j2ee/dbname SOL
SAPSYSTEMNAME SOL
SAPGLOBALHOST SOLUTION
j2ee/scs/host SOLUTION
j2ee/scs/system 00
j2ee/ms/host SOLUTION
j2ee/ms/port 3900
rdisp/bufrefmode sendoff,exeoff
rdisp/mshost SOLUTION
rdisp/msserv sapmsSOL
rdisp/msserv_internal 3901
login/system_client 001
SAPDBHOST SOLUTION
dbms/type mss
dbs/mss/server SOLUTION
dbs/mss/dbname SOL
dbs/mss/schema sol
About message server:
in the file services(C:\WINDOWS\system32\drivers\etc):
sapmsSOL 3601/tcp # SAP System Messaging Service Port
and when I type command netstat:
C:\Documents and Settings\soladm.SOLUTION>netstat -a
Active Connections
Proto Local Address Foreign Address State
TCP solution:epmap solution.grupotec.local:0 LISTENING
TCP solution:microsoft-ds solution.grupotec.local:0 LISTENING
TCP solution:1031 solution.grupotec.local:0 LISTENING
TCP solution:ms-sql-s solution.grupotec.local:0 LISTENING
TCP solution:sapdp00 solution.grupotec.local:0 LISTENING
TCP solution:sapmsSOL solution.grupotec.local:0 LISTENING
TCP solution:3901 solution.grupotec.local:0 LISTENING
and log for message server, the file C:\usr\sap\SOL\DVEBMGS01\work\dev_ms:
trc file: "dev_ms", trc level: 1, release: "700"
[Thr 3528] Fri Apr 18 12:28:32 2008
[Thr 3528] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
systemid 560 (PC with Windows NT)
relno 7000
patchlevel 0
patchno 133
intno 20050900
make: multithreaded, Unicode, optimized
pid 144
[Thr 3528] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 144) [msxxserv.c 1824]
[Thr 3528] load acl file = C:\usr\sap\SOL\SYS\global\ms_acl_info.DAT
[Thr 3528] MsGetOwnIpAddr: my host addresses are :
[Thr 3528] 1 : [192.168.100.42] solution.grupotec.local (HOSTNAME)
[Thr 3528] 2 : [127.0.0.1] solution.grupotec.local (LOCALHOST)
[Thr 3528] MsHttpInit: full qualified hostname = solution.grupotec.local
[Thr 3528] HTTP logging is switch off
[Thr 3528] set HTTP state to LISTEN
[Thr 3528] MsHttpOwnDomain: own domain[1] = grupotec.local
[Thr 3528] ms/icf_info_server : deleted
[Thr 3528] *** I listen to port sapmsSOL (3601) ***
[Thr 3528] *** I listen to internal port 3901 (3901) ***
[Thr 3528] *** HTTP port 8101 state LISTEN ***
[Thr 3528] CUSTOMER KEY: >M0059840091<
[Thr 3528] Fri Apr 18 12:28:55 2008
[Thr 3528] MsHttpReadUrl2: H-1 url = /sap/public/icf_info/logon_groups (403 Forbidden)
[Thr 3528] MsHttpReadUrl2: H-1 url = /sap/public/icf_info/urlprefix (403 Forbidden)
Edited by: Raul Aguilar on Apr 18, 2008 1:21 PM -
10054: WSAECONNRESET: Connection reset by peer
Good Morning everybody.
We are having several problems with this issue. We are implementing SAP NetWeaver, and on the test fields, on the connection to sandbox, only 3 machines are presenting this issue. We already implement the solution adding on the Registry a key on the route HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCPIP\Parameters; here,we add the DWORD key 'TcpMaxDataRetransmissions', and for the day it works, but the problem appears at next day.
Please help us to find a definitive solution on the matter.Hi
See this thread
Re: J2EE Shutdown - DpProcKill: kill failed
Kind Regards
Mukesh -
JCO - Connection reset by peer - after 5 minute timeout
Hello
We're using SUP with the JCO Connector. This has been working flawlessly since project inception. Now, after switching to a new data center (Windows Server 2008 Server Enterprise Edition, SP2 on VMWare) we're observing a mysterious behavior with timeouts of idle connections. I hope someone in this forum knows what this might be.
JCO connections originate from SUP servers. When such connections are idle for more than 5 minutes they get disconnected from SAP -- this is in agreement with SAP timeout parameter of 300 seconds.
On our new systems we noticed that requests sent 5min+ (after timeout) show following error:
Thread-8 [22:08:55:343]: [JNI-LAYER] RFC.nativeExecute() before RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeExecute() after RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88) = RFC_SYS_EXCEPTION
Thread-8 [22:08:55:344]: [JAV-LAYER] JCO.Client.execute (Z_U_ONEMOBILE_SWO_SEARCH) threw a NON-ABAP exception: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: CPIC-CALL: 'CMRCV : rc=20
ERROR connection to partner '---removed!---:3299'
broken
TIME Fri Feb 11 18:08:55 201
RELEASE 710
COMPONENT NI (network interface)
VERSION 39
RC -6
MODULE nixxi.cpp
LINE 4448
DETAIL NiIWrite: P=161.88.23.170:3299; L=0.0.0.0:49730
SYSTEM CALL WSASend
ERRNO 10054
ERRNO TEXT WSAECONNRESET: Connection reset by peer
COUNTER 3
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() enter, [SUCCESS]
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() before RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() after RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() with rc = RFC_OK leave, [SUCCESS]
Our suspicion is that the JCO client doesn't notice the fact that it gets disconnected. We used Network Monitor 3.4 to look at network traffic. Indeed, after 5 minutes the client gets a single frame (with reset flag) and no acknowledgement goes back.
What could this be?
We use
JCO 2.1.8 AMD 64-bit (contains librfc 6.40) and
JCO 2.1.9 AMD 64-bit (contains librfc 6.40) but replaced this with librfc 7.10 (after seeing Note 825494). Behavior was exactly the same. We did confirm in jco/rfc trace that those versions were actually used.
Any ideas?
Thanks and regards
Edited by: B. Gottipati on Feb 14, 2011 9:17 PMHello
We're using SUP with the JCO Connector. This has been working flawlessly since project inception. Now, after switching to a new data center (Windows Server 2008 Server Enterprise Edition, SP2 on VMWare) we're observing a mysterious behavior with timeouts of idle connections. I hope someone in this forum knows what this might be.
JCO connections originate from SUP servers. When such connections are idle for more than 5 minutes they get disconnected from SAP -- this is in agreement with SAP timeout parameter of 300 seconds.
On our new systems we noticed that requests sent 5min+ (after timeout) show following error:
Thread-8 [22:08:55:343]: [JNI-LAYER] RFC.nativeExecute() before RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeExecute() after RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88) = RFC_SYS_EXCEPTION
Thread-8 [22:08:55:344]: [JAV-LAYER] JCO.Client.execute (Z_U_ONEMOBILE_SWO_SEARCH) threw a NON-ABAP exception: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: CPIC-CALL: 'CMRCV : rc=20
ERROR connection to partner '---removed!---:3299'
broken
TIME Fri Feb 11 18:08:55 201
RELEASE 710
COMPONENT NI (network interface)
VERSION 39
RC -6
MODULE nixxi.cpp
LINE 4448
DETAIL NiIWrite: P=161.88.23.170:3299; L=0.0.0.0:49730
SYSTEM CALL WSASend
ERRNO 10054
ERRNO TEXT WSAECONNRESET: Connection reset by peer
COUNTER 3
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() enter, [SUCCESS]
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() before RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() after RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() with rc = RFC_OK leave, [SUCCESS]
Our suspicion is that the JCO client doesn't notice the fact that it gets disconnected. We used Network Monitor 3.4 to look at network traffic. Indeed, after 5 minutes the client gets a single frame (with reset flag) and no acknowledgement goes back.
What could this be?
We use
JCO 2.1.8 AMD 64-bit (contains librfc 6.40) and
JCO 2.1.9 AMD 64-bit (contains librfc 6.40) but replaced this with librfc 7.10 (after seeing Note 825494). Behavior was exactly the same. We did confirm in jco/rfc trace that those versions were actually used.
Any ideas?
Thanks and regards
Edited by: B. Gottipati on Feb 14, 2011 9:17 PM -
Mac Clients are running 10.9.2 Mavericks.
Client is Microsoft Remote Desktop 8.05.
Clients are mixed in how they connect to the Windows 2008 R2 server, some
are on Wifi some are on Wired Ethernet.
If you connect to the Server through the RD Client, and get on you work
and if you then say go idle ( still connected but not doing anything such as
printing from the Server or in an Application on the Server) then after 20 mins it
(the client) throws up a "Connection reset by Peer" error.
You click OK, and then it breaks connection. You can however reconnect without issue.
We have currently about six users who are using the RD Connection to access QuickBooks on
this 2008 R2 server. Four are on Macs and get the errors. Two are on PCs and do not get the errors.
Here is the log file from one of the Macs that had the error:
[2014-Apr-07 10:34:07] RDP (0): Server shows cursor
[2014-Apr-07 10:34:09] RDP (0): Server hides cursor
[2014-Apr-07 10:34:21] RDP (0): Server shows cursor
[2014-Apr-07 10:34:22] RDP (0): Server hides cursor
[2014-Apr-07 10:34:25] RDP (0): Server shows cursor
[2014-Apr-07 11:00:29] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Apr-07 11:00:29] RDP (0): ------ END ACTIVE CONNECTION ------
[2014-Apr-07 11:00:29] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
User Message : Failed to read from socket: -1
[2014-Apr-07 11:02:35] RDP (0): Final rdp configuration used: screen mode id:i:2
use multimon:i:1
session bpp:i:24
full address:s:192.168.16.x
audiomode:i:0
username:s:m
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com:1
bookmarktype:i:3
use redirection server name:i:0
[2014-Apr-07 11:02:35] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Apr-07 11:02:35] RDP (0): lo0 af=18 addr= netmask=
[2014-Apr-07 11:02:35] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Apr-07 11:02:35] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2014-Apr-07 11:02:35] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-07 11:02:35] RDP (0): gif0 af=18 addr= netmask=
[2014-Apr-07 11:02:35] RDP (0): stf0 af=18 addr= netmask=
[2014-Apr-07 11:02:35] RDP (0): en0 af=18 addr= netmask=
[2014-Apr-07 11:02:35] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-07 11:02:35] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
[2014-Apr-07 11:02:35] RDP (0): en1 af=18 addr= netmask=
[2014-Apr-07 11:02:35] RDP (0): en4 af=18 addr= netmask=
[2014-Apr-07 11:02:35] RDP (0): en3 af=18 addr= netmask=
[2014-Apr-07 11:02:35] RDP (0): p2p0 af=18 addr= netmask=
[2014-Apr-07 11:02:35] RDP (0): bridge0 af=18 addr= netmask=
[2014-Apr-07 11:02:35] RDP (0): --- END INTERFACE LIST ---
[2014-Apr-07 11:02:35] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Apr-07 11:02:35] RDP (0): client version: 8.0.24428
[2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Apr-07 11:02:35] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
[2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-07 11:02:35] RDP (0): Server supports RAIL
[2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-07 11:02:35] RDP (0): Server supports RAIL
[2014-Apr-07 11:02:35] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-07 11:09:38] RDP (0): Server hides cursor
[2014-Apr-07 11:09:38] RDP (0): Server shows cursor
[2014-Apr-07 11:09:38] RDP (0): Server hides cursor
[2014-Apr-07 11:09:38] RDP (0): Server shows cursor
[2014-Apr-07 11:09:38] RDP (0): Server hides cursor
[2014-Apr-07 11:09:38] RDP (0): Server shows cursor
[2014-Apr-07 12:16:31] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Apr-07 12:16:31] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
User Message : Failed to read from socket: -1
[2014-Apr-07 12:16:31] RDP (0): ------ END ACTIVE CONNECTION ------
[2014-Apr-07 12:21:42] RDP (0): Final rdp configuration used: screen mode id:i:2
use multimon:i:1
session bpp:i:24
full address:s:192.168.16.x
audiomode:i:0
username:s:m
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com:1
bookmarktype:i:3
use redirection server name:i:0
[2014-Apr-07 12:21:42] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Apr-07 12:21:42] RDP (0): lo0 af=18 addr= netmask=
[2014-Apr-07 12:21:42] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Apr-07 12:21:42] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2014-Apr-07 12:21:42] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-07 12:21:42] RDP (0): gif0 af=18 addr= netmask=
[2014-Apr-07 12:21:42] RDP (0): stf0 af=18 addr= netmask=
[2014-Apr-07 12:21:42] RDP (0): en0 af=18 addr= netmask=
[2014-Apr-07 12:21:42] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-07 12:21:42] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
[2014-Apr-07 12:21:42] RDP (0): en1 af=18 addr= netmask=
[2014-Apr-07 12:21:42] RDP (0): en4 af=18 addr= netmask=
[2014-Apr-07 12:21:42] RDP (0): en3 af=18 addr= netmask=
[2014-Apr-07 12:21:42] RDP (0): p2p0 af=18 addr= netmask=
[2014-Apr-07 12:21:42] RDP (0): bridge0 af=18 addr= netmask=
[2014-Apr-07 12:21:42] RDP (0): --- END INTERFACE LIST ---
[2014-Apr-07 12:21:42] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Apr-07 12:21:42] RDP (0): client version: 8.0.24428
[2014-Apr-07 12:21:42] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Apr-07 12:21:42] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
[2014-Apr-07 12:21:42] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Apr-07 12:21:43] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Apr-07 12:21:43] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-07 12:21:43] RDP (0): Server supports RAIL
[2014-Apr-07 12:21:43] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-07 12:21:43] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-07 12:21:43] RDP (0): Server supports RAIL
[2014-Apr-07 12:21:43] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-07 15:30:19] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Apr-07 15:30:19] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
User Message : Failed to read from socket: -1
[2014-Apr-07 15:30:19] RDP (0): ------ END ACTIVE CONNECTION ------
[2014-Apr-07 15:30:22] RDP (0): Final rdp configuration used: screen mode id:i:2
use multimon:i:1
session bpp:i:24
full address:s:192.168.16.x
audiomode:i:0
username:s:m
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com:1
bookmarktype:i:3
use redirection server name:i:0
[2014-Apr-07 15:30:22] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Apr-07 15:30:22] RDP (0): lo0 af=18 addr= netmask=
[2014-Apr-07 15:30:22] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Apr-07 15:30:22] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2014-Apr-07 15:30:22] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-07 15:30:22] RDP (0): gif0 af=18 addr= netmask=
[2014-Apr-07 15:30:22] RDP (0): stf0 af=18 addr= netmask=
[2014-Apr-07 15:30:22] RDP (0): en0 af=18 addr= netmask=
[2014-Apr-07 15:30:22] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-07 15:30:22] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
[2014-Apr-07 15:30:22] RDP (0): en1 af=18 addr= netmask=
[2014-Apr-07 15:30:22] RDP (0): en4 af=18 addr= netmask=
[2014-Apr-07 15:30:22] RDP (0): en3 af=18 addr= netmask=
[2014-Apr-07 15:30:22] RDP (0): p2p0 af=18 addr= netmask=
[2014-Apr-07 15:30:22] RDP (0): bridge0 af=18 addr= netmask=
[2014-Apr-07 15:30:22] RDP (0): --- END INTERFACE LIST ---
[2014-Apr-07 15:30:22] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Apr-07 15:30:22] RDP (0): client version: 8.0.24428
[2014-Apr-07 15:30:22] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Apr-07 15:30:22] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
[2014-Apr-07 15:30:22] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Apr-07 15:30:22] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Apr-07 15:30:22] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-07 15:30:22] RDP (0): Server supports RAIL
[2014-Apr-07 15:30:22] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-07 15:30:23] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-07 15:30:23] RDP (0): Server supports RAIL
[2014-Apr-07 15:30:23] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-07 16:52:24] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Apr-07 16:52:24] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
User Message : Failed to read from socket: -1
[2014-Apr-07 16:52:24] RDP (0): ------ END ACTIVE CONNECTION ------
[2014-Apr-07 16:52:27] RDP (0): Final rdp configuration used: screen mode id:i:2
use multimon:i:1
session bpp:i:24
full address:s:192.168.16.x
audiomode:i:0
username:s:m
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com:1
bookmarktype:i:3
use redirection server name:i:0
[2014-Apr-07 16:52:27] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Apr-07 16:52:27] RDP (0): lo0 af=18 addr= netmask=
[2014-Apr-07 16:52:27] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Apr-07 16:52:27] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2014-Apr-07 16:52:27] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-07 16:52:27] RDP (0): gif0 af=18 addr= netmask=
[2014-Apr-07 16:52:27] RDP (0): stf0 af=18 addr= netmask=
[2014-Apr-07 16:52:27] RDP (0): en0 af=18 addr= netmask=
[2014-Apr-07 16:52:27] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-07 16:52:27] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.195 netmask=255.255.255.0
[2014-Apr-07 16:52:27] RDP (0): en1 af=18 addr= netmask=
[2014-Apr-07 16:52:27] RDP (0): en4 af=18 addr= netmask=
[2014-Apr-07 16:52:27] RDP (0): en3 af=18 addr= netmask=
[2014-Apr-07 16:52:27] RDP (0): p2p0 af=18 addr= netmask=
[2014-Apr-07 16:52:27] RDP (0): bridge0 af=18 addr= netmask=
[2014-Apr-07 16:52:27] RDP (0): --- END INTERFACE LIST ---
[2014-Apr-07 16:52:27] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Apr-07 16:52:27] RDP (0): client version: 8.0.24428
[2014-Apr-07 16:52:27] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Apr-07 16:52:27] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
[2014-Apr-07 16:52:27] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Apr-07 16:52:27] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Apr-07 16:52:27] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-07 16:52:28] RDP (0): Server supports RAIL
[2014-Apr-07 16:52:28] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-07 16:52:28] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-07 16:52:28] RDP (0): Server supports RAIL
[2014-Apr-07 16:52:28] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-07 16:52:40] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-07 16:52:40] RDP (0): Disconnect initiated by server
[2014-Apr-07 16:52:45] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Apr-07 16:52:45] RDP (0): ------ END ACTIVE CONNECTION ------
[2014-Apr-07 16:52:45] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
User Message : Failed to read from socket: -1
[2014-Apr-07 16:58:19] RDP (0): *** Application terminated ***
[2014-Apr-08 10:00:23] RDP (0): Final rdp configuration used: screen mode id:i:2
use multimon:i:1
session bpp:i:24
full address:s:192.168.16.x
audiomode:i:0
username:s:m
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com:1
bookmarktype:i:3
use redirection server name:i:0
[2014-Apr-08 10:00:23] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Apr-08 10:00:23] RDP (0): lo0 af=18 addr= netmask=
[2014-Apr-08 10:00:23] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Apr-08 10:00:23] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2014-Apr-08 10:00:23] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-08 10:00:23] RDP (0): gif0 af=18 addr= netmask=
[2014-Apr-08 10:00:23] RDP (0): stf0 af=18 addr= netmask=
[2014-Apr-08 10:00:23] RDP (0): en0 af=18 addr= netmask=
[2014-Apr-08 10:00:23] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-08 10:00:23] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
[2014-Apr-08 10:00:23] RDP (0): en1 af=18 addr= netmask=
[2014-Apr-08 10:00:23] RDP (0): en4 af=18 addr= netmask=
[2014-Apr-08 10:00:23] RDP (0): en3 af=18 addr= netmask=
[2014-Apr-08 10:00:23] RDP (0): p2p0 af=18 addr= netmask=
[2014-Apr-08 10:00:23] RDP (0): bridge0 af=18 addr= netmask=
[2014-Apr-08 10:00:23] RDP (0): --- END INTERFACE LIST ---
[2014-Apr-08 10:00:23] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Apr-08 10:00:23] RDP (0): client version: 8.0.24428
[2014-Apr-08 10:00:23] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Apr-08 10:00:23] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
[2014-Apr-08 10:00:23] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Apr-08 10:00:23] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Apr-08 10:00:23] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-08 10:00:23] RDP (0): Server supports RAIL
[2014-Apr-08 10:00:23] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-08 10:00:38] RDP (0): Server hides cursor
[2014-Apr-08 10:00:40] RDP (0): Server shows cursor
[2014-Apr-08 10:08:35] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Apr-08 10:08:35] RDP (0): ------ END ACTIVE CONNECTION ------
[2014-Apr-08 10:08:35] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
User Message : Failed to read from socket: -1
[2014-Apr-08 10:08:39] RDP (0): Final rdp configuration used: screen mode id:i:2
use multimon:i:1
session bpp:i:24
full address:s:192.168.16.x
audiomode:i:0
username:s:m
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com:1
bookmarktype:i:3
use redirection server name:i:0
[2014-Apr-08 10:08:39] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Apr-08 10:08:39] RDP (0): lo0 af=18 addr= netmask=
[2014-Apr-08 10:08:39] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Apr-08 10:08:39] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2014-Apr-08 10:08:39] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-08 10:08:39] RDP (0): gif0 af=18 addr= netmask=
[2014-Apr-08 10:08:39] RDP (0): stf0 af=18 addr= netmask=
[2014-Apr-08 10:08:39] RDP (0): en0 af=18 addr= netmask=
[2014-Apr-08 10:08:39] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-08 10:08:39] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.195 netmask=255.255.255.0
[2014-Apr-08 10:08:39] RDP (0): en1 af=18 addr= netmask=
[2014-Apr-08 10:08:39] RDP (0): en4 af=18 addr= netmask=
[2014-Apr-08 10:08:39] RDP (0): en3 af=18 addr= netmask=
[2014-Apr-08 10:08:39] RDP (0): p2p0 af=18 addr= netmask=
[2014-Apr-08 10:08:39] RDP (0): bridge0 af=18 addr= netmask=
[2014-Apr-08 10:08:39] RDP (0): --- END INTERFACE LIST ---
[2014-Apr-08 10:08:39] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Apr-08 10:08:39] RDP (0): client version: 8.0.24428
[2014-Apr-08 10:08:39] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Apr-08 10:08:39] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
[2014-Apr-08 10:08:39] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Apr-08 10:08:39] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Apr-08 10:08:39] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-08 10:08:39] RDP (0): Server supports RAIL
[2014-Apr-08 10:08:39] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-08 10:08:40] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-08 10:08:40] RDP (0): Server supports RAIL
[2014-Apr-08 10:08:40] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-08 11:02:36] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Apr-08 11:02:36] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
User Message : Failed to read from socket: -1
[2014-Apr-08 11:02:36] RDP (0): ------ END ACTIVE CONNECTION ------
[2014-Apr-08 11:04:38] RDP (0): Final rdp configuration used: screen mode id:i:2
use multimon:i:1
session bpp:i:24
full address:s:192.168.16.25
audiomode:i:0
username:s:michele.lefebvre
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com:1
bookmarktype:i:3
use redirection server name:i:0
[2014-Apr-08 11:04:38] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Apr-08 11:04:38] RDP (0): lo0 af=18 addr= netmask=
[2014-Apr-08 11:04:38] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Apr-08 11:04:38] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2014-Apr-08 11:04:38] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-08 11:04:38] RDP (0): gif0 af=18 addr= netmask=
[2014-Apr-08 11:04:38] RDP (0): stf0 af=18 addr= netmask=
[2014-Apr-08 11:04:38] RDP (0): en0 af=18 addr= netmask=
[2014-Apr-08 11:04:38] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-08 11:04:38] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
[2014-Apr-08 11:04:38] RDP (0): en1 af=18 addr= netmask=
[2014-Apr-08 11:04:38] RDP (0): en4 af=18 addr= netmask=
[2014-Apr-08 11:04:38] RDP (0): en3 af=18 addr= netmask=
[2014-Apr-08 11:04:38] RDP (0): p2p0 af=18 addr= netmask=
[2014-Apr-08 11:04:38] RDP (0): bridge0 af=18 addr= netmask=
[2014-Apr-08 11:04:38] RDP (0): --- END INTERFACE LIST ---
[2014-Apr-08 11:04:38] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Apr-08 11:04:38] RDP (0): client version: 8.0.24428
[2014-Apr-08 11:04:38] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Apr-08 11:04:38] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
[2014-Apr-08 11:04:38] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Apr-08 11:04:38] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Apr-08 11:04:38] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-08 11:04:38] RDP (0): Server supports RAIL
[2014-Apr-08 11:04:39] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-08 11:04:39] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-08 11:04:39] RDP (0): Server supports RAIL
[2014-Apr-08 11:04:39] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-08 11:04:49] RDP (0): Server hides cursor
[2014-Apr-08 11:04:50] RDP (0): Server shows cursor
[2014-Apr-08 11:04:51] RDP (0): Server hides cursor
[2014-Apr-08 11:04:55] RDP (0): Server shows cursor
[2014-Apr-08 11:05:09] RDP (0): Server hides cursor
[2014-Apr-08 11:05:12] RDP (0): Server shows cursor
[2014-Apr-08 11:06:33] RDP (0): Server hides cursor
[2014-Apr-08 11:06:33] RDP (0): Server shows cursor
[2014-Apr-08 11:06:35] RDP (0): Server hides cursor
[2014-Apr-08 11:06:44] RDP (0): Server shows cursor
[2014-Apr-08 11:06:49] RDP (0): Server hides cursor
[2014-Apr-08 11:06:50] RDP (0): Server shows cursor
[2014-Apr-08 11:06:54] RDP (0): Server hides cursor
[2014-Apr-08 11:07:02] RDP (0): Server shows cursor
[2014-Apr-08 11:07:06] RDP (0): Server hides cursor
[2014-Apr-08 11:07:14] RDP (0): Server shows cursor
[2014-Apr-08 11:07:26] RDP (0): Server hides cursor
[2014-Apr-08 11:07:29] RDP (0): Server shows cursor
[2014-Apr-08 11:07:32] RDP (0): Server hides cursor
[2014-Apr-08 11:07:33] RDP (0): Server shows cursor
[2014-Apr-08 11:07:35] RDP (0): Server hides cursor
[2014-Apr-08 11:07:35] RDP (0): Server shows cursor
[2014-Apr-08 11:07:35] RDP (0): Server hides cursor
[2014-Apr-08 11:07:35] RDP (0): Server shows cursor
[2014-Apr-08 11:07:35] RDP (0): Server hides cursor
[2014-Apr-08 11:07:35] RDP (0): Server shows cursor
[2014-Apr-08 11:07:36] RDP (0): Server hides cursor
[2014-Apr-08 11:07:36] RDP (0): Server shows cursor
[2014-Apr-08 11:07:36] RDP (0): Server hides cursor
[2014-Apr-08 11:07:36] RDP (0): Server shows cursor
[2014-Apr-08 11:07:36] RDP (0): Server hides cursor
[2014-Apr-08 11:07:36] RDP (0): Server shows cursor
[2014-Apr-08 11:07:38] RDP (0): Server hides cursor
[2014-Apr-08 11:07:38] RDP (0): Server shows cursor
[2014-Apr-08 11:17:05] RDP (0): Server hides cursor
[2014-Apr-08 11:17:08] RDP (0): Server shows cursor
[2014-Apr-08 11:26:53] RDP (0): Server hides cursor
[2014-Apr-08 11:26:54] RDP (0): Server shows cursor
[2014-Apr-08 11:26:54] RDP (0): Server hides cursor
[2014-Apr-08 11:26:54] RDP (0): Server shows cursor
[2014-Apr-08 11:26:54] RDP (0): Server hides cursor
[2014-Apr-08 11:26:54] RDP (0): Server shows cursor
[2014-Apr-08 11:26:54] RDP (0): Server hides cursor
[2014-Apr-08 11:26:54] RDP (0): Server shows cursor
[2014-Apr-08 11:26:54] RDP (0): Server hides cursor
[2014-Apr-08 11:26:54] RDP (0): Server shows cursor
[2014-Apr-08 11:26:58] RDP (0): Server hides cursor
[2014-Apr-08 11:26:58] RDP (0): Server shows cursor
[2014-Apr-08 11:26:58] RDP (0): Server hides cursor
[2014-Apr-08 11:26:58] RDP (0): Server shows cursor
[2014-Apr-08 11:27:05] RDP (0): Server hides cursor
[2014-Apr-08 11:27:06] RDP (0): Server shows cursor
[2014-Apr-08 11:27:15] RDP (0): Server hides cursor
[2014-Apr-08 11:27:15] RDP (0): Server shows cursor
[2014-Apr-08 11:27:15] RDP (0): Server hides cursor
[2014-Apr-08 11:27:15] RDP (0): Server shows cursor
[2014-Apr-08 11:27:17] RDP (0): Server hides cursor
[2014-Apr-08 11:27:17] RDP (0): Server shows cursor
[2014-Apr-08 11:27:22] RDP (0): Server hides cursor
[2014-Apr-08 11:27:22] RDP (0): Server shows cursor
[2014-Apr-08 11:27:23] RDP (0): Server hides cursor
[2014-Apr-08 11:27:25] RDP (0): Server shows cursor
[2014-Apr-08 11:27:25] RDP (0): Server hides cursor
[2014-Apr-08 11:27:25] RDP (0): Server shows cursor
[2014-Apr-08 11:27:25] RDP (0): Server hides cursor
[2014-Apr-08 11:27:26] RDP (0): Server shows cursor
[2014-Apr-08 11:27:29] RDP (0): Server hides cursor
[2014-Apr-08 11:27:29] RDP (0): Server shows cursor
[2014-Apr-08 11:27:29] RDP (0): Server hides cursor
[2014-Apr-08 11:27:29] RDP (0): Server shows cursor
[2014-Apr-08 11:27:29] RDP (0): Server hides cursor
[2014-Apr-08 11:27:29] RDP (0): Server shows cursor
[2014-Apr-08 11:27:31] RDP (0): Server hides cursor
[2014-Apr-08 11:27:31] RDP (0): Server shows cursor
[2014-Apr-08 11:27:32] RDP (0): Server hides cursor
[2014-Apr-08 11:27:33] RDP (0): Server shows cursor
[2014-Apr-08 11:27:35] RDP (0): Server hides cursor
[2014-Apr-08 11:27:36] RDP (0): Server shows cursor
[2014-Apr-08 11:29:50] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Apr-08 11:29:50] RDP (0): ------ END ACTIVE CONNECTION ------
[2014-Apr-08 11:29:50] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
User Message : Failed to read from socket: -1
[2014-Apr-08 11:30:04] RDP (0): Final rdp configuration used: screen mode id:i:2
use multimon:i:1
session bpp:i:24
full address:s:192.168.16.x
audiomode:i:0
username:s:m
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com:1
bookmarktype:i:3
use redirection server name:i:0
[2014-Apr-08 11:30:04] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Apr-08 11:30:04] RDP (0): lo0 af=18 addr= netmask=
[2014-Apr-08 11:30:04] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Apr-08 11:30:04] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2014-Apr-08 11:30:04] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-08 11:30:04] RDP (0): gif0 af=18 addr= netmask=
[2014-Apr-08 11:30:04] RDP (0): stf0 af=18 addr= netmask=
[2014-Apr-08 11:30:04] RDP (0): en0 af=18 addr= netmask=
[2014-Apr-08 11:30:04] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-08 11:30:04] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
[2014-Apr-08 11:30:04] RDP (0): en1 af=18 addr= netmask=
[2014-Apr-08 11:30:04] RDP (0): en4 af=18 addr= netmask=
[2014-Apr-08 11:30:04] RDP (0): en3 af=18 addr= netmask=
[2014-Apr-08 11:30:04] RDP (0): p2p0 af=18 addr= netmask=
[2014-Apr-08 11:30:04] RDP (0): bridge0 af=18 addr= netmask=
[2014-Apr-08 11:30:04] RDP (0): --- END INTERFACE LIST ---
[2014-Apr-08 11:30:04] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Apr-08 11:30:04] RDP (0): client version: 8.0.24428
[2014-Apr-08 11:30:04] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Apr-08 11:30:04] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
[2014-Apr-08 11:30:04] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Apr-08 11:30:04] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Apr-08 11:30:04] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-08 11:30:04] RDP (0): Server supports RAIL
[2014-Apr-08 11:30:04] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-08 11:30:05] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-08 11:30:05] RDP (0): Server supports RAIL
[2014-Apr-08 11:30:05] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-08 11:30:11] RDP (0): Server hides cursor
[2014-Apr-08 11:30:11] RDP (0): Server shows cursor
[2014-Apr-08 11:30:11] RDP (0): Server hides cursor
[2014-Apr-08 11:30:11] RDP (0): Server shows cursor
[2014-Apr-08 11:30:12] RDP (0): Server hides cursor
[2014-Apr-08 11:30:12] RDP (0): Server shows cursor
[2014-Apr-08 11:30:12] RDP (0): Server hides cursor
[2014-Apr-08 11:30:12] RDP (0): Server shows cursor
[2014-Apr-08 11:30:12] RDP (0): Server hides cursor
[2014-Apr-08 11:30:12] RDP (0): Server shows cursor
[2014-Apr-08 11:30:30] RDP (0): Server hides cursor
[2014-Apr-08 11:30:31] RDP (0): Server shows cursor
[2014-Apr-08 11:30:31] RDP (0): Server hides cursor
[2014-Apr-08 11:30:31] RDP (0): Server shows cursor
[2014-Apr-08 14:45:21] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Apr-08 14:45:21] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
User Message : Failed to read from socket: -1
[2014-Apr-08 14:45:21] RDP (0): ------ END ACTIVE CONNECTION ------
[2014-Apr-08 15:11:03] RDP (0): Final rdp configuration used: screen mode id:i:2
use multimon:i:1
session bpp:i:24
full address:s:192.168.16.x
audiomode:i:0
username:s:m
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com:1
bookmarktype:i:3
use redirection server name:i:0
[2014-Apr-08 15:11:03] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Apr-08 15:11:03] RDP (0): lo0 af=18 addr= netmask=
[2014-Apr-08 15:11:03] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Apr-08 15:11:03] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2014-Apr-08 15:11:03] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-08 15:11:03] RDP (0): gif0 af=18 addr= netmask=
[2014-Apr-08 15:11:03] RDP (0): stf0 af=18 addr= netmask=
[2014-Apr-08 15:11:03] RDP (0): en0 af=18 addr= netmask=
[2014-Apr-08 15:11:03] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-08 15:11:03] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
[2014-Apr-08 15:11:03] RDP (0): en1 af=18 addr= netmask=
[2014-Apr-08 15:11:03] RDP (0): en4 af=18 addr= netmask=
[2014-Apr-08 15:11:03] RDP (0): en3 af=18 addr= netmask=
[2014-Apr-08 15:11:03] RDP (0): p2p0 af=18 addr= netmask=
[2014-Apr-08 15:11:03] RDP (0): bridge0 af=18 addr= netmask=
[2014-Apr-08 15:11:03] RDP (0): --- END INTERFACE LIST ---
[2014-Apr-08 15:11:03] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Apr-08 15:11:03] RDP (0): client version: 8.0.24428
[2014-Apr-08 15:11:03] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Apr-08 15:11:03] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
[2014-Apr-08 15:11:03] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Apr-08 15:11:03] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Apr-08 15:11:03] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-08 15:11:03] RDP (0): Server supports RAIL
[2014-Apr-08 15:11:03] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-08 15:11:04] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-08 15:11:04] RDP (0): Server supports RAIL
[2014-Apr-08 15:11:04] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-08 15:22:36] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-08 15:22:36] RDP (0): Disconnect initiated by server
[2014-Apr-08 15:22:41] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Apr-08 15:22:41] RDP (0): ------ END ACTIVE CONNECTION ------
[2014-Apr-08 15:22:41] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
User Message : Failed to read from socket: -1
[2014-Apr-08 16:29:11] RDP (0): Final rdp configuration used: screen mode id:i:2
use multimon:i:1
session bpp:i:24
full address:s:192.168.16.x
audiomode:i:0
username:s:michele.lefebvre
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com:1
bookmarktype:i:3
use redirection server name:i:0
[2014-Apr-08 16:29:11] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Apr-08 16:29:11] RDP (0): lo0 af=18 addr= netmask=
[2014-Apr-08 16:29:11] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Apr-08 16:29:11] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2014-Apr-08 16:29:11] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-08 16:29:11] RDP (0): gif0 af=18 addr= netmask=
[2014-Apr-08 16:29:11] RDP (0): stf0 af=18 addr= netmask=
[2014-Apr-08 16:29:11] RDP (0): en0 af=18 addr= netmask=
[2014-Apr-08 16:29:11] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-08 16:29:11] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.195 netmask=255.255.255.0
[2014-Apr-08 16:29:11] RDP (0): en1 af=18 addr= netmask=
[2014-Apr-08 16:29:11] RDP (0): en4 af=18 addr= netmask=
[2014-Apr-08 16:29:11] RDP (0): en3 af=18 addr= netmask=
[2014-Apr-08 16:29:11] RDP (0): p2p0 af=18 addr= netmask=
[2014-Apr-08 16:29:11] RDP (0): bridge0 af=18 addr= netmask=
[2014-Apr-08 16:29:11] RDP (0): --- END INTERFACE LIST ---
[2014-Apr-08 16:29:11] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Apr-08 16:29:11] RDP (0): client version: 8.0.24428
[2014-Apr-08 16:29:11] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Apr-08 16:29:11] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
[2014-Apr-08 16:29:11] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Apr-08 16:29:11] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Apr-08 16:29:11] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-08 16:29:12] RDP (0): Server supports RAIL
[2014-Apr-08 16:29:12] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-08 16:29:51] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-08 16:29:51] RDP (0): Disconnect initiated by server
[2014-Apr-08 16:29:56] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Apr-08 16:29:56] RDP (0): ------ END ACTIVE CONNECTION ------
[2014-Apr-08 16:29:56] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
User Message : Failed to read from socket: -1
[2014-Apr-08 16:37:07] RDP (0): *** Application terminated ***
[2014-Apr-09 09:24:29] RDP (0): Final rdp configuration used: screen mode id:i:2
use multimon:i:1
session bpp:i:24
full address:s:192.168.16.x
audiomode:i:0
username:s:m
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com:1
bookmarktype:i:3
use redirection server name:i:0
[2014-Apr-09 09:24:29] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Apr-09 09:24:29] RDP (0): lo0 af=18 addr= netmask=
[2014-Apr-09 09:24:29] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Apr-09 09:24:29] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2014-Apr-09 09:24:29] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-09 09:24:29] RDP (0): gif0 af=18 addr= netmask=
[2014-Apr-09 09:24:29] RDP (0): stf0 af=18 addr= netmask=
[2014-Apr-09 09:24:29] RDP (0): en0 af=18 addr= netmask=
[2014-Apr-09 09:24:29] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-09 09:24:29] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.195 netmask=255.255.255.0
[2014-Apr-09 09:24:29] RDP (0): en1 af=18 addr= netmask=
[2014-Apr-09 09:24:29] RDP (0): en4 af=18 addr= netmask=
[2014-Apr-09 09:24:29] RDP (0): en3 af=18 addr= netmask=
[2014-Apr-09 09:24:29] RDP (0): p2p0 af=18 addr= netmask=
[2014-Apr-09 09:24:29] RDP (0): bridge0 af=18 addr= netmask=
[2014-Apr-09 09:24:29] RDP (0): --- END INTERFACE LIST ---
[2014-Apr-09 09:24:29] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Apr-09 09:24:29] RDP (0): client version: 8.0.24428
[2014-Apr-09 09:24:29] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Apr-09 09:24:29] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
[2014-Apr-09 09:24:29] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Apr-09 09:24:29] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Apr-09 09:24:29] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-09 09:24:29] RDP (0): Server supports RAIL
[2014-Apr-09 09:24:29] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-09 09:24:45] RDP (0): Server hides cursor
[2014-Apr-09 09:24:46] RDP (0): Server shows cursor
[2014-Apr-09 09:24:46] RDP (0): Server hides cursor
[2014-Apr-09 09:24:49] RDP (0): Server shows cursor
[2014-Apr-09 09:25:08] RDP (0): Server hides cursor
[2014-Apr-09 09:25:10] RDP (0): Server shows cursor
[2014-Apr-09 09:25:15] RDP (0): Server hides cursor
[2014-Apr-09 09:25:27] RDP (0): Server shows cursor
[2014-Apr-09 09:25:30] RDP (0): Server hides cursor
[2014-Apr-09 09:25:31] RDP (0): Server shows cursor
[2014-Apr-09 09:25:33] RDP (0): Server hides cursor
[2014-Apr-09 09:25:34] RDP (0): Server shows cursor
[2014-Apr-09 09:25:38] RDP (0): Server hides cursor
[2014-Apr-09 09:25:48] RDP (0): Server shows cursor
[2014-Apr-09 09:25:50] RDP (0): Server hides cursor
[2014-Apr-09 09:26:40] RDP (0): Server shows cursor
[2014-Apr-09 09:26:40] RDP (0): Server hides cursor
[2014-Apr-09 09:26:40] RDP (0): Server shows cursor
[2014-Apr-09 09:26:40] RDP (0): Server hides cursor
[2014-Apr-09 09:26:40] RDP (0): Server shows cursor
[2014-Apr-09 09:26:40] RDP (0): Server hides cursor
[2014-Apr-09 09:26:41] RDP (0): Server shows cursor
[2014-Apr-09 09:26:41] RDP (0): Server hides cursor
[2014-Apr-09 09:26:41] RDP (0): Server shows cursor
[2014-Apr-09 09:26:41] RDP (0): Server hides cursor
[2014-Apr-09 09:26:41] RDP (0): Server shows cursor
[2014-Apr-09 09:26:53] RDP (0): Server hides cursor
[2014-Apr-09 09:26:53] RDP (0): Server shows cursor
[2014-Apr-09 09:26:53] RDP (0): Server hides cursor
[2014-Apr-09 09:26:53] RDP (0): Server shows cursor
[2014-Apr-09 09:26:58] RDP (0): Server hides cursor
[2014-Apr-09 09:26:58] RDP (0): Server shows cursor
[2014-Apr-09 09:27:20] RDP (0): Server hides cursor
[2014-Apr-09 09:27:22] RDP (0): Server shows cursor
[2014-Apr-09 09:27:23] RDP (0): Server hides cursor
[2014-Apr-09 09:27:23] RDP (0): Server shows cursor
[2014-Apr-09 10:10:53] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Apr-09 10:10:53] RDP (0): ------ END ACTIVE CONNECTION ------
[2014-Apr-09 10:10:53] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
User Message : Failed to read from socket: -1
[2014-Apr-09 10:10:56] RDP (0): Final rdp configuration used: screen mode id:i:2
use multimon:i:1
session bpp:i:24
full address:s:192.168.16.x
audiomode:i:0
username:s:m
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com:1
bookmarktype:i:3
use redirection server name:i:0
[2014-Apr-09 10:10:56] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Apr-09 10:10:56] RDP (0): lo0 af=18 addr= netmask=
[2014-Apr-09 10:10:56] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Apr-09 10:10:56] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2014-Apr-09 10:10:56] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-09 10:10:56] RDP (0): gif0 af=18 addr= netmask=
[2014-Apr-09 10:10:56] RDP (0): stf0 af=18 addr= netmask=
[2014-Apr-09 10:10:56] RDP (0): en0 af=18 addr= netmask=
[2014-Apr-09 10:10:56] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-09 10:10:56] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
[2014-Apr-09 10:10:56] RDP (0): en1 af=18 addr= netmask=
[2014-Apr-09 10:10:56] RDP (0): en4 af=18 addr= netmask=
[2014-Apr-09 10:10:56] RDP (0): en3 af=18 addr= netmask=
[2014-Apr-09 10:10:56] RDP (0): p2p0 af=18 addr= netmask=
[2014-Apr-09 10:10:56] RDP (0): bridge0 af=18 addr= netmask=
[2014-Apr-09 10:10:56] RDP (0): --- END INTERFACE LIST ---
[2014-Apr-09 10:10:56] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Apr-09 10:10:56] RDP (0): client version: 8.0.24428
[2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Apr-09 10:10:56] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
[2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-09 10:10:56] RDP (0): Server supports RAIL
[2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-09 10:10:56] RDP (0): Server supports RAIL
[2014-Apr-09 10:10:56] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-09 10:12:00] RDP (0): Server hides cursor
[2014-Apr-09 10:12:01] RDP (0): Server shows cursor
[2014-Apr-09 10:16:50] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Apr-09 10:16:50] RDP (0): ------ END ACTIVE CONNECTION ------
[2014-Apr-09 10:16:50] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
User Message : Failed to read from socket: -1
[2014-Apr-09 10:22:22] RDP (0): Final rdp configuration used: screen mode id:i:2
use multimon:i:1
session bpp:i:24
full address:s:192.168.16.x
audiomode:i:0
username:s:m
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com:1
bookmarktype:i:3
use redirection server name:i:0
[2014-Apr-09 10:22:22] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Apr-09 10:22:22] RDP (0): lo0 af=18 addr= netmask=
[2014-Apr-09 10:22:22] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Apr-09 10:22:22] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2014-Apr-09 10:22:22] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-09 10:22:22] RDP (0): gif0 af=18 addr= netmask=
[2014-Apr-09 10:22:22] RDP (0): stf0 af=18 addr= netmask=
[2014-Apr-09 10:22:22] RDP (0): en0 af=18 addr= netmask=
[2014-Apr-09 10:22:22] RDP (0): en1 af=18 addr= netmask=
[2014-Apr-09 10:22:22] RDP (0): en1 af=30 (AF_INET6) addr=fe80::ee35:86ff:fe3b:e3d8%en1 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-09 10:22:22] RDP (0): en1 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
[2014-Apr-09 10:22:22] RDP (0): en4 af=18 addr= netmask=
[2014-Apr-09 10:22:22] RDP (0): en3 af=18 addr= netmask=
[2014-Apr-09 10:22:22] RDP (0): p2p0 af=18 addr= netmask=
[2014-Apr-09 10:22:22] RDP (0): bridge0 af=18 addr= netmask=
[2014-Apr-09 10:22:22] RDP (0): --- END INTERFACE LIST ---
[2014-Apr-09 10:22:22] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Apr-09 10:22:22] RDP (0): client version: 8.0.24428
[2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Apr-09 10:22:22] RDP (0): Resolved '192.168.16.x' to '192.168.16.x' using NameResolveMethod_DNS(1)
[2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-09 10:22:22] RDP (0): Server supports RAIL
[2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-09 10:22:22] RDP (0): Server supports RAIL
[2014-Apr-09 10:22:22] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-09 10:26:40] RDP (0): Protocol state changed to: ProtocolDisconnecting(7)
[2014-Apr-09 10:26:40] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Apr-09 10:26:40] RDP (0): *** Application terminated ***
[2014-Apr-09 10:27:28] RDP (0): *** Application terminated ***
[2014-Apr-09 10:28:36] RDP (0): Final rdp configuration used: screen mode id:i:2
use multimon:i:1
session bpp:i:24
full address:s:192.168.16.x
audiomode:i:0
username:s:m
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com:1
bookmarktype:i:3
use redirection server name:i:0
[2014-Apr-09 10:28:36] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Apr-09 10:28:36] RDP (0): lo0 af=18 addr= netmask=
[2014-Apr-09 10:28:36] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Apr-09 10:28:36] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2014-Apr-09 10:28:36] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-09 10:28:36] RDP (0): gif0 af=18 addr= netmask=
[2014-Apr-09 10:28:36] RDP (0): stf0 af=18 addr= netmask=
[2014-Apr-09 10:28:36] RDP (0): en0 af=18 addr= netmask=
[2014-Apr-09 10:28:36] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-09 10:28:36] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.1xx netmask=255.255.255.0
[2014-Apr-09 10:28:36] RDP (0): en1 af=18 addr= netmask=
[2014-Apr-09 10:28:36] RDP (0): en4 af=18 addr= netmask=
[2014-Apr-09 10:28:36] RDP (0): en3 af=18 addr= netmask=
[2014-Apr-09 10:28:36] RDP (0): p2p0 af=18 addr= netmask=
[2014-Apr-09 10:28:36] RDP (0): bridge0 af=18 addr= netmask=
[2014-Apr-09 10:28:36] RDP (0): --- END INTERFACE LIST ---
[2014-Apr-09 10:28:36] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Apr-09 10:28:36] RDP (0): client version: 8.0.24428
[2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Apr-09 10:28:36] RDP (0): Resolved '192.168.16.25' to '192.168.16.x' using NameResolveMethod_DNS(1)
[2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-09 10:28:36] RDP (0): Server supports RAIL
[2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-09 10:28:36] RDP (0): Server supports RAIL
[2014-Apr-09 10:28:36] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-09 11:33:11] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2014-Apr-09 11:33:11] RDP (0): Exception caught: Exception in file '../../librdp/legacytcpstreamadapter.cpp' at line 322
User Message : Failed to read from socket: -1
[2014-Apr-09 11:33:11] RDP (0): ------ END ACTIVE CONNECTION ------
[2014-Apr-09 11:33:18] RDP (0): Final rdp configuration used: screen mode id:i:2
use multimon:i:1
session bpp:i:24
full address:s:192.168.16.x
audiomode:i:0
username:s:michele.lefebvre
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:2
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop com:1
bookmarktype:i:3
use redirection server name:i:0
[2014-Apr-09 11:33:18] RDP (0): --- BEGIN INTERFACE LIST ---
[2014-Apr-09 11:33:18] RDP (0): lo0 af=18 addr= netmask=
[2014-Apr-09 11:33:18] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2014-Apr-09 11:33:18] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
[2014-Apr-09 11:33:18] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-09 11:33:18] RDP (0): gif0 af=18 addr= netmask=
[2014-Apr-09 11:33:18] RDP (0): stf0 af=18 addr= netmask=
[2014-Apr-09 11:33:18] RDP (0): en0 af=18 addr= netmask=
[2014-Apr-09 11:33:18] RDP (0): en0 af=30 (AF_INET6) addr=fe80::12dd:b1ff:febe:9771%en0 netmask=ffff:ffff:ffff:ffff::
[2014-Apr-09 11:33:18] RDP (0): en0 af=2 (AF_INET) addr=192.168.16.195 netmask=255.255.255.0
[2014-Apr-09 11:33:18] RDP (0): en1 af=18 addr= netmask=
[2014-Apr-09 11:33:18] RDP (0): en4 af=18 addr= netmask=
[2014-Apr-09 11:33:18] RDP (0): en3 af=18 addr= netmask=
[2014-Apr-09 11:33:18] RDP (0): p2p0 af=18 addr= netmask=
[2014-Apr-09 11:33:18] RDP (0): bridge0 af=18 addr= netmask=
[2014-Apr-09 11:33:18] RDP (0): --- END INTERFACE LIST ---
[2014-Apr-09 11:33:18] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Apr-09 11:33:18] RDP (0): client version: 8.0.24428
[2014-Apr-09 11:33:18] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2014-Apr-09 11:33:18] RDP (0): Resolved '192.168.16.25' to '192.168.16.25' using NameResolveMethod_DNS(1)
[2014-Apr-09 11:33:18] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2014-Apr-09 11:33:18] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2014-Apr-09 11:33:18] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-09 11:33:19] RDP (0): Server supports RAIL
[2014-Apr-09 11:33:19] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-09 11:33:19] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2014-Apr-09 11:33:19] RDP (0): Server supports RAIL
[2014-Apr-09 11:33:19] RDP (0): Protocol state changed to: ProtocolActive(5)
[2014-Apr-09 11:33:34] RDP (0): Server hides cursor
[2014-Apr-09 11:33:38] RDP (0): Server shows cursor
Any help would be appreciated.Hi,
A connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a timeout or a restart. On a datastream socket, the
connection was reset. This reset could be generated locally by the network system when it detects a connection failure, or it might be received from the remote host (in TCP terms, the remote host sent an RST packet). This error is also possible on a datagram
socket; for instance, this error could result if your application sends a UDP datagram to a host, which rejects it by responding with an ICMP Port Unreachable.
Please check the following:
1. Ping the remote host you were connected to. If it does respond, this problem might have been a transient one (so you can reconnect now), or the server application you were
connected to might have terminated (so you might not be able to connect again).
2. Type tracert at the command prompt to determine the path to the host you were connected to. This won't reveal too much unless you know the router addresses at the remote end,
but it might help to identify if the problem is somewhere along the way.
3. Check if there is any related error log in the server side.
Thanks.
Jeremy Wu
TechNet Community Support -
Socket read error: connection reset by peer
Hi.
Has anybody experienced the error message �Socket read error: connection reset by peer�
Please see below for detailed information.
Appreciate your help
Regards
RT
Enviroment specification
Server: HP/UX 11.00 64-bit, Oracle RDBMS 8.1.6.0.0 64-bit
2 firewalls between client and db.
Client:
Win 2000,
SP3,
Oracle Client 8.1.7.0.0 ,JDBC OCI (thin JDBC driver,class12.zip)
JDK 1.3
JRUN3.0
The TCP protocol is being used in the communication
Error messages
Web Users receive: Socket read error: connection reset by peer
Trace files on the sever: Read unexpected EOF ERROR on 18.
Explanation: The error in the server sqlnet trace file, suggests that a client connection has terminated abnormally, i.e. client machine powered off, a cable removed or a network connection aborted without warning. No user has complained of such a problem and there is no client trace with an error.
The problem
The users of the java web application, experiencing an exception almost once or twice a day.
The JRUN web-server reports broken connections to the db and client are receiving "connection reset by peer".
At the moment when the errors occurs the users just have to wait a while(2-10 min) and then they can use the web application again.(no action is taken)
This problem can not be reproduced. The problem happens only occasionally when the network is under heavy load and new DB connection is being created.
The application
The java web-application uses a customized connection pooling against the database. This pool is shared among all the users of the website. whenever a user process needs to fetch data from the database, a free connection from this pool is allocated. The application is testing if the connection is valid before making a transaction (select '1' from dual). When the error occurs a ORA-3113 end-of-file on communication channel is returned to the application.
The path between the client and db involves at least two firewalls. The firewalls are opened for sql*net traffic. The network group can tell that enquiries from the app.server is not getting feedback from the db. They have not however, identified if the enquiries are reaching the db-srever, or if they are stopped earlier in the network.
Around 1000 users, are using other applications which uses dedicated sqlnet connections against the db and they have not experienced any problems.
Issues considered
Connection pooling
It is a customized connection pooling, developed by Lindorff developers.
I have read through the source code for the connection pooling and it does the job as it should, and in case of bad connection, it tries to create a new connection.
The log file shows that the call to the method DriverManager.getConnection() hangs until the server goes down, which is probably because of the fact that the method DriverManager.setLoginTimeout(), does not take effect and timeout value is Zero. ( According to oracle , Oracle JDBC does not support login timeouts and calling the static DriverManager.setLoginTimeout() method will have no effect).
Firewall
One thing to consider is when the firewall may decide to shut down the socket due to long inactivity of a connection. This will cause problems to JDBC Connection Pool because the pool is not aware of this disconnection at the TCP/IP level; until someone checks out the connection from the pool and tries to use it. The user will get a Socket read error: connection reset by peer.
Jrun timeout paramter is less than the firewall�s timeout so the firewall will not close a connection before Jrun does.
Number of processes the DB can handle
Processes parameter is 1300, , they have not experienced the Oracle error msg �max # of processes reached�.
Port redirection through a firewall:
Since the firewall has a sql net proxy Port redirection through a firewall is not a problem. Problems with port redirection only appear at connect time, but in this situation the connections fail long after the connection is established.
The network group
The network people who investigaged the problem at Lindorff report that there are a significant amount of "dropped packages" between the database server and the jdbc client (web-application) 24 hrs. The reason for this is "unknown established TCP packet" which means that the firewall does not consider these packages to be part of an already established session. The network group believes this happen because one of the hosts send a RESET or FIN signal which the firewall have noticed but are not received by the other host.
It seems like the firewall are dropping packages bacause of "Unknown
established TCP packet" from both the JDBC client and the TNSLISTENER on the database server. The dropped packages are SQL*Net v2 traffic so clearly Oracle products are involvedPresumably something is working.
Thus the problem is not with your code. At least not the database part that you have control over.
That error occurs when the other side closes the socket. Presumably you are catching lost connection exceptions and trying to restore it. -
XI 2.0 Inbound file adapter : Connection reset by peer
I am using XI 2.0 and have an inbound file adapter. It polls every 5 minutes. But at least 1 or twice a day the file adapter stops with the following error message.
"java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read" occurred \par
There have been times when this runs for days or weeks without any problems.
Has anyone else seen this issue and how do your correct it?
Currently I have to go into the file adpaters and restart them manually. It would be nice if there was some way to automate this function. Any ideas?
Regards,
JimWith JDK 5.0 use ojdbc5.jar instead of ojdbc14.jar.
-
Connection reset by peer problem
I have the following code, and every time I run it i get a "java.net.SocketException: Connection reset by peer: socket write error" exception. Why is that? This is the first time I'm writing a network client application, so please help :)
Socket s = new Socket("127.0.0.1",8080);
OutputStream out = new BufferedOutputStream(s.getOutputStream());
InputStream in = new BufferedInputStream(s.getInputStream());
out.write("server status\r\n".getBytes());
//out.flush();
StringBuffer responseLine = new StringBuffer();
int c;
while(in.available() > 0) {
c = in.read();
responseLine.append((char)c);
//out.close();
//in.close();
//s.close();
System.out.println(responseLine.toString());P.S. It's the same problem with or wothout the out.flush(), and with or wothout closing my streams and socket.InputStream = new BufferedReader
Um..just look at that code, oh boy.
InputStream is a class and so is
BufferedReader
Two different classes (event if they are subclasses)
cant be directly assigned to each other.The human eye sometimes sees what it wants to see and not what it is... :-)
I think the problem is with the protocol and the timing. The while loop may never execute due to timing:
1. Client's "server status" request takes a few ms to arrive in the server.
2. In the meanwhile, in.available is zero and the client does not enter the loop and does not append any characters to the string buffer.
3. Server writes its status on the socket which arrives at the client which is no longer reading it a few ms later.
Which brings us to the protocol:
If the server status is a fixed length block of data, try reading it into a single byte buffer.
If it is variable length or text, use a BufferedReader on the socket, read the response a line at a time and make the server end the report with a token (like a last line of "END_OF_SERVER_STATUS_REPORT" or "01234567890123456789012345678901234567890123456789", whatever).
Don't check if data is available on a socket if you know it should be, sooner or later, and you don't want to multiplex your flow on data availability. -
Io exception: Connection reset by peer: JVM_recv in socket input stream read
We are developing a new J2EE app using JDev, OC4J, servlets, and EJBs. We have determined that our firewall is closing database connections that have been idle for 1 hour. This is a security requirement that cannot be changed. When we try to use these idle connections in both stateless and entity beans, we consistently receive this or a similar error message:
"ServletSACategoryList: Error invoking EJB procedure. Exception: java.sql.SQLException: StatelessSysAdminBean::getCategoryList - Io exception: Connection reset by peer: JVM_recv in socket input stream read "
Environment:
Oracle 9iAS 9.0.2.0.0
Database: Oracle 8.1.7
JDBC 8.1.7
JDK 1.3
JDev 9.0.2.829
We are using the ejb-location attribute within data-sources.xml for JNDI lookup of the DataSource. Here is what this file looks like:
<data-sources>
<data-source
class="oracle.jdbc.pool.OracleDataSource"
name="jdbc/OracleDS"
location="jdbc/OracleCoreDS"
xa-location="jdbc/xa/OracleXADS"
ejb-location="jdbc/OraclePoolDS"
url="jdbc:oracle:thin:@###.###.#.###:1521:dev1"
connection-driver="oracle.jdbc.driver.OracleDriver"
username="????????"
password="????????"
max-connections="4"
wait-timeout="20"
min-connections="1"
inactivity-timeout="60"
connection-retry-interval="1"
max-connect-attempts="3"
/>
</data-sources>
After calling getConnection() on the Connection object in my stateless bean, I have tried checking if the Connection object is null or isClosed(), I have caught any Exception, and looped to try again, but nothing has worked.
Please respond to [email protected] or directly to this post if you can help in any way.
Thank you,
- RobHi Robert,
If you don't mind, I can only offer a few suggestions for things
to try -- I'm afraid I don't have a solution for you. Of-course,
you may have already tried these things, so please excuse me if
this is the case.
Firstly, your "data-sources.xml" file looks "different". Have
you read the "Data Sources" chapter of the "Oracle9iAS Containers
for J2EE Services Guide, Release 2 (9.0.2)"? It is accessible
from here:
http://otn.oracle.com/docs/products/ias/doc_library/90200doc_otn/web.902/a95879/ds.htm#1004903
Also, have you tried running OC4J in "debug" mode? This web
page has more details:
http://kb.atlassian.com/content/atlassian/howto/orionproperties.jsp
I get the impression from the information you have supplied,
that you may not be explicitly closing your database connections
in your code. It looks to me like you are obtaining a database
connection in your session bean, and then keeping it for the
lifetime of that bean. Is that correct? I think it's better
to obtain a connection when you need to interact with the database,
and then close the connection immediately after completing the
interaction with the database (but that's just my opinion).
Lastly, if you haven't already discovered them, these web sites
may also be of help:
http://www.orionserver.com
http://www.orionsupport.com
http://www.elephantwalker.com
Hope this helps you.
Good Luck,
Avi. -
Netscape Error: Connection reset by peer
I am running a JSP application on weblogic and when I view in Netscape 4.08 on
W2K I am getting an error saying Netscape Error:Connection reset by peer. Anyone
else see same error. Any fixes?
do u see this on the 5.1 line ?
Netscape needs a content-length for every response that comes in, and in case the
response is larger than the buffer size, the content-length isnt set and netscape
keeps hovering even after getting all the data.
When it sees that the connection has been closed from the other side, it thinks that
the connection has been reset. (even after the server sends it a Connection: Close
header)
solns can be summed up as:
1. call response.setContentLength whereever possible
2. increase the buffersize of jsps (there might be an upperlimit though)
3. move to another version of netscape (atleast > 4.7 ) on win2k
let me know how the workarounds are
thanks
Nagesh
Mettu Kumar wrote:
> which version of wls are u using and what sp's?
>
> Kumar.
>
> Kyle Donovan wrote:
>
> > I am running a JSP application on weblogic and when I view in Netscape 4.08 on
> > W2K I am getting an error saying Netscape Error:Connection reset by peer. Anyone
> > else see same error. Any fixes?
-
Re: Connection reset by peer: Connection reset by peer
>This is not a problem. It is an error message that you can safely ignore (that
we should not be printing) and have fixed in version 6.0.
Sorry but we are upgrading from 5.1 to 6.1sp2 and this became a problem for us.
Indeed we just ignored this exception in 5.1, but today with 6.1sp2, we get it
each time we do a RequestDispatcher.forward(). The forward is done, but every
attributes set on the request are lost !!
At first I thought it was related with the NT Muxer, or the NT Performance Pack,
I removed the property NativeIOEnabled but I still get a :
ven. 20020726 09:11:31 CEST <0> java.net.SocketException: Connection reset by
peer: socket write error
at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
at weblogic.servlet.internal.ChunkUtils.writeHeaderChunk(ChunkUtils.java:151)
at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:380)
at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:827)
at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:222)
at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:113)
at weblogic.servlet.internal.ServletOutputStreamImpl.commit(ServletOutputStreamImpl.java:446)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:266)
at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.forwardScreen(TeamsWebScreenBuilder.java:155)
at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.build(TeamsWebScreenBuilder.java:98)
at cegedim.tvf.koala.servlet.GlobalServlet.callResultBuilder(GlobalServlet.java:365)
at cegedim.tvf.teamsweb.servlet.ConnectionServlet.doPost(ConnectionServlet.java:112)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Yann,
This is not a J2EE Connector problem. From the stack trace it looks like you might
have better luck posting this to the Servlet newsgroup.
Also, just so that you are aware, this newsgroup is not monitored regularly so
if your issue/question is not getting answered in a timely manner, please send
a request to BEA Support.
>
>>This is not a problem. It is an error message that you can safely ignore
>(that
>we should not be printing) and have fixed in version 6.0.
>
>--
>
>Sorry but we are upgrading from 5.1 to 6.1sp2 and this became a problem
>for us.
>Indeed we just ignored this exception in 5.1, but today with 6.1sp2,
>we get it
>each time we do a RequestDispatcher.forward(). The forward is done, but
>every
>attributes set on the request are lost !!
>At first I thought it was related with the NT Muxer, or the NT Performance
>Pack,
>I removed the property NativeIOEnabled but I still get a :
>
>ven. 20020726 09:11:31 CEST <0> java.net.SocketException: Connection
>reset by
>peer: socket write error
> at java.net.SocketOutputStream.socketWrite(Native Method)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
> at weblogic.servlet.internal.ChunkUtils.writeHeaderChunk(ChunkUtils.java:151)
> at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:380)
> at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:827)
> at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:222)
> at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:113)
> at weblogic.servlet.internal.ServletOutputStreamImpl.commit(ServletOutputStreamImpl.java:446)
> at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:266)
> at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.forwardScreen(TeamsWebScreenBuilder.java:155)
> at cegedim.tvf.teamsweb.gui.TeamsWebScreenBuilder.build(TeamsWebScreenBuilder.java:98)
> at cegedim.tvf.koala.servlet.GlobalServlet.callResultBuilder(GlobalServlet.java:365)
> at cegedim.tvf.teamsweb.servlet.ConnectionServlet.doPost(ConnectionServlet.java:112)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
> at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
> at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
>
-
Connection reset by peer:/Broken pipe using JTurbo JDBC Driver
I am using the JTurbo JDBC driver to connect to a SQL Server 7.0 database. I am using Connection Pooling. After roughly an hour or so, I am no longer to get connections from the pool. Exceptions thrown are "connection reset by peer", followed by "Broken pipe" exceptions on every subsequent getConnection call.
Has anyone found a successfull resolution to this problem using the JTurbo JDBC driver for SQL Server 7.0? I have tried the "autoReconnection=true" option on the URL string for the driver, but this has had no effect.
I am running the Resin app server, version 1.2.7, on Solaris 8 and connecting to a SQL Server database running on NT 4.0. The JVM on Solaris where the servlet is running is 1.3.1.
Any help is greatly appreciated!
Mark Crouch
Lead Developer
accessKentI do not have an idea about your application server but i do know how i solved it in weblogic. Just see whether this is helpful to you.
Points to be sure of........
1) Make sure that when ever you request a connection from a pool, after you are done with it return it. If you are not returning it and trying to use that reference again, this problem will occur.
2) Look at the capabilities of your app server. Set the connection pool such that
a) All the connections are checked at regular interval with some default select statement from any table in the database.
b) Connections are check when the connection is checked out and returned to the pool.
I the connection object is not ready , close it and create a new one. The app server which manages the pool should implement these feature so that when you get the connection - its the tested and working object.
If your app server does not support - then think of ways you testing it before you using it(Anyway this is not the good solution). -
Connection reset by peer WLS 7.0.1
Hi,
I have an application running on the wls 7.0.1 server, it runs fine until we let
the users access it. Problem is users click fast :) and somehow a connection reset
by peer exception is thrown into the client... Should not this only get logged
into the server log? If it should be thrown to the client, is this possible to
switch off, or do I have to make a try catch for every out.print i make in the
code????
On Mon, 02 Dec 2002 05:34:44 +0000, Klaus Myrseth wrote:
>
> Hi,
>
> I have an application running on the wls 7.0.1 server, it runs fine until we let
> the users access it. Problem is users click fast :) and somehow a connection reset
> by peer exception is thrown into the client... Should not this only get logged
> into the server log? If it should be thrown to the client, is this possible to
> switch off, or do I have to make a try catch for every out.print i make in the
> code????
Looks like you are not running JSP pages? You said it is an application
run by client from server? Then of course the error messages will be
displayed at the client side.
Thank you,
Neo Gigs
"Follow the white rabbit..."
-
"Connection reset by peer" using firewall between iFS API and Database
Hi ..
We have a webapplication running on a websphere server using the iFS API to connect to a iFS schema through a firewall ( PIX ). The firewall will close idle connections after a while, and this results in "Connection reset by peer" errors in our application.
Firewall guys says that configuring the firewall not to close connections, is not an option.
Does anybody have experiences with this, suggestions on how to deal with this?
We are running iFS 9.0.1.
Thanks
Anders Monrad
Danisco ITI'm having the same problem, using a PIX firewall, however, I have the firewall setup between OHS & OC4J, also between OC4J and our application database.
I have a solution for the OC4J and app DB. If I set the expire_time = 10 in sqlnet.ora, this will ensure that sqlnet will ping the connection between OC4j and the DB every 10 minutes, thus the firewall will not close the connection due to inactivity.
However, does anyone have a solution for the OHS & OC4J connection? Can this be resolved with configuration rather than having to use an app to ping it?
[I realise I could write an app to retrieve a page every so often to keep the connection open, but I want to do it with configuration]
Thanks in Advance.
Maybe you are looking for
-
Error when activating 0MAT_Plant.
Hi Experts, I have added a custom created infoobject(Material Freight Group) as an attribute of 0MAT_PLANT.When i assign it as only display attribute,its activating.But when i change it to Naviagtional attribute,its giving me the error"Error activati
-
HOW TO MAKE MY JAVA APPLICATION CODE INTO A EXE?
I JUST FINISH WRITING A JAVA APPICATION code USING JCreator. there is no error in the program. Can someone provide me the steps to change it into a exe so that i can use the application in any computer. THANK YOU!
-
How to change the selected row color in an alv grid display ?
Hello , I WANT TO CHANGE THE COLOR OF THE SELECTED RECORDS IN AN ALV GRID DISPLAY ? ITS URGENT.. WILL BE REWARDED...
-
Little telephone handset icon in top menu bar?
I was doing something with a while back and turned on the little telephone handset icon in the menubar that is associated with Networking. Now I'd like to turn it off, but I can't remember where that preference check box is hidden. Can someone give m
-
Grants given to a user give to another as well...
How is it possible the grants given to a user , given also to another.... For example : connect scott/tiger; grant select on dept to x; grant insert on dept to x; Many thanks, Simon