Win a copy of Head First Android this week in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Rob Spoor
  • Devaka Cooray
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • Tim Holloway
Bartenders:
  • Jj Roberts
  • Al Hobbs
  • Piet Souris

Thread struck in execute queue

 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi,

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.

Thanks.
 
Ranch Hand
Posts: 1683
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.

What kind of processing are you doing?
 
sudhakar papireddy
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
H Thanks for your reply.

Issue is :

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.


Thanks
-------
 
Roger Chung-Wee
Ranch Hand
Posts: 1683
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You need to resolve the problem with server B. What does server B do?
 
Ranch Hand
Posts: 977
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

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.

regards.
 
sudhakar papireddy
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,
Thanks for your information.

currently we are planning to use two execute queue to resolve this issue to some extent.
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic