Ok for memory
but for winsock, i'm not the only one in my company to have the problem.
When it's occur it affect all external connexions.
Well, there can be so many factors at play here.
Basically, if you're getting that, then there are two possible problems:
1) You have network issues. It can range from the hosts file to actual connectivity.
2) There is something wrong with the zcs box itself. If there is, then it'll be in the logs.
Is there some mechanism that times out sessions? After several days of trouble shooting with the user, it finally became clear that she is getting this error after the browser has been idle for :30-:40 minutes and then she tries to create a new e-mail or calendar item. And if there is a session timeout of some kind, why does it lock the user out from logging back in?
I am going to upgrade to 4.5.1 this afternoon and see if anything changes.
oh - the java_heap_memory_percent="50" didn't change anything
What happens if you hit "refresh" on the browser? Do things work fine after that?
There are two ways a client can "timeout" but neither of them should cause any problems:
1) The session itself will timeout if it gets nothing from the client for ~10 minutes. The client is supposed to send keepalive requests to the server about every 3 minutes, but if a keepalive fails, the client stops sending them (this is a Known Bug) until the user does something. Usually the session timeout isn't a problem: it just means you stop getting new mail notifications -- the next time you try to do anything, the client should create a new session transparently and things should just work.
2) The auth token will timeout after ~24 hours. When this happens, the next time the client tries to do anything, the user will be taken to the login screen.