KSI
Active Member
We just started with unique DB system users for every JDE user account. We are using OAS 10.1.3.4.0. E1 is not dropping the DB connection when users log out.
Result is that connections into SQL 2005 keep rising until the JVMs decide to restart (at about 4200 DB connections.) Currently, our 2 JVMs (75 max users each) are restarting once a shift (we are 24/7 follow the sun).
All of our tests could not get JDE to drop these connections upon user logout. Database folks say it is an application issue.
SM Tools 8.98.0.1 settings we've tried so far:
JDBj Connection Pools
Min connections=0
Pool Growth size=1
Initial connections=1 (this seemed to reduce the number of connections per user, but not persistance. Default was 5.)
Also tried KeepAlive=off in http config file.
HTTP, JAS, and JDBj files zipped and attached.
Any help is appreciated,
KSI
Result is that connections into SQL 2005 keep rising until the JVMs decide to restart (at about 4200 DB connections.) Currently, our 2 JVMs (75 max users each) are restarting once a shift (we are 24/7 follow the sun).
All of our tests could not get JDE to drop these connections upon user logout. Database folks say it is an application issue.
SM Tools 8.98.0.1 settings we've tried so far:
JDBj Connection Pools
Min connections=0
Pool Growth size=1
Initial connections=1 (this seemed to reduce the number of connections per user, but not persistance. Default was 5.)
Also tried KeepAlive=off in http config file.
HTTP, JAS, and JDBj files zipped and attached.
Any help is appreciated,
KSI