It’s more like In-ActiveSync!

6 thoughts on “It’s more like In-ActiveSync!

  1. Hi Jon,
    thank you for the detailed description.
    I have trouble with some iPhones, sometimes they stop receiving mail in native mailapp.
    I’m using SEG V2 vers. 2.9
    Do you know how to configure the timout-values in SEG V2?

    Like

    1. Do you have your idle session timeouts configured properly from client to server?

      The idea is that your first hop needs to have a 30m timeout and grows in (e.g. Load balancer would have a 30m timeout, SEG would be 35m, firewall would be 40m, F5 45m, Exchange Server 50m etc). One of the biggest issues you run into is if something besides exchange closes the long-lived connection it may result in server issues e.g. email resync, 500 errors, etc

      Like

      1. Thanks for your reply!

        Exchange-Server has standard-configuration in web.config:
        “MinHeartbeatInterval” value=”60″
        “MaxHeartbeatInterval” value=”3540″
        “HeartbeatSampleSize” value=”200″
        “HeartbeatAlertThreshold” value=”540″

        We’re using Kemp-LB with 2100 sec. session-timeout and “least connection”.

        But we can’t change the session timeout of SEG V2 – it seems it can be configured in config.json-file:

        “emailServerConfig” : {
        “serverHostAndPort” : “https://activesync.domain.com:443”,
        “serverTimeoutInMillis” : 1200000,
        “serverConnectionPoolSize” : 25000,
        “ignoreSslErrorsWithExch” : false,
        “emailType” : “EXCHANGE”

        I tried to set the timeout-value to “2700000” – but any changes in this file will be overwritten by the SEG-Service.

        I see in SEG app.log the entry below and on Exchange-Serverlog a lot of “NMstolen” and 1040 Event-Logs (ActiveSync push-Warnings)

        2019-01-21 16:23:14.652 ERROR (vert.x-eventloop-thread-0) [c.a.s.h.EmailResponseHelper] – Error serving email request for device [DeviceId=very-long-Devide-ID,DeviceType=iPhone,User=unername@domain.com,TransactionId=efe4f4c4-d6b1-4c56-98aa-955f654f8e8e,Cmd=Ping,MailClient=Apple-iPhone9C3/1603.101] URI /Microsoft-Server-ActiveSync?User=unername@domain.com&DeviceId=very-long-Devide-ID&DeviceType=iPhone&Cmd=Ping, query User=unername@domain.com&DeviceId=very-long-Devide-ID&DeviceType=iPhone&Cmd=Ping, method POST
        java.util.concurrent.TimeoutException: The timeout period of 1200000ms has been exceeded while executing POST /Microsoft-Server-ActiveSync?User=unername%40domain.com&DeviceId=very-long-Devide-ID&DeviceType=iPhone&Cmd=Ping for host activesync.domain.com
        at io.vertx.core.http.impl.HttpClientRequestBase.timeout(HttpClientRequestBase.java:183)
        at io.vertx.core.http.impl.HttpClientRequestBase.handleTimeout(HttpClientRequestBase.java:168)
        at io.vertx.core.http.impl.HttpClientRequestBase.lambda$setTimeout$0(HttpClientRequestBase.java:126)
        at io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:870)
        at io.vertx.core.impl.VertxImpl$InternalTimerHandler.handle(VertxImpl.java:829)
        at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:344)
        at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
        at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:403)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:463)
        at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
        at java.lang.Thread.run(Unknown Source)
        2019-01-21 16:23:14.652 ERROR (vert.x-eventloop-thread-0) [c.a.s.h.EmailResponseHelper] – Response to device is (status code 400, status message The timeout period of 1200000ms has been exceeded while executing POST /Microsoft-Server-ActiveSync?User=unername%40domain.com&DeviceId=very-long-Devide-ID&DeviceType=iPhone&Cmd=Ping for host activesync.domain.com). Device [DeviceId=very-long-Devide-ID,DeviceType=iPhone,User=unername@domain.com,TransactionId=efe4f4c4-d6b1-4c56-98aa-955f654f8e8e,Cmd=Ping,MailClient=Apple-iPhone9C3/1603.101]
        2019-01-21 16:23:14.652 ERROR (vert.x-eventloop-thread-0) [c.a.s.u.HeadersLogger] – efe4f4c4-d6b1-4c56-98aa-955f654f8e8e – DEVICE_REQUEST headers::
        Host : seg1.domain.com
        MS-ASProtocolVersion : 16.1
        Accept-Encoding : br, gzip, deflate
        Cookie : X-BackEndCookie=”S-1-5-21-169686320-456479945-464344438-92648=u56Lnp2ejJqBysjJzMnMysnSmczGy9LLzMmb0s -> header actual length : 151
        Connection : keep-alive
        Accept : */*
        User-Agent : Apple-iPhone9C3/1603.101
        Content-Length : 0
        Accept-Language : en-us
        X-MS-PolicyKey : 2491819913

        Liked by 1 person

    1. Are you running a cluster? That might be why that setting is being overwritten.

      Have you opened a a ticket with their support team to see what the supported way of increasing the serverTimeoutInMillis? I’m emailing their PM now.

      Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s