ICEpush
  1. ICEpush
  2. PUSH-375

heartbeat updates returning as closed/duplicate after navigation

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: EE-3.3.0.GA_P03
    • Fix Version/s: EE-3.3.0.GA_P04
    • Component/s: Push Library
    • Labels:
      None
    • Environment:
      ICEpush EE
    • Assignee Priority:
      P1
    • Support Case References:
    • Workaround Exists:
      Yes
    • Workaround Description:
      Hide
      Set the com.icesoft.icepush.maxHeartbeatInterval so that it does not go over 20 seconds:
          <context-param>
              <param-name>com.icesoft.icepush.maxHeartbeatInterval</param-name>
              <param-value>15000</param-value>
          </context-param>
      Show
      Set the com.icesoft.icepush.maxHeartbeatInterval so that it does not go over 20 seconds:     <context-param>         <param-name>com.icesoft.icepush.maxHeartbeatInterval</param-name>         <param-value>15000</param-value>     </context-param>

      Description

      When the adaptive heartbeat goes over 20 seconds and application navigation occurs, the next heartbeat updates return with:
      X-connection-reason: duplicate
      X-connection: closed

      This is causing the connection to fail. After 3 retries if the connection is not reestablished the NCI pop is shown.

      This seems to only happen once the heartbeat interval is over 20 seconds. If the navigation happens before it gets to 20 seconds, the duplicate updates are not seen.

        Activity

          People

          • Assignee:
            Mircea Toma
            Reporter:
            Arran Mccullough
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: