Question & Answer
Question
In the System Properties application, there is a property named mxe.mbocount. By default, its property value is 1 (for yes).
Cause
Documentation
Answer
The mxe.mbocount property can generate critical debug information for troubleshooting performance, stability, and runtime issues.
In Maximo, the mxe.mbocount property can be found and modified in the System Properties application. The default value for this property is 1.
When enabled, this property generates output from the JVM once per minute showing:
- Maximo Business Objects (MBOs) loaded
- Total users
- Users connected to each JVM in the system
- Cron Tasks Running on JVMs
- Total memory allocated and memory available
MBOs are objects related to the processing of various procedures executed on the server. They are somewhat analogous to rows in a database or spreadsheet. Each process may require objects loaded into one or more sets to search or manipulate the data. Each row of MBO results shows the MBO name, the number of sets, and the total number of MBOs across all sets.
Typical output to the logs might look as follows:
[4/6/16 8:54:15:465 EDT] 000000cb SystemOut O 06 Apr 2016 08:54:15:465 [INFO] [MAXIMO] [] REPFACAUTH: mbosets (4), mbos (4)
[4/6/16 8:54:15:465 EDT] 000000cb SystemOut O 06 Apr 2016 08:54:15:465 [INFO] [MAXIMO] [] REPORTRUNLOCK: mbosets (7), mbos (8)
[4/6/16 8:54:15:465 EDT] 000000cb SystemOut O 06 Apr 2016 08:54:15:465 [INFO] [MAXIMO] [] REPORTRUNQUEUE: mbosets (8), mbos (8)
[4/6/16 8:54:15:465 EDT] 000000cb SystemOut O 06 Apr 2016 08:54:15:465 [INFO] [MAXIMO] [] SITEAUTH: mbosets (4), mbos (4)
[4/6/16 8:54:15:465 EDT] 000000cb SystemOut O 06 Apr 2016 08:54:15:465 [INFO] [MAXIMO] [] SYNONYMDOMAIN: mbosets (2), mbos (4)
[4/6/16 8:54:15:465 EDT] 000000cb SystemOut O 06 Apr 2016 08:54:15:465 [INFO] [MAXIMO] [] TASKSCHEDULER: mbosets (23), mbos (45)
[4/6/16 8:54:15:465 EDT] 000000cb SystemOut O 06 Apr 2016 08:54:15:465 [INFO] [MAXIMO] [] BMXAA6372I - Host name: 6.42.145.227. Server name: MAXIMO. Cron task name: AssetTopoCacheCron.AssetTopoCacheCron01. Last run: 2016-04-06 08:52:16.0
[4/6/16 8:54:15:465 EDT] 000000cb SystemOut O 06 Apr 2016 08:54:15:465 [INFO] [MAXIMO] [] BMXAA6372I - Host name: 6.42.145.227. Server name: MAXIMO. Cron task name: AsyncImmediateJobCron.AsyncImmediate. Last run: 2016-04-06 08:54:07.0
[4/6/16 8:54:15:465 EDT] 000000cb SystemOut O 06 Apr 2016 08:54:15:465 [INFO] [MAXIMO] [] BMXAA6372I - Host name: 6.42.145.227. Server name: MAXIMO. Cron task name: AsyncJobCleanupCron.AsyncJobCleanup. Last run: 2016-04-06 05:00:13.0
IBM has internal tools that can correlate and trend this information combined with the output of the mxe.db.fetchResultLogLimit property and the mxe.db.logSQLTimeLimit to determine many causes of performance, stability, and runtime problems. Since this runs every minute, IBM can gather an understanding of the health of the JVM over a period of time. Often IBM will request up to 24 hours of logs to determine trends in user loads, memory requirements and many other points of interest.
This property should be left running at all times, since a problem can often not be foreseen or replicated. In order to troubleshoot or find root cause of many issues, the data from this property is required.
For more information on debug properties see the document Using debug properties to monitor and troubleshoot performance
Related Information
Was this topic helpful?
Document Information
Modified date:
02 July 2018
UID
swg21425963