"[deadlocked thread] [ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" - OTM Went Down Due DB Locks
Last updated on MARCH 08, 2017
Applies to:Oracle Transportation Management - Version 6.2.0 to 6.2.9 [Release 6.2]
Information in this document applies to any platform.
Application server crashed due to some DB dead lock identified by app server and after that there was no processing happening in OTM.
The unavaliability of OTM UI was resolved by bounce.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms