WebLogic Server Hang/Application Deadlock Support Pattern
(Doc ID 1264876.1)
Last updated on SEPTEMBER 25, 2020
Oracle WebLogic Server - Version 8.1 and later Information in this document applies to any platform.
***Checked for relevance on 24-Oct-2013***
An inadvertent deadlock in the application code can cause a server to hang. For example, a situation in which thread1 is waiting for resource1 and is holding a lock on resource2, while thread2 needs resource2 and is holding the lock on resource1. Neither thread can progress.
This article should be used if all the steps delineated in the Generic Server Hang Pattern (<note 1264286.1>) article failed to resolve the hang issue. Threads hung in application methods are indicators that the problem is specific to an application deadlock problem. Several thread dumps taken a few seconds apart could confirm that the threads are not progressing. Troubleshooting this problem will involve reviewing the application code.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!