- This topic has 0 replies, 1 voice, and was last updated 8 years, 1 month ago by Anonymous.
Viewing 1 post (of 1 total)
-
AuthorPosts
-
October 13, 2016 at 19:04 #4419AnonymousInactive
Hi all,
I have a NetworkComms.Net Connection between Client and Server (TCP Socket IPv4) using the RPC functionality. Additional I send unsolicited packages to the client when some events on server-side occurs.
But sometimes my client connection is disconnected by fatal error on client-side:
13:44:48.2972942: Notice Network Added connection specific incoming packetHandler for 'IRPC_Commander-RPC-CALL-TPPEzBVU/3bB/b/69pCspk/lUPw=-5gI9RWcqS0GUQ0sj175V1A' packetType with [TCP-E-E] 10.1.3.126:52156 -> 10.1.3.102:10000 (WTYZKfNDQkWGstQ88W0IKQ) 13:44:48.3010443: Notice Network Removed a connection specific packetHandler for 'IRPC_Commander-RPC-CALL-TPPEzBVU/3bB/b/69pCspk/lUPw=-5gI9RWcqS0GUQ0sj175V1A' packetType. No handlers remain with [TCP-E-E] 10.1.3.126:52156 -> 10.1.3.102:10000 (WTYZKfNDQkWGstQ88W0IKQ) 13:44:48.3010443: Notice Network No handlers remain for ConnectionSpecificShutdownDelegate with [TCP-E-E] 10.1.3.126:52156 -> 10.1.3.102:10000 (WTYZKfNDQkWGstQ88W0IKQ) 13:44:50.7223315: Trace Input Freisprechen PTT losgelassen 13:44:50.7235815: Notice Network Added connection specific incoming packetHandler for 'IRPC_Commander-RPC-CALL-TPPEzBVU/3bB/b/69pCspk/lUPw=-Ozv4O92D-UeOiIdLBtUHGQ' packetType with [TCP-E-E] 10.1.3.126:52156 -> 10.1.3.102:10000 (WTYZKfNDQkWGstQ88W0IKQ) 13:44:50.7260815: Notice Network Removed a connection specific packetHandler for 'IRPC_Commander-RPC-CALL-TPPEzBVU/3bB/b/69pCspk/lUPw=-Ozv4O92D-UeOiIdLBtUHGQ' packetType. No handlers remain with [TCP-E-E] 10.1.3.126:52156 -> 10.1.3.102:10000 (WTYZKfNDQkWGstQ88W0IKQ) 13:44:50.7273315: Notice Network No handlers remain for ConnectionSpecificShutdownDelegate with [TCP-E-E] 10.1.3.126:52156 -> 10.1.3.102:10000 (WTYZKfNDQkWGstQ88W0IKQ) 13:46:33.4164088: Warning Network Packet builder cache contains 0,3KB when only 0,1KB were expected. 13:48:41.2383721: Critical Exception Failed to deserialize a valid packet header. Deserialized header result was null or did not contain the compulsory fields, TotalPayloadSize and PacketType. 13:48:41.2421222: Critical Exception Invalid wire-type; this usually means you have over-written a file without truncating or setting the length; see http://stackoverflow.com/q/2152978/23354 13:48:41.2433722: Critical Network A fatal exception occurred in IncomingPacketHandleHandOff(), connection with [TCP-E-E] 10.1.3.126:52156 -> 10.1.3.102:10000 (WTYZKfNDQkWGstQ88W0IKQ) be closed. See log file for more information. 13:48:41.2471223: Critical Network An unhanded exception occurred in CompleteIncomingPacketWorker(), connection with [TCP-E-E] 10.1.3.126:52156 -> 10.1.3.102:10000 (WTYZKfNDQkWGstQ88W0IKQ) be closed. See log file for more information. 13:48:41.2471223: Critical Exception Error deserializing packetHeader. NetworkCommsDotNet.SerialisationException: Failed to deserialize a valid packet header. Deserialized header result was null or did not contain the compulsory fields, TotalPayloadSize and PacketType.\r\n bei NetworkCommsDotNet.PacketHeader..ctor(MemoryStream packetHeaderStream, SendReceiveOptions headerSendReceiveOptions) in c:\Users\Karnifexx\Documents\Visual Studio 2010\Projects\networkcomms.net\NetworkCommsDotNet\PacketHeader.cs:Zeile 166. 13:48:41.2496223: Message Connection Disconnected!
Do you have an idea why this happens? Is it possible that different threads, sending unsolicited packets in unpredictable moments, can trigger some byte mixup on client side? I thought it will be queued in the library.
Do you had any similar problems?Best regards,
Holger- This topic was modified 8 years, 1 month ago by .
-
AuthorPosts
Viewing 1 post (of 1 total)
- You must be logged in to reply to this topic.