PI35761: IN A CUSTOMER APP, APP OCCASIONALLY CRASHES DUE TO ILLEGALSTATEEXCEPTION: TIMER WAS CLOSED.

IBM MobileFirst Platform Foundation Interim Fix README for 7.0
IBM MobileFirst Platform Foundation Interim Fix README for 6.3
IBM Worklight Interim Fix README for 6.2.0.1

APAR status

• Closed as program error.

Error description

• The following stacktrace has been reported 3 times via Android
  Crash Reports:
  
  java.lang.IllegalStateException: Timer was canceled
  
  at java.util.Timer.scheduleImpl(Timer.java:561)
  
  at java.util.Timer.schedule(Timer.java:459)
  
  at
  com.worklight.common.Logger.processAutomaticTrigger(SourceFile:1
  368)
  at
  com.worklight.androidgap.plugin.LoggerPlugin$1.run(SourceFile:10
  5)
  at
  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
  utor.
  java:1080)
  
  at java.util.concurrent.ThreadPoolExecutor$Worker.run
  
  (ThreadPoolExecutor.java:573)
  
  at java.lang.Thread.run(Thread.java:838)
  
  This occurs on sign-on.
  
  The issue is present on two versions of Android and 3 different
  devices.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * This is a concurrency issue, so any user with a native       *
  * Android, or hybrid Android project is susceptible to this    *
  * bug.                                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The client-side API has the ability to automatically send    *
  * logs to the Worklight server.  There is a concurrency bug    *
  * which at times can cause the Timer object to be in an        *
  * illegal state, causing an IllegalStateException.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * -                                                            *
  ****************************************************************
  

Problem conclusion

• The critical section was synchronized so that no concurrent
  modification takes place, ensuring the validity of the Timer
  object.
  

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

  WL/MFPF CONSUME

• Fixed component ID

  5725I4301

Applicable component levels

• R620 PSY

     UP

• R630 PSY

     UP

• R700 PSY

     UP