Weblogic Threads Stuck when Provisioning Exchange Connector Concurrently
(Doc ID 1379547.1)
Last updated on FEBRUARY 11, 2020
Applies to:Identity Manager Connector - Version 220.127.116.11 to 18.104.22.168 [Release 10gR3]
Information in this document applies to any platform.
**Checked For Relevance on 21-Jun-2013**
When provisioning to Exchange Connector concurrently, OIM server deployed on top of Weblogic did not receive response from Remote Manager within 5 minutes.
In the Weblogic server log, it reported many provisioning threads stuck more than 5 minutes.
<Nov 11, 2011 11:12:33 AM GMT-03:00> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: <TID> for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "826" seconds working on the request "weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl@<ID>", which is more than the configured time (StuckThreadMaxTime) of "720" seconds. Stack trace:
Thread-<TID> "[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON>
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