Hello,
we want to investigate a problem where messages seem not to arrive at the client. By default, is there any log in the SFS2X when outgoing messages are dropped? If so, what do we have to look for?
Specifically we want to know if the maximum outgoing message queue size is reached, i.e. if the queue is full. The max value is currently at 20,000 and we want to understand if this is too low.
Thanks in advance,
Ruben
Outgoing messages dropped Log
Re: Outgoing messages dropped Log
Hi
No by default there's no log related to dropped messages as it would potentially cause massive log file size.
You can turn on the DEBUG level in the logger and you'll be able to see warnings for specific sessions.
This is highly unlikely. The Outgoing queue is used by the server when it knows it can send data to users.
There's a previous stage however, the User's queue where packets are parked if the network state of that client says that no more data can be received.
In other words, packet dropping happens because the User's queue is filled up. The outgoing queue instead only contains data that is certain to be delivered.
To be even more specific the queue logic is as follows:
- Server wants to send a packet to User1
- Server checks the network state for User1:
When data is parked in the user queue it will stay there until the network state changes from "Can't read any data" to "I am available". At that point the oldest packet in the queue is moved into the Outgoing Q.
Hope it's clear.
rewb0rn wrote:we want to investigate a problem where messages seem not to arrive at the client. By default, is there any log in the SFS2X when outgoing messages are dropped? If so, what do we have to look for?
No by default there's no log related to dropped messages as it would potentially cause massive log file size.
You can turn on the DEBUG level in the logger and you'll be able to see warnings for specific sessions.
Specifically we want to know if the maximum outgoing message queue size is reached, i.e. if the queue is full. The max value is currently at 20,000 and we want to understand if this is too low.
This is highly unlikely. The Outgoing queue is used by the server when it knows it can send data to users.
There's a previous stage however, the User's queue where packets are parked if the network state of that client says that no more data can be received.
In other words, packet dropping happens because the User's queue is filled up. The outgoing queue instead only contains data that is certain to be delivered.
To be even more specific the queue logic is as follows:
- Server wants to send a packet to User1
- Server checks the network state for User1:
- if OK -> put packet in Outgoing Queue,
- if NOT OK -> put packet in User1's queue
When data is parked in the user queue it will stay there until the network state changes from "Can't read any data" to "I am available". At that point the oldest packet in the queue is moved into the Outgoing Q.
Hope it's clear.
Re: Outgoing messages dropped Log
Hi Lapo,
thanks for your response and the additional information on the message queue. I am currently observing the dashboard and I can see that the size of the message queue peaks up to 3,000 messages, and it is not peak time, yet. In user peak times we are also running tournaments, where a lot of messages are sent simultaneously to all users. That's why we thought the message queue size might go over 20,000. What do you think?
Thanks,
Ruben
thanks for your response and the additional information on the message queue. I am currently observing the dashboard and I can see that the size of the message queue peaks up to 3,000 messages, and it is not peak time, yet. In user peak times we are also running tournaments, where a lot of messages are sent simultaneously to all users. That's why we thought the message queue size might go over 20,000. What do you think?
Thanks,
Ruben
Re: Outgoing messages dropped Log
Can you show me a screenshot of the outgoing queue in your server?
Thanks
Thanks
Re: Outgoing messages dropped Log
Hi Lapo,
here is a screenshot from a moment ago. Some time earlier it was showing 3,000 something. There are peaks that regularly go over 2,000.
Thanks,
Ruben
here is a screenshot from a moment ago. Some time earlier it was showing 3,000 something. There are peaks that regularly go over 2,000.
Thanks,
Ruben
Re: Outgoing messages dropped Log
Hi,
those spikes don't represent an issue because are very short lived, which is expected.
They wouldn't look good if instead of a spike they looked like an wide curve, meaning that those messages go into the queue and stay there for a long time.
Also check % of overall dropped packets (AdminTool > Dashboard). If the out value is within 5-8% it's pretty normal: it is expected that a minor portion of users will have slow connections and thus cause dropped packets.
Cheers
those spikes don't represent an issue because are very short lived, which is expected.
They wouldn't look good if instead of a spike they looked like an wide curve, meaning that those messages go into the queue and stay there for a long time.
Also check % of overall dropped packets (AdminTool > Dashboard). If the out value is within 5-8% it's pretty normal: it is expected that a minor portion of users will have slow connections and thus cause dropped packets.
Cheers
Who is online
Users browsing this forum: No registered users and 57 guests