MobileFirst Runtime Scheduler Trouble shooting
Scheduler job of MobileFirst Runtime.
The scheduler job does the following tasks:</p>
- Marks the data for License Tracking and saves the data to license tracking related tables. For more information, see License tracking.
- Clean up
MFP_PERSISTENT_DATA. For more information, see Purge runtime tables.
JNDI properties for 1 and 2 are enabled by default for liberty. To enable the scheduler in WebSphere Application Server, set the value to true. If JNDI properties related to #1 or #2 is enabled, then the scheduler runs.
Mobile Foundation Platform scheduler runs by default between 1AM and 2AM. In the case of farm with multiple servers, the scheduler runs from all servers. The starting time of scheduler in each server is few random minutes apart. The scheduler runs 4 hours after a server restart. For example, if the servers start at 8PM today, the scheduler runs the following day 1 AM. But if the server was restarted at 11 PM today, the scheduler does not run the following day 1 AM as the gap is not 4 hours between server start and scheduler’s scheduled run time. In this case, the scheduler runs at 1 AM, the day after.
NOTE: Previous to ifix level 126.96.36.199-MFPF-IF201907091643, the gap between server start and scheduler run was 8 hours.
The scheduler start time can be configured using the JNDI property, mfp.scheduler.startHour, which takes values from 1 to 23 (Starting ifix level 188.8.131.52-MFPF-IF201907091643). With this property, the scheduler run can be set to any time of your preference instead of the default 1 AM. Using this property, you can can configure your scheduler to start at your light traffic hours and can also ensure that the scheduler runs despite the daily start of the server. If you restart your server every night at 1 AM, then you can set the value for
mfp.scheduler.startHour to 5. This ensures a 4 hours gap between server restart and the scheduler runs at 5 AM.
Keep the license tracking disabled as the license tracking activities are database intensive. Only if you use the Mobile Foundation addressable devices licensing model, you need to run license tracking.
If you have not enabled license tracking, then use the purge feature to do the following:
- Clean up the old records.
MFP_PERSISTENT_DATAand `MFP_TRANSIENT_DATA tables for better performances of Mobile Foundation Platform. (Feature available starting from ifix level 184.108.40.206-MFPF-IF201812191602-CDUpdate-04)
Combination of flags and impact on MobileFirst tables
|true||false||0 (default)||Deletes records older than days = sum of values of JNDI properties,
|Deletes records with
|true||true||0 (default)||Deletes records older than days = sum of JNDI properties,
|Deletes records with
|false||true||0 (default)||Records are not deleted||Delete records with
|false||false||0 (default)||No action||No action|
|true||false||>=90||Follows rules of License tracking: Deletes records older than days = sum of JNDI properties,
||Deletes records with
|false||true||>=90||Deletes records older than days specified by JNDI property
||Deletes records with expiresAt column value 5 days prior to current day.|
Messages in MFP logs to troubleshoot purge related issues
Default, when there are no messages or traces enabled, the following message is available in the logs:
Configure your apps to collect analytics on the Network device event. FWLSE0293I: License tracking will run at < date and time>
FWLSE0293I: License tracking will run at 'Wed Nov 11 01:23:00 IST 2020'.` This message is only one time, during server start.
The following messages are available in every day log at the time the scheduler starts and ends the license tracking or purge operation:
FWLSE0294I: Processing platform usage on <date and time>` and `FWLSE0295I: Processing platform usage ended at <date and time>`.
If the flags
mfp.purgedata.enabledis true and
mfp.purgeOldData.ageis non zero, then records from
MFP_PERSISTENT_DATAare deleted, base. Deletion happens in batches of 5000 records. This message shows the batch number and time taken to delete that batch:
FWLSE0291I: Completed deletion of <number> batches in <time elapsed> ms
In addition, there are further logging that can be enabled by setting the tracing option to