ICEpush
  1. ICEpush
  2. PUSH-276

Set missing browserID cookie while ice.push.createPushId is used

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.0.BETA
    • Fix Version/s: 4.0.BETA, 4.0
    • Component/s: None
    • Labels:
      None
    • Environment:
      supported browsers
    • Assignee Priority:
      P1

      Description

      Make sure the browserID is set first when ice.push.createPushId function is used and then create the pushID.
      1. localmongo.html
        3 kB
        Ted Goddard
      2. mongochat.html
        3 kB
        Ted Goddard

        Activity

        Hide
        Ted Goddard added a comment -

        Can you attach your .war file? I will deploy to labs for testing.

        Show
        Ted Goddard added a comment - Can you attach your .war file? I will deploy to labs for testing.
        Hide
        Mircea Toma added a comment -

        Attached pushservice.war that works as expected on my local deployment.

        Show
        Mircea Toma added a comment - Attached pushservice.war that works as expected on my local deployment.
        Hide
        Ted Goddard added a comment -

        It appears that this problem is transient – after restarting the server, I had good results with the browser I tested with, but then observed a storm of traffic for a connected mobile device. Please leave your server running locally over a period of time and test it periodically with a number of browsers while keeping an eye on the network activity. I will monitor the labs deployment to look for the problem again.

        Show
        Ted Goddard added a comment - It appears that this problem is transient – after restarting the server, I had good results with the browser I tested with, but then observed a storm of traffic for a connected mobile device. Please leave your server running locally over a period of time and test it periodically with a number of browsers while keeping an eye on the network activity. I will monitor the labs deployment to look for the problem again.
        Hide
        Ted Goddard added a comment -

        Restarting tomcat and clearing the work directory seems to temporarily fix the problem. So, this appears to be a transient state that either the push client or the server enters (but it is a very severe failure since it could exhaust either a mobile user's bandwidth cap or result in a high network use bill from amazon for us.)

        Show
        Ted Goddard added a comment - Restarting tomcat and clearing the work directory seems to temporarily fix the problem. So, this appears to be a transient state that either the push client or the server enters (but it is a very severe failure since it could exhaust either a mobile user's bandwidth cap or result in a high network use bill from amazon for us.)
        Hide
        Mircea Toma added a comment -

        The infinite loop issue cannot be reproduced any more, most probably it was caused by browser caching. We can open this issue again if the problem re-occurs.

        Show
        Mircea Toma added a comment - The infinite loop issue cannot be reproduced any more, most probably it was caused by browser caching. We can open this issue again if the problem re-occurs.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: