Page 2 of 2
More users than sessions
Posted: 17 Jul 2011, 04:20
by Fraggle
Hi again,
I would really appreciate some feedback from the smartfox team on my issues.
At the moment (after 3 days uptime) I got 1050 CCU wich is the same as the number of sessions displayed on the admin panel, but I got 2600 "users logged in". I really don't understand what can cause this issue.
When I start the server, both numbers are really close.
Thanks,
Sebastien
Posted: 18 Jul 2011, 08:24
by Lapo
Yes thanks,
this is a known bug with the admin tool, it's going to be fixed soon
Posted: 18 Jul 2011, 11:47
by Fraggle
Hi Lapo,
Thanks for the quick response, but can you also checkout my other questions ?
I have tweaked the various threads values but the server still "lock" at some point, not processing any new incoming connexion, with a bunch of:
Code: Select all
18 Jul 2011 14:40:17,474 WARN [Scheduler1-thread-1] bitswarm.sessions.DefaultSessionManager - Failed closing connection while removing idle Session: { Id: 164, Type: DEFAULT, Logged: No, IP: 192.168.2.82:11149 }
Those exceptions never happen when the server is running smoothly.
Can you point me in the right direction or give me some clues about where to look?
Thanks,
Sebastien
Posted: 22 Jul 2011, 07:44
by Lapo
If the server "locks" you should create a thread dump and see what's happening or send it to us.
Use jconsole or VisualVM to create a dump.
Those error messages are not so bad, they can happen due to network errors. They can't be responsible for any errors.
Thanks.
Posted: 22 Jul 2011, 07:54
by Fraggle
Hi,
Our server is running on a remote linux. I cannot run any graphical tool.
Can you explain to me exactly how I can provide you with the necessary information ?
I dont know if it's of any interrest, but we noticed using strace during an issue that one of the java thread was cycling very very quickly with E_TIMEOUT on the same memory address, nothing like other threads.
I'm not a specialist of thoses low level stuff, so I may be saying something stupid there.
Thanks,
Sebastien
Posted: 22 Jul 2011, 14:07
by Lapo
You can obtain a full thread dump by sending kill -SIGQUIT to the process (under Linux/Unix)
Posted: 22 Jul 2011, 15:03
by Fraggle
To the main process or to each threads one by one (there can be a few of them

) ?
Sebastien
Posted: 23 Jul 2011, 10:17
by Lapo
Main process, threads live in the JVM and you can't see them from outside. And by "outside" I mean the OS. Ok?
You go with ---> kill -SIGQUIT <processId>