In Maximo, there are some
causes that creates performance problem. One of them is Out of Memory.
Maximo uses proprietary connection pooling. There are some default connection settings available in properties,
Maximo uses proprietary connection pooling. There are some default connection settings available in properties,
[mxe.db.initialConnections=15, mxe.db.maxFreeConnections=30,
mxe.db.minFreeConnections=10, mxe.db.newConnectionCount=5]. These values are
optimal when only one JVM is deployed.
However, when Maximo is implemented in a clustered environment, these settings can create a large number of open connections to the database. These unused connections results in unnecessary memory usage. You can tune the database by revising connection settings for fewer open connections to improve performance [mxe.db.initialConnections=6, mxe.db.maxFreeConnections=10, mxe.db.minFreeConnections=4, mxe.db.newConnectionCount=3].
Having seen the problem by many connections to database, we must avoid creating new database connections in customization, especially in crontasks. The below code snippet can be used to getDBConnection from existing connection DB pool.
However, when Maximo is implemented in a clustered environment, these settings can create a large number of open connections to the database. These unused connections results in unnecessary memory usage. You can tune the database by revising connection settings for fewer open connections to improve performance [mxe.db.initialConnections=6, mxe.db.maxFreeConnections=10, mxe.db.minFreeConnections=4, mxe.db.newConnectionCount=3].
Having seen the problem by many connections to database, we must avoid creating new database connections in customization, especially in crontasks. The below code snippet can be used to getDBConnection from existing connection DB pool.
No comments:
Post a Comment