We have deployed an Enterprise application 4 application servers which are pointed to single Database Schema, load will be distributed on these application servers through netscalar.
Here problem is in Database statistics are showing too many inactive sessions around 1450 ( 1500 Max session limit set), once it reached to maximum limit DB not allowing to login/open a new session.
1. how to optimize JDBC configurations to reduce no of inactive sessions?
2. what all needs to be considered while configuring Datasources (JDBC connection pooling)?
3. what is the criteria to define each parameter?
Our application using both Datasource and Datasource(vesrion 4) JNDI names for connection pooling.
Regarding Out Of Memory (OOM), we have raised n PMRs and had analyzed heap and thread dumps done optimization at application level as IBM said application creating large objects, requesting 400 mb to allocate heap for some requests etc.... we still working on it....
With above info can any one suggest what is the best configuration for the application/application server?,, how can come out of those issues or reduce up to some extent.. what else can be done in application to optimize further.
Technology used in application:
>HTML, CSS, Java Script (huge script is used)
>JSP (with huge scriptlets)
> Custom Tag libs
> EJB 2.0 (all are BMP)
> JDBC 2.0
Design Patterns: Singleton, Front Controller, Session Facade, Service Locator, DAO,VO,MVC ,Factories, Distributed Cache(one that come with websphere itself).
awaiting for your detail and valuable replies... thanks in advance.