Where I can change the maximum number of "Client HTTP queue" ?
I have many errors like:
Client HTTP queue limit was reached
This setting is not available yet. It will in the final version.
However the current default is already set to an optimal value and if you changed it you would probably get little benefit.
The error you see depends on the fact that the clients connected to the BlueBox have a very bad connection and they are not able to keep up with the transmission rate.
If you get too many of these errors you might need to investigate on your side for network problems, such as high lag or bandwidth limits.
Lag problems, actually, are a bit difficult to diagnose because they depend on where the User is coming from.
For instance your ISP might have a bad lag only for users connecting from south America, or Australia etc...
Big companies solve this issue by running multiple servers in different regions of the world to provide good connectivity.
hope it helps
However the current default is already set to an optimal value and if you changed it you would probably get little benefit.
The error you see depends on the fact that the clients connected to the BlueBox have a very bad connection and they are not able to keep up with the transmission rate.
If you get too many of these errors you might need to investigate on your side for network problems, such as high lag or bandwidth limits.
Lag problems, actually, are a bit difficult to diagnose because they depend on where the User is coming from.
For instance your ISP might have a bad lag only for users connecting from south America, or Australia etc...
Big companies solve this issue by running multiple servers in different regions of the world to provide good connectivity.
hope it helps
-
- Posts: 5
- Joined: 22 Jun 2011, 09:36
-
- Posts: 1
- Joined: 08 Dec 2008, 08:29
Re: Client HTTP queue limit was reached
We can't find any config for this limit in the final version.
Re: Client HTTP queue limit was reached
The parameter is not configurable. If a client generates that error it is definitely too slow and problematic.
The error gets logged and does no harm to the server at all. It's just a notification.
@ajay.bhosle
There is no relation between the two events. You should check the server logs and see what other errors there are.
The error gets logged and does no harm to the server at all. It's just a notification.
@ajay.bhosle
There is no relation between the two events. You should check the server logs and see what other errors there are.
-
- Posts: 81
- Joined: 13 Sep 2011, 15:59
- Location: Nitra, Slovakia
- Contact:
Re: Client HTTP queue limit was reached
Hi guys, I have same problem with
1. IllegalStateException
"java.lang.IllegalStateException: Client HTTP queue limit was reached: {BBClient - { Id: .... "
and shortly thereafter I get
2 ERROR
"SocketReader] protocol.SFSProtocolCodec - RequestQueue is full (40000/40000). Controller ID: 1, Dropping incoming request:"
and my game is unable to work properly. Client cofing useBlueBox = true, I thinking about to set useBlueBox=false.
Can 1. IllegalStateException evoke 2 ERROR ???
1. IllegalStateException
"java.lang.IllegalStateException: Client HTTP queue limit was reached: {BBClient - { Id: .... "
and shortly thereafter I get
2 ERROR
"SocketReader] protocol.SFSProtocolCodec - RequestQueue is full (40000/40000). Controller ID: 1, Dropping incoming request:"
and my game is unable to work properly. Client cofing useBlueBox = true, I thinking about to set useBlueBox=false.
Can 1. IllegalStateException evoke 2 ERROR ???
Re: Client HTTP queue limit was reached
Problem 1) is already explained in my previous post
There's something wrong on your server side. Not enough resources, or it could be a DDOS. It is very difficult to say without know all the details. Anywaysi f you have over 40K messages in the read queue, something is going pretty wrong.
Can you describe what hardware are you using, and under which load this happens?
Also specify which server version are you using
2 ERROR
"SocketReader] protocol.SFSProtocolCodec - RequestQueue is full (40000/40000). Controller ID: 1, Dropping incoming request:"
There's something wrong on your server side. Not enough resources, or it could be a DDOS. It is very difficult to say without know all the details. Anywaysi f you have over 40K messages in the read queue, something is going pretty wrong.
Can you describe what hardware are you using, and under which load this happens?
Also specify which server version are you using
Re: Client HTTP queue limit was reached
We are experiencing the same problem infrequently. (it is only the
here.)
After having this error multiple times, it doesn't acceppt any logins.
Could this have any relation to the problem discussed here: viewtopic.php?f=18&t=10198 ?
Otherwise could you provide any more hints on how to reproduce this and or detect code that could cause this?
Code: Select all
24 Apr 2012 | 17:24:06,066 | WARN | SocketWriter-1 | bitswarm.core.SocketWriter | | Problems in SocketWriter main loop, Thread: Thread[SocketWriter-1,5,main]
24 Apr 2012 | 17:24:06,070 | WARN | SocketWriter-1 | bitswarm.core.SocketWriter | |
java.lang.IllegalStateException: Client HTTP queue limit was reached: {BBClient - { Id: 408, Type: BLUEBOX, Logged: Yes, IP: 178.196.37.17 }, 391f798a2c9151e611d558f645e4d03f}(limit=120)
here.)
After having this error multiple times, it doesn't acceppt any logins.
Could this have any relation to the problem discussed here: viewtopic.php?f=18&t=10198 ?
Otherwise could you provide any more hints on how to reproduce this and or detect code that could cause this?
Who is online
Users browsing this forum: No registered users and 57 guests