My problem sounds similar to this one: When i am connecting directly, everything is fine. When i connect through the bluebox, at some points my client stops reveiving messages.
Sending still works. Other people receive my chatmessages and Variable-updates, but i don't even receive my own public messages.
I could not yet pinpoint the exact moment when this happens. There seems to be no special message perceeding the blackout. The Message Queue ( http://IP/BlueBox/HttpBox.do?debugCmd=main ) starts to fill up, and eventually my client is disconnected.
Here's what the debugCmd says:
Code: Select all
Logging level: FINER
Client idle time: 2500
Client idle request time: 1200
Active sessions: 1
SessionId Q Size Creation Last Act. Last Req.
5fd... ...a29 1 11:17:25 11:17:43 11:17:43
This time, it happened approximately 18 seconds after my connection, so i doubt it can be a timeout already. The que is already filling up. This one would have been another user joining the room.
Jetty Runs on 80, SFS runs on 9600. I found references to the client_request_idle_time so i added it to my config like this:
Code: Select all
# This value should always be > 20. A value of 30 is recommended.
client_idle_time=2500
# found forum-post about bluebox. added it in here for debugging.
client_idle_request_time=300
SFS is 1.6.5, Bluebox is 1.0.5 (both updated from clean installed 1.6.2 SFS Pro)
My greatest problem here is: How do i debug this. I tried Wireshark, but i can't find anything out of the ordinary.
Any help will be greatly appreciated.