i have a problem with weblogic execute queue. i have one weblogic (multiple users).there are requests coming from all the users. some how if one request is stuck in execute queue. all subsequent threads also struck and it leads to the whole application freezes. here i need to bounce the weblogic.
can some one help me how i can overcome this scenario.
What typically happens is that a thread pool is maintained by the server and a thread is assigned from the pool to service each request. So, there is normally no problem unless the number of requests is so great that the server has to block requests.
In my weblogic (eg:Server A), my servlet handles multile requests some of them will be processed locally and some requests require information from another servers(eg:Server B).
As we know all requests should go through execute queue of server A. In my case all the requests to Server B are struck(some problem in server B). due to that all my threads are struck in execute queue of Server A. even the requests, which need to be processed locally also struck due to there are no execute threads available.
the best way I have found on solving thread stuck problems is taking a thread dump on the server. My suggestion is, when the threads are stucked take a thread dump and study it, then you'll be able to see exactly where the threads are stucked. usually some failing resource or bad coding.