-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jasdeep,

jasdeep wrote:
>  2. Configuring Jboss's Internal Container Level Connection pooling  simply
> creating the datasources

This is the right way to do things.

> The application works OK with Second method but When it is being hit with 
> 200 request/second The pool gets [exhausted].

200 requests per second is a /lot/ of traffic (8 million requests per
month, if that load is sustained). Is this a peak load, or a steady load?

Does your pool become permanently exhausted? Or, do you have some users
who get exceptions (cannot get connection after timeout) and others who
get through. If the load drops off, is your pool still exhausted? If
that's the case, then you have a connection leak in your application.

With heavy load, usually individual requests fail, but the server is
still healthy. You might run out of memory, but you can avoid that by
configuring your server to accept only a certain number of requests and
refusing the rest.

How long is your connection pool timeout (the amount of time a thread
will wait for a connection before giving up). Perhaps you have to
increase that timeout. You could also increase the number of connections
in your pool. How many do you have in there, now?

The last option is to buy more hardware. If you really are getting 200
requests/sec, then you probably need some more hardware for your
application.

> i am unable to decide which approach i should be using  as my application
> can receive large no. of requests around 1000/sec ?

Geez... I hope that's /peak/ load. Do you have to handle 1000
requests/sec or 1000 simultaneous users?

- -chris

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGUv4G9CaO5/Lv0PARAvZNAJ9+S6+Oyl5cEyFoxkgCmijHkJBJXgCgrzhP
lSigTUYwfyzbIkiEfBLT3Qw=
=ncCh
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to