- This topic has 10 replies, 3 voices, and was last updated 8 years, 9 months ago by
.
-
Posts
-
The PC terminal and the mobile terminal is connected, the PC terminal can be mobile terminal, receiving cannot return
android：
string i = NetworkComms.SendReceiveObject<string, string>(“1111”, “192.168.43.155”, 6003, “11”, 1000, “1”);
Toast.MakeText(this, i, ToastLength.Long).Show();PC：
NetworkComms.AppendGlobalIncomingPacketHandler<string>(“1111”, (header, connection, message) =>
{
Console.WriteLine(message);
connection.SendObject(“11”, “2”);});
NetworkCommsDotNet.ConnectionShutdownException: Remote end closed connection bef
ore data was successfully returned.
at NetworkCommsDotNet.Connections.Connection.SendReceiveObject[String,String]
(System.String sendingPacketTypeStr, System.String expectedReturnPacketTypeStr,
Int32 returnPacketTimeOutMilliSeconds, System.String sendObject, NetworkCommsDot
Net.SendReceiveOptions sendOptions, NetworkCommsDotNet.SendReceiveOptions receiv
eOptions, System.Int64& sentPacketSequenceNumber) [0x00000] in <filename unknown
>:0
at NetworkCommsDotNet.Connections.Connection.SendReceiveObject[String,String]
(System.String sendingPacketTypeStr, System.String expectedReturnPacketTypeStr,
Int32 returnPacketTimeOutMilliSeconds, System.String sendObject, NetworkCommsDot
Net.SendReceiveOptions sendOptions, NetworkCommsDotNet.SendReceiveOptions receiv
eOptions) [0x00000] in <filename unknown>:0
at NetworkCommsDotNet.Connections.Connection.SendReceiveObject[String,String]
(System.String sendingPacketTypeStr, System.String expectedReturnPacketTypeStr,
Int32 returnPacketTimeOutMilliSeconds, System.String sendObject) [0x00000] in <f
ilename unknown>:0
at FlyOutMenu.Login.btnLogin_Click (System.Object sender, System.EventArgs e)
[0x00000] in <filename unknown>:0Heya a77a77a777,
There is not enough code there to know what the problem may be. Please post more code, but importantly please use the ‘Code’ tags so that it is formatted correctly.
Regards,
MarcThanks for your reply，
I think Android and PC communication like PC and PC like structures, with a few simple code can，But the PC end as the receiving end，Can receive it each time, and Android did not receive the return value。
PC：//The message may receive value NetworkComms.AppendGlobalIncomingPacketHandler<string>("Message", (header, connection, message) => { Console.WriteLine(message); Console.WriteLine(connection.ConnectionInfo.RemoteEndPoint); connection.SendObject("Retuen", "1"); }); Connection.StartListening(ConnectionType.TCP, new IPEndPoint(IPAddress.Parse(ip), port)); Console.ReadKey(true);Android：
`
//I cannot receive the return value
string i = NetworkComms.SendReceiveObject<string, string>(“Message”, ip, port, “Retuen”, 1000, “Hello Word”);`A few questions:
1. What error occurs on the android client?
2. What happens if you create the connection differently in android:ConnectionInfo info = new ConnectionInfo(ip, port); TCPConnection conn = TCPConnection.GetConnection(info); string i = conn.SendReceiveObject<string, string>("Message", "Retuen", 1000, "Hello Word");Regards,
Marcusing System; using Android.App; using Android.Content; using Android.Runtime; using Android.Views; using Android.Widget; using Android.OS; using System.Xml.Linq; using FlyOutMenu.Model; using NetworkCommsDotNet; using NetworkCommsDotNet.Connections; using System.Net; using NetworkCommsDotNet.Connections.TCP; namespace FlyOutMenu { [Activity (Label = "FlyInMenu", MainLauncher = true, Theme = "@android:style/Theme.Holo.Light.NoActionBar")] public class Login : Activity { string ip="192.168.43.155"; int port=6003; protected override void OnCreate (Bundle bundle) { base.OnCreate (bundle); // Set our view from the "main" layout resource SetContentView (Resource.Layout.Login); Button btnLogin = FindViewById<Button>(Resource.Id.login); btnLogin.Click += new EventHandler(btnLogin_Click); TextView txtSheZhi = FindViewById<TextView>(Resource.Id.SheZhi); txtSheZhi.Click += new EventHandler(txtSheZhi_Click); } //Trigger when click the login button void btnLogin_Click(object sender, EventArgs e) { try { ConnectionInfo info = new ConnectionInfo(ip, port); TCPConnection conn = TCPConnection.GetConnection(info); string i = conn.SendReceiveObject<string, string>("Message", "Re", 1000, "Hello word"); Toast.MakeText(this, i, ToastLength.Long).Show(); } catch (Exception ex) { Toast.MakeText(this, ex.ToString(), ToastLength.Long).Show(); } } } }PC is already successfully received the “Hello word”.
When the PC terminal to send a return value back to the Android, but that such errors.The same mistake:
NetworkCommsDotNet.ConnectionShutdownException: Remote end closed connection bef
ore data was successfully returned.
at NetworkCommsDotNet.Connections.Connection.SendReceiveObject[String,String]
(System.String sendingPacketTypeStr, System.String expectedReturnPacketTypeStr,
Int32 returnPacketTimeOutMilliSeconds, System.String sendObject, NetworkCommsDot
Net.SendReceiveOptions sendOptions, NetworkCommsDotNet.SendReceiveOptions receiv
eOptions, System.Int64& sentPacketSequenceNumber) [0x00000] in <filename unknown
>:0
at NetworkCommsDotNet.Connections.Connection.SendReceiveObject[String,String]
(System.String sendingPacketTypeStr, System.String expectedReturnPacketTypeStr,
Int32 returnPacketTimeOutMilliSeconds, System.String sendObject, NetworkCommsDot
Net.SendReceiveOptions sendOptions, NetworkCommsDotNet.SendReceiveOptions receiv
eOptions) [0x00000] in <filename unknown>:0
at NetworkCommsDotNet.Connections.Connection.SendReceiveObject[String,String]
(System.String sendingPacketTypeStr, System.String expectedReturnPacketTypeStr,
Int32 returnPacketTimeOutMilliSeconds, System.String sendObject) [0x00000] in <f
ilename unknown>:0
at FlyOutMenu.Login.btnLogin_Click (System.Object sender, System.EventArgs e)
[0x00000] in <filename unknown>:0NetworkCommsDotNet 2.3 Edition can be used normally, and the 3.0 can not
Interesting, something strange is going on. If you could enable logging for both server and client, https://networkcomms.net/enable-logging/, and post the logs here that should help me resolve the problem. Also please post your server code.
Hi MarcF, now I have the same issue. Server side perfect, with many windows clients at the same time. I’m able to transfer via sendreceive messages and file. With xamarin android no way. The client send the message, the server receives the message, send the answer and close the connection… but the android client receive nothing.
The error is: Remote end closed connection before data was succesfully returned.
Here the server log:
10.19.22.950 [1 – Trace] – —————————————————————————-
10.19.22.950 [1 – Trace] – c:\pennytools\pennyserver\pennyserver.exe
10.19.22.950 [1 – Trace] – InitializeComponent
10.19.23.559 [7 – Trace] – OnStart
10.19.23.762 [8 – Trace] – AppendGlobalIncomingPacketHandler
10.19.23.762 [8 – Info] – Added incoming packetHandler for ‘MFMQ’ packetType.
10.19.23.762 [8 – Info] – Added incoming packetHandler for ‘MNEW’ packetType.
10.19.23.762 [8 – Info] – Added incoming packetHandler for ‘MSET’ packetType.
10.19.23.778 [8 – Info] – Added incoming packetHandler for ‘MGET’ packetType.
10.19.23.778 [8 – Info] – Added incoming packetHandler for ‘MDEL’ packetType.
10.19.23.778 [8 – Info] – Added incoming packetHandler for ‘MGLC’ packetType.
10.19.23.778 [8 – Info] – Added incoming packetHandler for ‘GANA’ packetType.
10.19.23.778 [8 – Info] – Added incoming packetHandler for ‘SANA’ packetType.
10.19.23.778 [8 – Trace] – StartListening on:
10.19.23.887 [8 – Info] – Created new connection listener (TCP-E).
10.19.23.887 [8 – Info] – Created new connection listener (TCP-E).
10.19.23.887 [8 – Info] – Created new connection listener (TCP-E).
10.19.24.12 [8 – Info] – Listener started (TCP-E – 10.0.0.4:443).
10.19.24.12 [8 – Info] – Listener started (TCP-E – [::1]:443).
10.19.24.28 [8 – Info] – Listener started (TCP-E – 127.0.0.1:443).
10.19.24.28 [8 – Trace] – 10.0.0.4:443
10.19.24.28 [8 – Trace] – ::1:443
10.19.24.28 [8 – Trace] – 127.0.0.1:443
10.19.24.28 [8 – Trace] – loop while service not stopped…
10.19.59.497 [11 – Info] – New incoming TCP connection from [TCP-E-U] 10.0.0.4:443 -> 93.32.67.165:4429
10.19.59.560 [12 – Trace] – RetrieveConnection by remoteEndPoint=’93.32.67.165:4429′, localEndPoint=’10.0.0.4:443′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’. No matching connections found.
10.19.59.560 [12 – Trace] – Creating new TCPConnection to connectionInfo='[TCP-E-U] 10.0.0.4:443 -> 93.32.67.165:4429′. Connection will be established.
10.19.59.575 [12 – Info] – Appended connection specific packet handlers from listener ‘[TCP-E] Listening – 10.0.0.4:443’ to connection ‘[TCP-E-U] 10.0.0.4:443 -> 93.32.67.165:4429′.
10.19.59.591 [12 – Trace] – Checking for existing connection by remoteEndPoint=’93.32.67.165:4429′, localEndPoint=’10.0.0.4:443′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’.
10.19.59.591 [12 – Trace] – RetrieveConnection by remoteEndPoint=’93.32.67.165:4429′, localEndPoint=’10.0.0.4:443′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’. No matching connections found.
10.19.59.607 [12 – Trace] – Adding connection reference by endPoint. Connection='[TCP-E-U] 10.0.0.4:443 -> 93.32.67.165:4429′.
10.19.59.607 [12 – Trace] – RetrieveConnection by remoteEndPoint=’93.32.67.165:4429′, localEndPoint=’10.0.0.4:443′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Undefined’. No matching connections found.
10.19.59.607 [12 – Trace] – RetrieveConnection by remoteEndPoint=’93.32.67.165:4429′, localEndPoint=’10.0.0.4:443′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Undefined’. No matching connections found.
10.19.59.607 [12 – Trace] – Completed adding connection reference by endPoint. Connection='[TCP-E-U] 10.0.0.4:443 -> 93.32.67.165:4429′.
10.19.59.607 [12 – Trace] – Establishing new connection with [TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:4429
10.19.59.607 [12 – Trace] – Updating connection reference by endPoint. Connection='[TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:4429′. Provided newRemoteEndPoint of 93.32.67.165:4429. Provided newLocalEndPoint of 10.0.0.4:443.
10.19.59.622 [12 – Trace] – Checking for existing connection by remoteEndPoint=’93.32.67.165:4429′, localEndPoint=’10.0.0.4:443′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’.
10.19.59.622 [12 – Trace] – RetrieveConnection by remoteEndPoint=’93.32.67.165:4429′, localEndPoint=’10.0.0.4:443′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’. 1 matching connections found.
10.19.59.622 [12 – Trace] – Listening for incoming data from [TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:4429
10.19.59.638 [12 – Debug] – Waiting for client connnectionInfo from [TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:4429
10.20.0.169 [11 – Trace] – … 68 bytes added to packetBuilder for [TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:4429. Cached 0 bytes, expecting 0 bytes.
10.20.0.169 [11 – Trace] – … added 68 bytes to packetBuilder.
10.20.0.200 [11 – Trace] – … checking for completed packet with 68 bytes read.
10.20.0.200 [11 – Trace] – … deserializing header using 68 bytes, 68 bytes cached.
10.20.0.263 [11 – Trace] – … more data required for complete packet payload. Expecting 120 total packet bytes.
10.20.0.263 [11 – Trace] – … reusing byte[512] from packetBuilder which contains 68 existing bytes.
10.20.0.529 [13 – Trace] – … 120 bytes added to packetBuilder for [TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:4429. Cached 0 bytes, expecting 120 bytes.
10.20.0.529 [13 – Trace] – … added 120 bytes to packetBuilder.
10.20.0.529 [13 – Trace] – … checking for completed packet with 120 bytes read.
10.20.0.529 [13 – Trace] – … deserializing header using 68 bytes, 120 bytes cached.
10.20.0.544 [13 – Debug] – Received packet of type ‘ConnectionSetup’ from [TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:4429, containing 68 header bytes and 52 payload bytes.
10.20.0.544 [13 – Trace] – … handling packet type ‘ConnectionSetup’ inline. Loop index – 0. pSeq#-1.
10.20.0.575 [13 – Trace] – Handling a ConnectionSetup packet from [TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:4429 with a priority of AboveNormal.
10.20.0.591 [13 – Trace] – RetrieveConnection by remoteEndPoint=’93.32.67.165:4429′, localEndPoint=’10.0.0.4:443′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’. 1 matching connections found.
10.20.0.591 [13 – Trace] – Updating connection reference by endPoint. Connection='[TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:4429′. Provided newRemoteEndPoint of 93.32.67.165:53238. Provided newLocalEndPoint of 10.0.0.4:443.
10.20.0.591 [13 – Trace] – Entering RemoveConnectionReference for [TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:4429
10.20.0.607 [13 – Trace] – Removed connection reference by endPoint for [TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:4429
10.20.0.607 [13 – Trace] – Adding connection reference by endPoint. Connection='[TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:4429′. Provided override endPoint of 93.32.67.165:53238
10.20.0.607 [13 – Trace] – RetrieveConnection by remoteEndPoint=’93.32.67.165:53238′, localEndPoint=’10.0.0.4:443′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Undefined’. No matching connections found.
10.20.0.607 [13 – Trace] – RetrieveConnection by remoteEndPoint=’93.32.67.165:53238′, localEndPoint=’10.0.0.4:443′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Undefined’. No matching connections found.
10.20.0.607 [13 – Trace] – Completed adding connection reference by endPoint. Connection='[TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:4429′.
10.20.0.654 [13 – Trace] – … created packet of type ConnectionSetup. PacketObject data size is 51 bytes
10.20.0.685 [13 – Trace] – Entering packet send of ‘ConnectionSetup’ packetType to [TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ)
10.20.0.700 [13 – Debug] – Sending a packet of type ‘ConnectionSetup’ to [TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ) containing 68 header bytes and 51 payload bytes. Allowing 1000.0 ms/KB for send.
10.20.0.763 [13 – Trace] – … 0.116KB sent at average of 1.859KB/s. Current:361.41 ms/KB, Connection Avg:413.04 ms/KB.
10.20.0.763 [13 – Trace] – Completed packet send of ‘ConnectionSetup’ packetType to [TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ)
10.20.0.763 [13 – Trace] – Triggering handlers for packet of type ‘ConnectionSetup’ from [TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ)
10.20.0.763 [13 – Trace] – Removing 120 bytes from incoming packet builder from connection with [TCP-E-I] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ).
10.20.0.779 [13 – Trace] – … removed 120 bytes from packetBuilder.
10.20.0.794 [12 – Trace] – Adding connection reference by identifier. Connection=[TCP-E-E] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ).
10.20.0.794 [12 – Trace] – Checking for existing connection by remoteEndPoint=’93.32.67.165:53238′, localEndPoint=’10.0.0.4:443′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’.
10.20.0.794 [12 – Trace] – RetrieveConnection by remoteEndPoint=’93.32.67.165:53238′, localEndPoint=’10.0.0.4:443′, connectionType=’TCP’ and ApplicationLayerProtocolStatus=’Enabled’. 1 matching connections found.
10.20.0.794 [12 – Trace] – … connection successfully established with [TCP-E-E] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ)
10.20.0.810 [15 – Debug] – Connection keep alive polling thread has started.
10.20.1.341 [14 – Trace] – … 68 bytes added to packetBuilder for [TCP-E-E] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ). Cached 0 bytes, expecting 0 bytes.
10.20.1.341 [14 – Trace] – … added 68 bytes to packetBuilder.
10.20.1.341 [14 – Trace] – … checking for completed packet with 68 bytes read.
10.20.1.341 [14 – Trace] – … deserializing header using 68 bytes, 68 bytes cached.
10.20.1.341 [14 – Trace] – … more data required for complete packet payload. Expecting 608 total packet bytes.
10.20.1.341 [14 – Trace] – … reusing byte[512] from packetBuilder which contains 68 existing bytes.
10.20.1.810 [14 – Trace] – … 512 bytes added to packetBuilder for [TCP-E-E] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ). Cached 0 bytes, expecting 608 bytes.
10.20.1.810 [14 – Trace] – … added 512 bytes to packetBuilder.
10.20.1.825 [14 – Trace] – … 96 bytes added to packetBuilder for [TCP-E-E] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ). Cached 512 bytes, expecting 608 bytes.
10.20.1.825 [14 – Trace] – … added 96 bytes to packetBuilder.
10.20.1.825 [14 – Trace] – … checking for completed packet with 608 bytes read.
10.20.1.825 [14 – Trace] – … deserializing header using 68 bytes, 608 bytes cached.
10.20.1.825 [14 – Debug] – Received packet of type ‘MGLC’ from [TCP-E-E] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ), containing 68 header bytes and 540 payload bytes.
10.20.1.825 [16 – Trace] – Handling a MGLC packet from [TCP-E-E] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ) with a priority of Normal.
10.20.1.825 [14 – Trace] – … added completed MGLC packet to thread pool (Q:0, T:1, I:0) with priority Normal. Selected threadId=16. Loop index=0. pSeq#-2.
10.20.1.841 [14 – Trace] – Removing 608 bytes from incoming packet builder from connection with [TCP-E-E] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ).
10.20.1.841 [14 – Trace] – … removed 608 bytes from packetBuilder.
10.20.1.841 [16 – Trace] – Triggering handlers for packet of type ‘MGLC’ from [TCP-E-E] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ)
10.20.1.841 [16 – Trace] – … passing completed data packet of type ‘MGLC’ to 1 selected global handlers.
10.20.1.872 [16 – Trace] – MGLC:ID1601000001|PB|2016022611195745|cqS2A9zNeGZyv8N/Y/srBBrUs0W1Mda6Yc6JdJlQ6ug=| | | | | |x37xj7FfHatgX3sXDoUc9g==
10.20.1.982 [16 – Trace] – MGLC 410 no file lic
10.20.2.60 [16 – Trace] – … created packet of type ACK. PacketObject data size is 17 bytes
10.20.2.60 [16 – Trace] – Entering packet send of ‘ACK’ packetType to [TCP-E-E] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ)
10.20.2.60 [16 – Debug] – Sending a packet of type ‘ACK’ to [TCP-E-E] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ) containing 56 header bytes and 17 payload bytes. Allowing 1000.0 ms/KB for send.
10.20.2.107 [16 – Trace] – … 0.071KB sent at average of 1.521KB/s. Current:347.43 ms/KB, Connection Avg:458.67 ms/KB.
10.20.2.107 [16 – Trace] – Completed packet send of ‘ACK’ packetType to [TCP-E-E] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ)
10.20.2.107 [16 – Trace] – … all handlers for packet of type ‘MGLC’ completed.
10.20.2.310 [14 – Debug] – Closing connection with [TCP-E-E] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ) from [-2].
10.20.2.310 [14 – Trace] – Entering RemoveConnectionReference for [TCP-E-S] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ)
10.20.2.325 [14 – Trace] – Removed connection reference by ID for [TCP-E-S] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ)
10.20.2.325 [14 – Trace] – Removed connection reference by endPoint for [TCP-E-S] 10.0.0.4:443 -> 93.32.67.165:53238 (eHVSO82b3UWSA2nd-CbShQ)The log is the same for a windows client that works…
I tested it with xamarin android emulator, xamarin player, and a samsung S4 lollipop…
I tried (server side)
SendReceiveOptions options = (SendReceiveOptions)NetworkComms.DefaultSendReceiveOptions.Clone();
options.ReceiveConfirmationRequired = true;
NetworkComms.AppendGlobalIncomingPacketHandler<string>(“MGLC”, MessageForMeQuery);What can I do?
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.
- You must be logged in to reply to this topic.