IBM Support

PI56634: NIL VALUE CAUSING CRASH IN OCLOGGER.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • OCLogger does not check for Nil values in header when sending
    OCLogger file, which may cause a MobileFirst Platform iOS to
    application crash.  When this crash occurs, a stack trace of
    the following form will be logged in the device log:
    
    thread #63: tid = 0xcfe4, 0x23292df0
    libobjc.A.dylib´objc_exception_throw, queue =
    'com.apple.root.default-qos', stop reason = breakpoint 1.1
      * frame #0: 0x23292df0 libobjc.A.dylib´objc_exception_throw
        frame #1: 0x23a0ae12
    CoreFoundation´-[__NSPlaceholderDictionary
    initWithObjects:forKeys:count:] + 342
        frame #2: 0x23a0ac96 CoreFoundation´+[NSDictionary
    dictionaryWithObjects:forKeys:count:] + 50
        frame #3: 0x00287c60 WorkExecution´+[OCLogger
    sendFileToServer:withDelegate:] + 408
        frame #4: 0x00288128 WorkExecution´+[OCLogger send] + 264
        frame #5: 0x00288bea WorkExecution´+[OCLogger
    processAutomaticTrigger] + 294
        frame #6: 0x001a1468 WorkExecution´__40-[LoggerPlugin
    processAutomaticTrigger:]_block_invoke + 112
        frame #7: 0x23665b5a
    libdispatch.dylib´_dispatch_call_block_and_release + 10
        frame #8: 0x23674920
    libdispatch.dylib´_dispatch_root_queue_drain + 1560
        frame #9: 0x23674304
    libdispatch.dylib´_dispatch_worker_thread3 + 96
        frame #10: 0x23823b28
    libsystem_pthread.dylib´_pthread_wqthread + 1024
        frame #11: 0x23823718
    libsystem_pthread.dylib´start_wqthread + 8
    

Local fix

  • As a workaround, disable all application logging, and disable
    sending of logs to MobileFirst Operational Analytics.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * This affects iOS developers that are wrapping their          *
    * application with third party wrappers.                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * After wrapping an iOS application null pointers exceptions   *
    * were occurring on the client when sending nil headers from   *
    * the Logger API to the server.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * -                                                            *
    ****************************************************************
    

Problem conclusion

  • Nil checks were placed on the headers to prevent the application
    crashing from nil errors.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI56634

  • Reported component name

    WL/MFPF ENTERPR

  • Reported component ID

    5725I4300

  • Reported release

    620

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-02-04

  • Closed date

    2016-02-24

  • Last modified date

    2016-02-24

  • 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

    WL/MFPF ENTERPR

  • Fixed component ID

    5725I4300

Applicable component levels

  • R620 PSY

       UP

  • 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":"620","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 October 2021