Home › Forums › Support › PC terminal and mobile terminal connection cannot be returned › Reply To: PC terminal and mobile terminal connection cannot be returned
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?