PI11467: RACE CONDITION DUE TO MULTIPLE REQUESTS UPON APPLICATION RETURNING TO THE FOREGROUND AFTER A SERVER RESTART

Download the cumulative interim fix for IBM Worklight V6.0.0 Fix Pack 2 and IBM Mobile Foundation v6.0.0 Fix Pack 2
Download the cumulative interim fix for IBM Worklight V5.0.6 Fix Pack 2 and IBM Mobile Foundation V5.0.6 Fix Pack 2
IBM Worklight Interim Fix README for 6.0.0.2

APAR status

• Closed as program error.

Error description

• A race condition takes place if a Worklight Server restart took
  place while the application was in the background, returned to
  the foreground and sent a request.
  This happens because when returning to the foreground a
  Worklight framework request is also being sent.
  Because the server was restarted and 2 requests are being sent,
  a race conditions happens.
  This causes loss of communication between the client and server.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * End users of a Worklight application who are getting endless *
  * "bad token" reponses from the server.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When a server sends the "bad token" message (which can       *
  * happen if, for example, you send out 2 messages, the server  *
  * responds to both of them, then before it gets the second     *
  * response , it restarts and then when your client responds    *
  * again, with the previous token, it (the server) does not     *
  * recognize it).                                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * -                                                            *
  ****************************************************************
  

Problem conclusion

• The code has been modified so that it now checks for a "bad
  token" failure and, if it receives one three times, it will call
  the request.onFailure method so that the user understands that
  there is an issue and the endless loop is broken.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WORKLIGHT CONSU

• Fixed component ID

  5725I4301

Applicable component levels

• R506 PSY

     UP

• R600 PSY

     UP