I am working in JDev 220.127.116.11 and weblogic 10.3.4
when I deploy my Application in my production weblogic
after some time (it does not constant it is variable) I got warnning on the server
when I check the server I got some stuck thread
any idea or notes how can I know what is the reason of these stuck threads?
is there any objects have thread unsafe issue, resource contention or race condition in ADF?
When you open the wls console you should be able to dig down to the stack of threads. In there you look for the threads which are marked stuck.Analyze their stack traces to get a hint where in your app the problem starts. If you see a class from your app this would be a candidate for further investigation.
A long running operation, such as possibly the View object query execution in your code, could produce stuck threads. This is not necessarily a problem, it is mostly a piece of information provided by WebLogic indicating that your application logic executes some piece of code that takes longer than expected. In these cases WebLogic considers those threads running the specific application code as 'stuck'. There is a configuration option in WebLogic called Stuck Thread Max Time (in Servers > Configuration > Tuning) that allows you to configure the time (in seconds) after which a thread is considered 'stuck'. Setting this number to a higher setting will avoid considering some of the threads as 'stuck'.
Note that there is also the possibility to create separate work managers in WebLogic and execute (in most cases) your long running application logic in them. Take a look at this post for some additional information on this: http://jdeveloperfaq.blogspot.com/2011/05/faq-34-using-weblogic-work-managers-to.html