Agile Managed Servers Goes to Warning State, Having Stuck Thread at com.agile.cs.query.QuerySessionBean
(Doc ID 2919154.1)
Last updated on JANUARY 24, 2024
Applies to:
Oracle Agile PLM Framework - Version 9.3.5.0 and laterInformation in this document applies to any platform.
Symptoms
Actual Behavior
Managed servers going into the warning state with the below stuck threads, and users are not able to login to Agile because the performance is extremely slow.
Below stuck thread can be seen from the thread dump:
com.agile.cs.query.QuerySessionBean.executeQuery
The issue happens intermittently, but happens frequently.
After restarting the managed server nodes, status will change to RUNNING, however after running for a while it gets to WARNING status again.
Expected Behavior
Managed servers to run in RUNNING state without the needs of restarting managed server nodes, and user can login to Agile without performance issue.
Steps
- Notice that users are not able to login to Agile from Web Client/Java Client. The login performance is extremely slow and no response.
- Login to WebLogic admin console as superadmin user http://{admin_server_name}.{domain_name}:{port}/console
- From the Domain Structure, go to agileDomain > Environment > Servers, and see the managed servers are in WARNING state.
- Take thread dump from the managed server node by following Doc ID 1294958.1, and see stuck threads are being generated.
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 |