I have another idea - TrackStudio 3.5 likes to "eat" DBMS connections, this can lead to such problem.
This problem has been likely fixed in this version:
SA + JRE for Windows: http://www.trackstudio.com/tse-35/Track ... th_jre.exe
SA + JRE for Linux: http://www.trackstudio.com/tse-35/Track ... jre.tar.gz
SA for Windows: http://www.trackstudio.com/tse-35/Track ... indows.exe
SA for UNIX: http://www.trackstudio.com/tse-35/Track ... nix.tar.gz
WAR: http://www.trackstudio.com/tse-35/TrackStudio_3558.zip
We have also introduced .vmoptions files, where you can set java startup options.
Anyway, there is no easy way to understand what happend. If this doesn't help, we need to install runtime profiler module on your server, run it and connect to the server with profiler to analyze it.
So, .58 worth to try.
