Batch Logs Are Consuming Too Much Space Due To Debug Statement 'Inside Invoke Of TransitionActiv...'
(Doc ID 2625989.1)
Last updated on MAY 31, 2024
Applies to:
Oracle Utilities Mobile Workforce Management - Version 2.3.0.2.0 to 2.3.0.3.0 [Release 2.3]Oracle Real-Time Scheduler - Version 2.3.0.2.0 to 2.3.0.3.0 [Release 2.3]
Information in this document applies to any platform.
Symptoms
We have been having space issues with our MWM batch issues due to the logs filling up. Over 7 million debug statements on MWM batch.
We could save space by not having the following log messages.
11:48:38,870 [DEFAULTWorker:1] INFO
(com.splwg.mwm.domain.serviceManagement.task.ActivityAssignmentResolutionAlg
Comp_Impl) In invoke of ActivityAssignmentResolutionComp_Impl
. . .
11:48:39,663 [DEFAULTWorker:1] INFO
(com.splwg.mwm.domain.serviceManagement.task.TransitionActivityIfAssignmentC
ompletedAlgComp_Impl) Inside invoke of
TransitionActivityIfAssignmentCompletedAlgComp_Impl
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |