When single user sends data to server and notifies AS the table was changed, all things go well.But some users do that at once, AS has possible to hang.
The scenario is simple. When a user completed his transaction and notify AS, AS will prepare to create cache. After time of SilentInterval, AS starts to create cache and commit new cache at the end. If a new NotifyTableChange event has been called just after
AS start to commit the new cache, AS will hang. I have looked this scenario in SQL Server Profiler.
In my thought, AS controls its objects in exclusively access control if it is needed. But just in my case it does not work.
What I want to know are
1. the points I had better to check (because I don't have confidence on my settings)
2. the way to avoid this problem, not in code but in settings or configurations
Thanks,