• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

WAS 6.1 Thread management

 
Ranch Hand
Posts: 62
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Friends I am new to Websphere Application Server and not much experience with administering WAS.

I have a problem, my application is running on WAS properly but I have this problem at hand.

If a user runs a query which is very resource intensive, all the other users get impacted. Which seems pretty strange given that first supect here would be connection pool settings but that seems alright to me. Nonetheless even if other users are just opening some screens which does not have anything to do with database connections they are also affected and the application is virtually brougt to crawl.

Please advise.

If this is of any relevance, this J2EE application is running on struts2 and hibernate 3.2 frameworks.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic