Results 1 to 6 of 6

Hybrid View

  1. #1
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    1,091
    I see; the simple recovery mechanism offered by the ls_proxy layer is too simple for this case.
    This means that you cannot take advantage of the internal reconnection loop that follows when you set connectionRetryTimeoutMillis to a nonzero value.
    By setting connectionRetryTimeoutMillis to 0, your code will receive a onFailedReconnection invocation on the PushErrorListener, with a suitable PushException. Then, by invoking rethrow() on this exception, you will get the original PushUserException with the relevant error code, based on which you should setup the proper recovery action.
    Sorry for the hassle.

  2. #2
    No problem, thanks for your help.

 

 

Similar Threads

  1. Updates lost (never reach the client)
    By Fabrizio Patrício in forum Client SDKs
    Replies: 2
    Last Post: January 15th, 2015, 11:05 AM
  2. Replies: 6
    Last Post: March 19th, 2013, 04:55 PM
  3. notifySessionClose sometimes not being called
    By lstest in forum Adapter SDKs
    Replies: 2
    Last Post: February 24th, 2010, 11:09 AM
  4. Replies: 5
    Last Post: August 20th, 2009, 10:38 AM
  5. Waiting for... and never connecting
    By wmolde in forum Client SDKs
    Replies: 1
    Last Post: April 20th, 2007, 05:18 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
All times are GMT +1. The time now is 11:28 AM.