PM92881: CALLS TO WL.CLIENT.CONNECT() FAIL WHEN CONNECTONSTARTUP IS FALSE IN INITOPTIONS.JS

APAR status

• Closed as program error.

Error description

• When connectOnStartup = false in initOptions.js, there is a
  possible race condition
  when connecting to the server at a later point. Specifically,
  event transmission which takes place as a result
  of WL.Client.transmitEvent() or triggers being activated can
  result in a call to WL.Client.connect().
  This can result in application code that calls
  WL.Client.connect() failing until the previous call to connect
  completes.
  

Local fix

• Make an explicit call to WL.Client.connect() before calling
  WL.Client.transmitEvent() or WL.Device.startAcquisition().
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Developers building applications that make use of            *
  * WL.Client.transmitEvent() or triggers in location services.  *
  * The problem will not occur if connect is called before       *
  * WL.Client.transmitEvent() or WL.Device.startAcquisition()    *
  * are called.                                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * A call to WL.Client.connect() fails, and the error message   *
  * "Cannot invoke WL.Client.connect while it is already         *
  * executing." is logged.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In the device logs there will be debug entries: "Client is
  disconnected,connecting..." and "Client is connected,trying to
  transmit...".
  The logs will also contain the error message:  "Cannot invoke
  WL.Client.connect while it is already executing."
  

Problem conclusion

• The code has been modified so that the event transmission
  mechanism will only transmit events when already connected. It
  is still possible to transmit events before calling
  WL.Client.connect() but they will not be transmitted until after
  it has successfully completed.
  
  The fix for this APAR is currently targeted for inclusion in
  fixpack 6.0.0.1.
  A fix is available in 6.0.0.0-IF201307011413 and later.
  

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

• R600 PSY

     UP