• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 460
  • Last Modified:

Websphere Application Server lags with multiple connections

Hello experts

I have an application running in Websphere 6.0, Linux SUSE Enterprise 9 SP2 (server A) that makes db2 queries to another server (server B). During the development stage, everything seemed to be working just fine. The problem came when doing traffic tests: when creating between 80-100 concurrent http requests to the WAS app, the application just stops answering, where:

- CPU consumption in server A is less than 20% when doing volume tests (we have a good server)
- Memory still available during volume tests (around 50% from total used)
- When reaching around 80-100 http requests, the application server lags, even trying to enter the administrative console is greatly slowed down, I need to restart the whole WAS from the terminal re-establish it. Looks as if threads don't want to be resolved when the queue reaches certain volume of requests.
- All other applications installed in the Application Server are affected, even if the others aren't doing anything at all.
- There are no errors detected in the SystemErr.log
- "Server B" is not the problem (there are many other servers consulting db2 to that server without any problem.
- No network issues
- Websphere Application Server has base configuration (as installed)

My first assumption is that there is a parameter in the WAS configuration that I need to change (number of threads? max memory consumption for WAS threads? Max Clients?) but I'm a newbie with WAS (used to work with Tomcat). Resources like memory (currently 3GB) and CPU can be added without problem

Any suggestions are greatly appreciated
0
Arrismog
Asked:
Arrismog
  • 3
  • 3
1 Solution
 
HonorGodCommented:
It sounds like you have exceeded the number of concurrent connections.

Take a look here: http://bit.ly/gJ9IUz
especially the part about "Maximum Connections"

How many do you currently have allowed?
0
 
ArrismogAuthor Commented:
Hello

Checking the value for Maximum Connections, they are currently set to 10:

Connection timeout -- 180 seconds
Maximum connections -- 10 connections
Minimum connections -- 1 connections
Reap time -- 180 seconds
Unused timeout -- 1800 seconds
Aged timeout -- 0 seconds

Is Maximum connections too low? there's an estimate to have hundreds of requests per minute to this application.

0
 
HonorGodCommented:
Maximum connections defines the absolute maximum number of concurrent connections that are allowed to that database.  If your applications need more than 10 concurrent connections, I would increase this value accordingly.

So, to answer your question:

> Is Maximum connections too low?

Yes, it appears so.
0
KuppingerCole Reviews AlgoSec in Executive Report

Leading analyst firm, KuppingerCole reviews AlgoSec's Security Policy Management Solution, and the security challenges faced by companies today in their Executive View report.

 
ArrismogAuthor Commented:
Sorry answering till now, we were in functionality and stress phase with the app.

Yep, increasing the maximum connections according to the link you provided, it now supports a lot (LOT) more connections without any problem

Sir, you made my day :)
0
 
ArrismogAuthor Commented:
Yep, increasing the maximum connections according to the link you provided, it now supports a lot (LOT) more connections without any problem

Sir, you made my day :)
0
 
HonorGodCommented:
Super!  I'm glad that I was able to be of some assistance.

Thanks for the grade & points.

Good luck & have a great day.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The Lifecycle Approach to Managing Security Policy

Managing application connectivity and security policies can be achieved more effectively when following a framework that automates repeatable processes and ensures that the right activities are performed in the right order.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now