IBM Support

PI51654: LOGGING CONFIG SET IN SERVER LOGGING PROFILE MAY BE UNSET VIA JAVASCRIPT PIGGYBACKERS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a MobileFirst Platform application makes a network request
    using WL.Client.connect or WLResourceRequest, the action of a
    JavaScript piggybacker may unset the logging configuration that
    was set in a client logging profile on the MobileFirst Platform
    Server.  When this occurs, the client logging level used by a
    MobileFirst Platform application may be reset to an unintended
    value.
    

Local fix

  • As a workaround, the customer may execute the following code in
    their MobileFirst Platform application:
    
    WL.webLogger._processUpdateConfig = function() {};
    
    And, additionally, call the API function
    "WL.Logger.updateConfigFromServer()" frequently in the
    application.
    
    The "WL.webLogger._processUpdateConfig" field is undocumented,
    and may change or be removed in any future version or iFix of
    MobileFirst Platform Foundation without notice, and therefore
    should be used only as a temporary workaround until the
    permanent fix can be applied.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Application end users are not affected.  Application         *
    * infrastructure managers may see unexpected log verbosity     *
    * from client applications.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * A logic error in the Worklight/MobileFirst hybrid JavaScript *
    * code will always remove any previously set log profile that  *
    * was set by an administrator from the Worklight/MobileFirst   *
    * log profiles tab.                                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * A simple workaround is to disable the processing of the      *
    * non-existent log profile in the client Worklight/MobileFirst *
    * JavaScript library in your hybrid apps (but not web          *
    * applications) by placing the following line in your          *
    * wlCommonInit() function implementation:                      *
    *                                                              *
    * WL.WebLogger._processUpdateConfig = function() {};  // a     *
    * no-op                                                        *
    ****************************************************************
    

Problem conclusion

  • The logic error is corrected such that we only process log
    profiles that are explicitly sent or removed according to the
    server instructions.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI51654

  • Reported component name

    MFPF/WORKLIGHT

  • Reported component ID

    5725I4301

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-10-30

  • Closed date

    2016-02-11

  • Last modified date

    2016-02-11

  • 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

    MFPF/WORKLIGHT

  • Fixed component ID

    5725I4301

Applicable component levels

  • R630 PSY

       UP

  • R700 PSY

       UP

  • R710 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSZH4A","label":"IBM Worklight"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"700","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
14 October 2021