PI11502: EVENT LISTENERS ATTACHED WHEN CONNECT() IS INVOKED BUT NEVER UNBOUND.

Download for IBM Worklight V6.1.0 Fix Pack 1
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

• Every time connect() is called, event listeners are attached,
  but there is no time when they are unbound.  This build up of
  listeners leads to a huge amount of requests from a single
  client.
  

Local fix

• The following code work around was suggested:
  
  In:
   function doConnect(success, failure, timeout){
   WL.Client.connect({
  
  Add:
   function doConnect(success, failure, timeout){
   WLJSX.unbind(document, 'foreground');
   WL.Client.connect({
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Developers and administrators that have applications which   *
  * check for Direct Update and/or Remote Disable.               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Whenever an application does a .connect() to the Worklight   *
  * Server, a "foreground" event listener is attached. This      *
  * event listener, however, is not unbinded, resulting in an    *
  * increasing amount of event listeners. The end-result is an   *
  * increasing amount of composite requests sent to the          *
  * Worklight Server with every return to the foreground. The    *
  * composite request is the one that checks for Direct Update   *
  * and Remote Disable upon returning to the foreground. This    *
  * can cause what may seem and interpreted by some as a Denial  *
  * of Service "attack" on a server.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * The application should be re-built in Worklight Studio or    *
  * with the Worklight Ant tasks after the fix is applied.       *
  ****************************************************************
  

Problem conclusion

• The framework was corrected so that the foreground event
  listener is unbound before another is attached.
  
  The fix for this APAR is currently targeted for fixpack 6.1.0.1.
  

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 ENTER

• Fixed component ID

  5725I4300

Applicable component levels

• R506 PSY

     UP

• R600 PSY

     UP

• R610 PSY

     UP