Recently our TrackStudio has been getting slower and slower to the point that it is almost unusable. Browsing tasks is fine. The problem is when posting changes.
When we post messages through the SOAP server we often get "The handle is in the wrong state for the requested operation" message which indicates a timeout.
When we post a change through the web interface we often get a similar result. The post itself has usually happened, although when a new task is created it is sometimes two identical tasks are created.
I monitored the server whilst creating a new task.
- The operation took 1min 40s seconds before timing out ("Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.").
- JettyService.exe was taking typically 18% processor time, with no other application taking significant time
- Hard disk access varied between 5 and 11 MB/s (It seems that disk access was the limiting process)
- Memory usage was constant at about 4.7GB
The server spec is
- Windows Server 2007, 64 bit
- 8GB RAM
- 3.6GB Dual Core processor
- SQL Server Express 2008 R2
- 3/4 of hard disk is empty
- The database contains about 3,000 tasks and 20,000 messages.
Help, please!