My Oracle Support Banner

How To Remove SMAuto Messages From TPW Logs and Confirm Native SMAuto Logging in v2 (Doc ID 1667700.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Utilities Mobile Workforce Management - Version 2.0 to 2.1.0 [Release 2.0 to 2.1]
Oracle Real-Time Scheduler - Version 2.1.0 to 2.1.0 [Release 2.1]
Information in this document applies to any platform.

Goal

**Examples provided in this article do not represent real life personal/confidential information. Please use proper values to your businees.**
**Disclaimer:** This KM article may include the following abbreviations:

MWM - Oracle Utilities Mobile Workforce Management
ORTS/ORS/ERTS - Oracle Real-Time Scheduler
TPW - Threadpoolworker

By default, the native SMAuto (Scheduler) logs are included within the threadpoolworker (TPW) logs.  This slightly increases the memory load on these processes and in certain cases has been linked to TPW crashes with memory dumps noted by 'java/lang/OutOfMemoryError'.

Further, the echoed SMAuto logs are not always complete enough for a problem investigation.  For example, if SMAuto crashes, the final lines of SMAuto processing will not be captured in the TPW log file.  Therefore, it is recommended to confirm that native SMAuto logs are created and to remove the SMAuto entries from the TPW log.  This can be accomplished with the steps below.
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.