Home Forums Support PC terminal and mobile terminal connection cannot be returned Reply To: PC terminal and mobile terminal connection cannot be returned

#4337
Anonymous
Inactive

Here the client log (not the one referred to the above server log, but same application)
11.49.17.98 [1 – Trace] – RetrieveConnection by remoteEndPoint=’40.122.xxx.xxx:443′, localEndPoint=’0.0.0.0:0′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’. No matching connections found.
11.49.17.130 [1 – Trace] – Creating new TCPConnection to connectionInfo='[TCP-E-U] 0.0.0.0:0 -> 40.122.xxx.xxx:443′. Connection will be established.
11.49.17.153 [1 – Trace] – Checking for existing connection by remoteEndPoint=’40.122.xxx.xxx:443′, localEndPoint=’0.0.0.0:0′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’.
11.49.17.218 [1 – Trace] – RetrieveConnection by remoteEndPoint=’40.122.xxx.xxx:443′, localEndPoint=’0.0.0.0:0′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’. No matching connections found.
11.49.17.230 [1 – Trace] – Adding connection reference by endPoint. Connection='[TCP-E-U] 0.0.0.0:0 -> 40.122.xxx.xxx:443′.
11.49.17.233 [1 – Trace] – RetrieveConnection by remoteEndPoint=’40.122.xxx.xxx:443′, localEndPoint=’0.0.0.0:0′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Undefined’. No matching connections found.
11.49.17.234 [1 – Trace] – RetrieveConnection by remoteEndPoint=’40.122.xxx.xxx:443′, localEndPoint=’0.0.0.0:0′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Undefined’. No matching connections found.
11.49.17.242 [1 – Trace] – Completed adding connection reference by endPoint. Connection='[TCP-E-U] 0.0.0.0:0 -> 40.122.xxx.xxx:443′.
11.49.17.246 [1 – Trace] – Establishing new connection with [TCP-E-I] 0.0.0.0:0 -> 40.122.xxx.xxx:443
11.49.17.251 [1 – Trace] – Connecting TCP client with [TCP-E-I] 0.0.0.0:0 -> 40.122.xxx.xxx:443
11.49.18.108 [1 – Trace] – Updating connection reference by endPoint. Connection='[TCP-E-I] 0.0.0.0:0 -> 40.122.xxx.xxx:443′. Provided newRemoteEndPoint of 40.122.xxx.xxx:443. Provided newLocalEndPoint of 192.168.2.100:49834.
11.49.18.147 [1 – Trace] – Entering RemoveConnectionReference for [TCP-E-I] 0.0.0.0:0 -> 40.122.xxx.xxx:443
11.49.18.171 [1 – Trace] – Removed connection reference by endPoint for [TCP-E-I] 0.0.0.0:0 -> 40.122.xxx.xxx:443
11.49.18.175 [1 – Trace] – Adding connection reference by endPoint. Connection='[TCP-E-I] 0.0.0.0:0 -> 40.122.xxx.xxx:443′. Provided override endPoint of 40.122.xxx.xxx:443
11.49.18.176 [1 – Trace] – RetrieveConnection by remoteEndPoint=’40.122.xxx.xxx:443′, localEndPoint=’0.0.0.0:0′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Undefined’. No matching connections found.
11.49.18.177 [1 – Trace] – RetrieveConnection by remoteEndPoint=’40.122.xxx.xxx:443′, localEndPoint=’192.168.2.100:49834′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Undefined’. No matching connections found.
11.49.18.178 [1 – Trace] – Completed adding connection reference by endPoint. Connection='[TCP-E-I] 0.0.0.0:0 -> 40.122.xxx.xxx:443′.
11.49.18.188 [1 – Trace] – Checking for existing connection by remoteEndPoint=’40.122.xxx.xxx:443′, localEndPoint=’192.168.2.100:49834′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’.
11.49.18.204 [1 – Trace] – RetrieveConnection by remoteEndPoint=’40.122.xxx.xxx:443′, localEndPoint=’192.168.2.100:49834′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’. 1 matching connections found.
11.49.18.212 [1 – Trace] – Listening for incoming data from [TCP-E-I] 192.168.2.100:49834 -> 40.122.xxx.xxx:443
11.49.18.222 [1 – Debug] – Sending connnectionInfo to [TCP-E-I] 192.168.2.100:49834 -> 40.122.xxx.xxx:443
11.49.18.271 [1 – Trace] – … created packet of type ConnectionSetup. PacketObject data size is 56 bytes
11.49.18.284 [1 – Trace] – Entering packet send of ‘ConnectionSetup’ packetType to [TCP-E-I] 192.168.2.100:49834 -> 40.122.xxx.xxx:443
11.49.18.311 [1 – Debug] – Sending a packet of type ‘ConnectionSetup’ to [TCP-E-I] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 containing 68 header bytes and 56 payload bytes. Allowing 1000,0 ms/KB for send.
11.49.18.494 [1 – Trace] – … 0,121KB sent at average of 1,501KB/s. Current:506,08 ms/KB, Connection Avg:553,29 ms/KB.
11.49.18.497 [1 – Trace] – Completed packet send of ‘ConnectionSetup’ packetType to [TCP-E-I] 192.168.2.100:49834 -> 40.122.xxx.xxx:443
11.49.19.104 [8 – Trace] – … 68 bytes added to packetBuilder for [TCP-E-I] 192.168.2.100:49834 -> 40.122.xxx.xxx:443. Cached 0 bytes, expecting 0 bytes.
11.49.19.118 [8 – Trace] – … added 68 bytes to packetBuilder.
11.49.19.133 [8 – Trace] – … checking for completed packet with 68 bytes read.
11.49.19.136 [8 – Trace] – … deserializing header using 68 bytes, 68 bytes cached.
11.49.19.179 [8 – Trace] – … more data required for complete packet payload. Expecting 119 total packet bytes.
11.49.19.183 [8 – Trace] – … reusing byte[512] from packetBuilder which contains 68 existing bytes.
11.49.19.185 [10 – Trace] – … 119 bytes added to packetBuilder for [TCP-E-I] 192.168.2.100:49834 -> 40.122.xxx.xxx:443. Cached 0 bytes, expecting 119 bytes.
11.49.19.186 [10 – Trace] – … added 119 bytes to packetBuilder.
11.49.19.187 [10 – Trace] – … checking for completed packet with 119 bytes read.
11.49.19.187 [10 – Trace] – … deserializing header using 68 bytes, 119 bytes cached.
11.49.19.196 [10 – Debug] – Received packet of type ‘ConnectionSetup’ from [TCP-E-I] 192.168.2.100:49834 -> 40.122.xxx.xxx:443, containing 68 header bytes and 51 payload bytes.
11.49.19.200 [10 – Trace] – … handling packet type ‘ConnectionSetup’ inline. Loop index – 0. pSeq#-34.
11.49.19.209 [10 – Trace] – Handling a ConnectionSetup packet from [TCP-E-I] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 with a priority of Lowest.
11.49.19.219 [10 – Trace] – RetrieveConnection by remoteEndPoint=’40.122.xxx.xxx:443′, localEndPoint=’192.168.2.100:49834′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’. 1 matching connections found.
11.49.19.221 [10 – Trace] – Updating connection reference by endPoint. Connection='[TCP-E-I] 192.168.2.100:49834 -> 40.122.xxx.xxx:443′. Provided newRemoteEndPoint of 40.122.xxx.xxx:443. Provided newLocalEndPoint of 192.168.2.100:49834.
11.49.19.234 [1 – Trace] – Adding connection reference by identifier. Connection=[TCP-E-E] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg).
11.49.19.235 [1 – Trace] – Checking for existing connection by remoteEndPoint=’40.122.xxx.xxx:443′, localEndPoint=’192.168.2.100:49834′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’.
11.49.19.236 [10 – Trace] – Triggering handlers for packet of type ‘ConnectionSetup’ from [TCP-E-E] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg)
11.49.19.240 [10 – Trace] – Removing 119 bytes from incoming packet builder from connection with [TCP-E-E] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg).
11.49.19.241 [1 – Trace] – RetrieveConnection by remoteEndPoint=’40.122.xxx.xxx:443′, localEndPoint=’192.168.2.100:49834′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’. 1 matching connections found.
11.49.19.248 [10 – Trace] – … removed 119 bytes from packetBuilder.
11.49.19.255 [1 – Trace] – … connection successfully established with [TCP-E-E] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg)
11.49.19.265 [1 – Debug] – Added a connection specific shutdown delegate to connection with [TCP-E-E] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg)
11.49.19.343 [11 – Debug] – Connection keep alive polling thread has started.
11.49.19.362 [1 – Info] – Added connection specific incoming packetHandler for ‘ACK’ packetType with [TCP-E-E] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg)
11.49.19.367 [1 – Trace] – … created packet of type MGLC. PacketObject data size is 540 bytes
11.49.19.371 [1 – Trace] – Entering packet send of ‘MGLC’ packetType to [TCP-E-E] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg)
11.49.19.375 [1 – Debug] – Sending a packet of type ‘MGLC’ to [TCP-E-E] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg) containing 68 header bytes and 540 payload bytes. Allowing 1000,0 ms/KB for send.
11.49.19.387 [1 – Trace] – … 0,594KB sent at average of 75,120KB/s. Current:32,96 ms/KB, Connection Avg:103,52 ms/KB.
11.49.19.393 [1 – Trace] – Completed packet send of ‘MGLC’ packetType to [TCP-E-E] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg)
11.49.20.207 [8 – Trace] – … 73 bytes added to packetBuilder for [TCP-E-E] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg). Cached 0 bytes, expecting 0 bytes.
11.49.20.211 [8 – Trace] – … added 73 bytes to packetBuilder.
11.49.20.214 [8 – Trace] – … checking for completed packet with 73 bytes read.
11.49.20.217 [8 – Trace] – … deserializing header using 56 bytes, 73 bytes cached.
11.49.20.232 [8 – Fatal] – A fatal exception occurred in IncomingPacketHandleHandOff(), connection with [TCP-E-E] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg) be closed. See log file for more information.
11.49.20.257 [8 – Fatal] – /storage/emulated/0/CommsError 11.49.20.256 27-02-2016 [8]
11.49.20.280 [8 – Debug] – Closing connection with [TCP-E-E] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg) due to error from [45].
11.49.20.286 [8 – Trace] – Entering RemoveConnectionReference for [TCP-E-S] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg)
11.49.20.308 [8 – Trace] – Removed connection reference by ID for [TCP-E-S] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg)
11.49.20.309 [8 – Trace] – Removed connection reference by endPoint for [TCP-E-S] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg)
11.49.20.310 [8 – Debug] – Triggered connection specific shutdown delegates with [TCP-E-S] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg)
11.49.20.321 [1 – Info] – Removed a connection specific packetHandler for ‘ACK’ packetType. No handlers remain with [TCP-E-S] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg)
11.49.20.326 [1 – Debug] – Removed ConnectionSpecificShutdownDelegate to connection with [TCP-E-S] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg)
11.49.20.327 [1 – Info] – No handlers remain for ConnectionSpecificShutdownDelegate with [TCP-E-S] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg)
11.49.20.331 [8 – Trace] – … reusing byte[512] from packetBuilder which contains 73 existing bytes.
11.49.20.333 [8 – Debug] – Closing connection with [TCP-E-S] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg) due to error from [13].
11.49.20.334 [8 – Trace] – Entering RemoveConnectionReference for [TCP-E-S] 192.168.2.100:49834 -> 40.122.xxx.xxx:443 (VxLqKttbPkKMfGAX05Obzg)
11.49.49.454 [11 – Trace] – Starting AllConnectionsSendNullPacketKeepAlive
11.49.49.463 [11 – Trace] – RetrieveConnection by remoteEndPoint=’0.0.0.0:0′, localEndPoint=’0.0.0.0:0′, connectionType=’Undefined’ and ApplicationLayerProtocolStatus=’Enabled’. No matching connections found.