Agile Thread Pool Has Stuck Threads on Agile 9.3.2 Where MCAD Connector 3.3 Is Running (Doc ID 1679058.1)

Last updated on OCTOBER 04, 2015

Applies to:

Oracle Agile PLM MCAD Connector - Version 3.3 and later
Oracle Agile PLM Framework - Version to [Release 9.3]
Information in this document applies to any platform.


Agile thread pool has stuck threads cause 90% CPU utilization in Agile Application Server, and affects Agile Application Server performance on the environment where MCAD connector is running.
Agile version is 9.3.2 and MCAD connector version is 3.3.

Below stack trace can be captured from thread dump obtained by Acollect log:

Thread "[STUCK] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'" (id = 455) RUNNABLE
CPU Time: 31265430000000 nanoseconds User Time: 31249810000000 nanoseconds
Number of times blocked: 66350
Number of times waited: 63363
Object monitors locked: none
Ownable synchronizers locked: none
Stack Trace:


1. Create a Design with a linked Item
2. Assign a new Change to the Item making the Item rev 'A'
3. Assign another Change to the Item with the same revision 'A'
4. Save into Agile
5. Step #3 should trigger the code that checks for the next possible revision as 'A' is already used
6. Repeat the steps #3 and #4 multiple time to create more stuck threads to see a significant increase of the permanent CPU load


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 hundreds of Community platforms