Syncing suddenly very slow

Question

I have a problem with really slow syncing the last days. Some users with a lot of data (typically 8-10 2mpix jpegs) to upload are not able to sync at all. Users doing a complete refresh has the same problem. Syncs with "normal" amounts of data get through, but it takes up to 20 minutes. Clients are running WM5 and WM6.x.
This exception shows in the Mobile server console:
SEVERE: OC4J cannot update access log: null
java.lang.NullPointerException
at com.evermind.server.http.StandardRequestLogger.appendIP(StandardRequestLogger.java:168)
at com.evermind.server.http.StandardRequestLogger.log(StandardRequestLogger.java:59)
at com.evermind.server.http.FormattedRequestLogger.log(FormattedRequestLogger.java:330)
The err.log has a lot of entries that says that users forcibly ends syncs, which I know is true due to the hang they experience.
This shows up quite regularly in err.log
java.io.IOException: Timed out waiting for spool space
There are lots of free disk space on the server running Mobile server (Win 2003 server), virtually no CPU load and no database capacity problems as far as I can see.
Does anybody know where to start digging?
EDIT: The "OC4J cannot update access log" is described in Metalink, docid 392995.1. There is a patch for it. It doesn't seem to be related to my problem with slow syncing.
Marius
Edited by: Marius H on Aug 28, 2009 12:31 AM

Answer 1

In the SYNC section of the polite.txt file.
E.3.2.6 RESUME_CLIENT_TIMEOUT
The RESUME_CLIENT_TIMEOUT parameter is the number of seconds that the client should use to timeout network operations. The default is 60 seconds.
Set the total number of seconds that the client should use to resume network timeout operations.
Default Value
60 seconds
Example
RESUME_CLIENT_TIMEOUT=120
E.3.2.7 RESUME_CLIENT_MAXSEND
The RESUME_CLIENT_MAXSEND parameter is the maximum data size, in KB, that the client should send in a single POST request. This is used in cases where there is a proxy with a small limit on the data size in one request. Specifying a reasonable value, such as 256 KB, can also help clients with limited storage space, as they can free the chunks that have already been transmitted and acknowledged. The default is 1024 KB.
Set the maximum data size in KiloBytes sent by a client in a single POST request. Some proxies maintain fixed limits on data size in one request.
Default Value
1024