2

We have a web application running which having around 100 users logged in, All clients are connected to server using websync. I was having requirement for keeping the session always live, so I am regenerating session when it is about to expire.

But after 3 or 4 days, I found cpu reached to 100% and application locked, then we need to restart the server to make it working.

Thanks for providing solutions in advance.

Thanks

BK Komal
  • 59
  • 1
  • 3
  • If you've purchased a license (as you must have to support > 10 concurrent users), I suggest contacting their support team :) – Anton Feb 06 '11 at 18:56

3 Answers3

2

Why don't you just extend the session duration to be extremely long instead of regenerating it?

Have you run a profiler against the server when it reaches 100% cpu? This should effectively tell you which methods/classes are being run in how many different threads. With this information you can figure out why your application is running those methods/classes across what I'm guessing is a lot of threads.

Macy Abbey
  • 3,877
  • 1
  • 20
  • 30
2

We've got plenty of clients using WebSync with tens of thousands of concurrent connections (and our On-Demand cluster sits at multiple thousands of users nonstop every day as well), so if you're seeing a CPU lockup, more than likely you've got a threading issue in your code, probably in one of your events (assuming it's related to the WebSync code at all).

Don't forget that the WebSync events are all static, so if you're using shared resources, you'll need to manage them accordingly (i.e., you have to count on the fact that they're multi-threaded). All the WebSync methods themselves are threadsafe, but if you've got stuff in your own events, you'll need to manage that yourself.

Feel free to chat with us directly though, as @Anton suggested!

Jerod Venema
  • 44,124
  • 5
  • 66
  • 109
1

As we deal with before, Windows update maybe reason for 100% CPU.

Zuuum
  • 1,495
  • 11
  • 18