search

lnobad / lidgren-network-gen3

Automatically exported from code.google.com/p/lidgren-network-gen3
0 stars 0 forks source link

'Ackonwledge' messages going unhandled by lidgren library? #119

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Fire up server
2. I have a load testing console app that just opens a set number of new 
clients (one per thread) and has them send a random number of messages to the 
server (between 3 and 10 messages per second). These get sent out as broadcasts
3. I had 30 clients connected to the server with everything running well for 
~8mins and then received a whole bunch of ackonwledge messages logged (see 
below). I have tried with smaller client numbers (~15) and still see the same 
issues after a random period of time.

What is the expected output? What do you see instead?
As it seems that there is on NetIncomingMessageType to match the 'Acknowledge' 
message type I'm assuming this is meant to be handled within the library?

In my server I am logging unhandled NetIncomingMessages like so...

                switch (msg.MessageType) {
case NetIncomingMessageType.ConnectionApproval:
                        ...
                        break;
                    case NetIncomingMessageType.Data:
                        var msgType = (NetworkCommandType)msg.ReadByte();
                          ...
                        break;
                    default:
                        Log.Write("Unhandled message type: " + msg.MessageType, LogLevel.Error);
                        break;
}

What version of the product are you using? On what operating system?

Tested on Windows 7 and 8 Consumer Preview using Lidgren3. We updated a few 
months back so it's pretty recent.

Original issue reported on code.google.com by joshua.h...@gmail.com on 26 May 2012 at 2:36

GoogleCodeExporter commented 9 years ago 
"What is the expected output? What do you see instead?"

I'm seeing acknowledge messages going unhandled after what seems to be a random 
period of time then the clients disconnecting. As seen above in my switch 
statement handling of different messages types I am seeing the following 
message logged;

"Unhandled message type: Acknowledge"

Original comment by joshua.h...@gmail.com on 26 May 2012 at 2:40

GoogleCodeExporter commented 9 years ago 
I wasn't sure whether to create a new issue for this or whether I was doing 
something wrong. But I thought I'd try and update to the latest version via 
NuGet(I noticed the NuGet package was updated on 4/5/2012). I'm unable to 
install it though and receive the following error...

Successfully installed 'Lidgren.Network 2012.2.15.2'.
Successfully uninstalled 'Lidgren.Network 2012.2.15.2'.
Install failed. Rolling back...
Could not install package 'Lidgren.Network 2012.2.15.2'. You are trying to 
install this package into a project that targets '.NETFramework,Version=v3.5', 
but the package does not contain any assembly references that are compatible 
with that framework. For more information, contact the package author.

I have also tried targeting .NET 4 on the library I am trying to install it 
into but that fails with the same issue.

Original comment by joshua.h...@gmail.com on 26 May 2012 at 2:48

GoogleCodeExporter commented 9 years ago 
Additional information...

- I have updated to the latest r297 code and am still receiving the same 
behaviour after a couple of minutes
- I have encountered this on both Unreliable and UnreliableSequenced
- I have also noticed the occasional unhandled 'pong' message

I'm not sure whether its the unhandled 'acknowledge' or 'pong' messages that 
ultimately causes the clients to drop.

Original comment by joshua.h...@gmail.com on 28 May 2012 at 12:15