[horde] Best timing settings for Horde ActiveSync

[Patrick De Zordo]

> Most likely, the process that was checking for changes during the heartbeat
> interval was terminated.
>
> Simplified, the way an ActiveSync SYNC (or PING) works, is that the folders
> that are synchronized to the device are checked for changes.
> If nothing has changed and less than the heartbeat interval has elapsed 
> since
> receiving the SYNC, the process sleeps for
> $conf[activesync][ping][waitinterval] seconds (in your case, 15
> seconds) and checks again. This repeats until a change is detected or the
> heartbeat interval elapses. Only then a response to the SYNC is sent to
> device. If the process is killed before the reply is sent, devices will not 
> know
> about that until the heartbeat interval elapses and will remain oblivious
> about any changes.
>
> Since another device seems to work correctly with a shorter heartbeat
> interval, chances are that something in your PHP and/or Apache
> configuration is killing the process before the heartbeat interval ends. A
> quick-and-dirty way to see if this might be the problem, would be to reduce
> both $conf[activesync][ping][heartbeatmax] and
> $conf[activesync][ping][heartbeatdefault] to 480 seconds (470 seconds
> seems to work on your Android device). If after that the problem no longer
> occurs, you need to look into your Apache and/or PHP configuration if
> something is killing long running processes.

I have tested with shorter heartbeat-values, 470/480sec and the issue seems to 
be related to a timeout like you suspected.
Now, how to setup a higher timeout in apache which is suitable for this 
environment?

Thank you!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6229 bytes
Desc: not available
URL: <http://lists.horde.org/archives/horde/attachments/20150117/a54aae4c/attachment.bin>